News:

Attention: For security reasons,please choose a user name *different* from your login name.
Also make sure to choose a secure password and change it regularly.

Main Menu

use prebuilt files

Started by Lilly_567, December 15, 2023, 04:24:39 PM

Previous topic - Next topic

Lilly_567

Hi,

I am really sorry about my maybe stupid questions, but I am a beginner. I was given the TE0715-05-73E33-A SoC Module with the TE0706 Carrier Board. Currently, I am trying to get the board to work with the prebuilt files. I did put BOOT.bin from \test_board\prebuilt\boot_images\03_30_3e_1gb\hello_te0715, image.ub from \test_board\prebuilt\os\petalinux\1GB and boot (the EAGLE configuration one) from the same location as the last one one an SD Card. Then I inserted the SD Card into the slot for it. I left the jumpers J10-J13 on their 1.8V position, as even if I would need HR, this also starts at 1.2V. As S1-1 does not change anything, I left it. I did switch S1-2 (PROGMODE) on, so that the SoC itself is programmed. I switched S1-3 (MODE) on in order to use SD-Boot. Furthermore, I switched S1-4 to on as well. Before plugging anything in, I checked my power supply and it was stable 5V. So I plugged in the power connector jack (J1). I connected XMOD JTAG- / UART-header, JX1 using your adapter to my laptop. To open Vivado, I used your vivado_open_existing_project_guimode script. However, I only get the following errors if I try to use the Hardware Manager:

ERROR: [Labtools 27-2269] No devices detected on target localhost:3121/xilinx_tcf/Digilent/2516330083A6A.
Check cable connectivity and that the target board is powered up then
use the disconnect_hw_server and connect_hw_server to re-register this hardware target.
ERROR: [Common 17-39] 'open_hw_target' failed due to earlier errors.
ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/2516330083A6A

I have two green and one red LED glowing, so the board seems to work. However, it does not seem to do anything, as none of the LEDs change.

If I try to use the scripts from \test_board\console\base_cmd that actually want to put something on the board, I get the same problem.

What am I doing wrong?
Thank you so much for spending time on this in advance.
Kind regards,
Lilly

JH

Hi,
TE0715-05-73E33-A  is  "\test_board\prebuilt\boot_images\04_30_3e_1gb\hello_te0715" see
https://wiki.trenz-electronic.de/display/PD/TE0715+Test+Board#TE0715TestBoard-Hardware


Hello TE0715 boot.bin print's only hello TE0715 in endless loop, so image.ub on sd is in this case not needed.
For linux boot you need Boot.bin with u-boot:
\test_board\prebuilt\boot_images\04_30_3e_1gb\u-boot
and in case of 21.2 or newer design also boot.scr file, see: https://wiki.trenz-electronic.de/display/PD/TE0715+Test+Board#TE0715TestBoard-Programming

When it boots  done LED D2 will go off:
https://wiki.trenz-electronic.de/display/PD/TE0715+TRM#TE0715TRM-MainComponents

When it boots check one time if you see  linux console or hello te0715 over uart --> connect uart for example with putty:
https://wiki.trenz-electronic.de/display/PD/TE0715+Test+Board#TE0715TestBoard-Usage


And least (it's independent from the other notes above), when you see only Digilent Number on Vivado HW Manager, than you has only a connectíon from PC to the FTDI of the XMOD. What's the XMOD DIPs?
https://wiki.trenz-electronic.de/display/PD/TE0706+TRM#TE0706TRM-JTAG/UARTInterfaceBase

If you see instead of SoC an unkown device than it's CPLD.


I didn't understand your " I did switch S1-2 (PROGMODE) on, so that the SoC itself is programmed. "  this does not mean that SOC program itself,  switch JTAG Chain between CPLD and SoC.
br
John


Lilly_567

Hi,

Thanks a lot for your reply. Sadly, it is still not working. I now use the files from the correct folder (sorry for that stupid mistake). I left the JTAG Chain switched to the SoC. The DIP Switches on TE0790-03 are still S1 ON, S2 OFF, S3 OFF and S4 ON. I did not change them since I have the board. I tried using only the hello boot.bin as well as the one with the linux boot (boot.bin, image.ub and boot). However, both seem to not work. LED D2 is not switched of either, so I guess the Linux boot does not work. Putty does open a connection, but nothing arrives. I used Speed 115200 as required in your TRM.

I searched a little bit more online and found this: https://forum.digilent.com/topic/21535-arty-a7-board-vivado-20202-labtools-27-2269-no-devices-detected-on-target-localhost3121/

It looks very similar to my problem. The hardware target is found (with an address that looks ok), but not the device. In the end they found out they have a connectivity problem that is not easy to fix. In another forum (https://support.xilinx.com/s/question/0D52E00006iHlecSAC/vivado-kc705-jtag-no-devices-detected-on-target?language=en_US) they just said that the hardware is damaged. So I was sadly not able to find a solution with the hardware manager as well.

What else could I try? Is there a way to make sure my hardware is ok? I am really sorry that this is such trouble.

Kind regards,
Lilly

JH

Hi,
it's correct, when you see only digilent serial number and no device than you has some problem between FTDI and AMD SoC oder SoC itself.
TE0790 DIPS are correct.
S1-3 DIP is set to ON and S1-4 is set to off (you wrote on it the first post, but it must be on (it's inverted))? And your SD Card is formatted as FAT32?
And which kind of external power supply did you use? what's the max. current limit?
br
John

Lilly_567

Hi,

thank you a lot for your help. The problem was the inverted switch.
I am sorry it took so long for me to reply.

Again, thank you so much. I am so happy that I can finally start to work.

Kind regards,
Lilly