KCC's Quizzes AQQ305 about a mutual exponentiation equation
1. Quote of the month: "A train station is where a train stops. A bus station is where a bus stops. I have a work station on my desk, so..." - unknown
2. Quiz AQQ305 about finding a mutual exponential equation
Good luck, and try to be among the
View All
September Monthly Blog Quiz! Read the blog, take the quiz, and you could win a gift card
Quiz: How Well Do You Know Adaptive Power Switching?
Is your I/O module overheating? The AD74416H's Adaptive Power Switching (APS) can cut heat dissipation by up to 40% — but how well do you really understand how it works?
Read the blog first: Cooling
View All
Hi all, I am following the official Unbricking PlutoSDR wiki guide on a bricked Pluto, however as this guide is quite outdated, here I describe my attempt at unsuccessfully unbricking a Pluto. The hardware was handed to me after a team of satellite engineers had difficulty unbricking it, so I am not sure how a working unit should appear. My configuration is:
Following the steps of the guide as follows:
> After the JTAG programmer is connected, provide power to PlutoSDR using either of its USB connectors. Once powered the D5 led should illuminate to signal the JTAG connection to the programmer is alive.
With the 10-way JTAG ribbon cable connected, I power the JTAG-HS3, then power the PlutoSDR (USB port "P3" plugged in to the PC, as shown in the guide figure). The red LED labeled "VIO" lights on the UARTJTAG board. My Pluto dimly lights the LED with designator DS2 (the one in the corner of the PCB). The Pluto LED DS1 remains off.
> 1. Plug in JTAG as documented above into Pluto and verify you can connect with Vivado
I run:
$ source /tools/Xilinx/Vivado/2024.1/settings64.sh
$ xsct
****** Software Commandline Tool (XSCT) v2024.1.2
**** SW Build 0 on 2024-09-05-05:57:41
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
Warning: XSCT has been deprecated. It will still be available for several releases.It's recommended to start new projects with new python command line tool.
Use "vitis -s <script>" (script mode) and "vitis -i" (interactive mode) to load new Python CLI for Vitis.
xsct% connect -host localhost -port 3121
Connection refused
xsct%
With the command having failed, I launch the `vivado` GUI from the command line and click on the "Open Hardware Manager" task link, then Menu -> Tools -> Open new target. Connect to local server. The `xilinx_tcf` hardware target is auto-detected with JTAG frequency 15000000 and hardware devices `arm_dap_0` and `xc7z010_1` are auto-detected. Hardware server settings on next page reads `localhost:3121`. Closing the dialog, the hardware list shows the status of `arm_dap_0` as "N/A", and the status of `xc7x010_1` as "Not programmed".
Now trying again with the command line, I get
$ xsct
****** Software Commandline Tool (XSCT) v2024.1.2
**** SW Build 0 on 2024-09-05-05:57:41
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
Warning: XSCT has been deprecated. It will still be available for several releases.It's recommended to start new projects with new python command line tool.
Use "vitis -s <script>" (script mode) and "vitis -i" (interactive mode) to load new Python CLI for Vitis.
xsct% connect -host localhost -port 3121
tcfchan#0
xsct% targets
1 APU
2 ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4 xc7z010
xsct%
There must be a command that is missing from the command line instructions, but now the command appears to work after the GUI procedure I described.
> 2. Download the JTAG bootstrap zip from the firmware release page (plutosdr-jtag-bootstrap-<Firmware Version>.zip)
> 3. Unzip the zip then source the run.tcl inside with xmd from the Xilinx tools (xmd -tcl run.tcl). We are done with JTAG now
The command `xmd` no longer exists, however the zip file contains a clue in the form of a file called `run-xsdb.tcl` with contents that look similar to the `run.tcl` in the instructions. The command to run is found in the file comment. Presumably, `xsdb` is a replacement for `xmd`.
~/Downloads/plutosdr-jtag-bootstrap-v0.39$ xsdb run-xsdb.tcl
attempting to launch hw_server
****** Xilinx hw_server v2024.1.2
**** Build date : Aug 28 2024 at 13:40:10
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application
INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121
$
The command prompt returns without any explicit success message but no error neither. LEDs are same as before. The instruction reads "We are done with JTAG now", but not sure what that means, whether we should leave it plugged in or unplug it. (spoiler: it made no difference in my case). For what it's worth, I left it plugged in and considered it "done".
> 4. Next plugin a USB cable to the UART port of the ADALM-UARTJTAG connector and open a serial session (Putty or screen or …)
A green LED (labeled "VUSB") lights up on the ADALM-UARTJTAG when plugged in as described. The guide doesn't give any details about what baud, stop bits, parity etc are needed, however despite trying virtually all possible common serial baud rate speeds and parameters, I was unable to get any sign of life from the serial port, and no u-boot menu was seen as indicated on the next step of the procedure.
Notably, after running the `xsdb` tcl script causes subsequent connection attempts with `xsct` to fail. Heading back to the GUI and reconnecting to the JTAG-HS3, the Xilinx still shows as "Not programmed".
After turning it off and on again, I reconnect with the GUI as before, except this time I click "Program device" with the bitstream file `system_top.bit`. There appears to be no "Debug probes file", however this does not seem to prevent the programming from going ahead. It appears to succeed, listing `arm_dap_0` as "N/A" (as before) but now `xc7x010_1` shows as "Programmed" and now the DS1 LED lights up much brighter than the constantly lit dim DS2 led. Despite this promising sign of life, u-boot remains unseen on any serial port with any baud rate and parameters I have tried, repeatedly typing, sending CTRL+C, and hitting ENTER with no result (to both Pluto and JTAG serial ports). There appears to be a `u-boot.elf` file in the zip archive, but I haven't yet found a way to get this onto the board by the command line or the GUI. Typing the tcl script lines one by one appears to
Can anyone spot where it's going wrong, or if it may even be a sign of dead Pluto?
It would really benefit the community to at least update that official unbricking guide, even if only to instill us with some confidence that the guide isn't broken and that we're not doing anything wrong. It would help with:
I am still hoping to get myself back into HDL/FPGA/SDR development after this thing is unbricked.
Hi m0set ,
Indeed the command xmd no longer exists, the valid one is "xsct run.tcl"
In regards to the UART parameters: https://wiki.analog.com/resources/fpga/uart_setup
However, when going trough the steps this has been observed:
- after programming the bootloader with "xsct run.tcl" there is output on the UART (uboot boot log)
- pluto then boots dirrectly into DFU mode, step 5 "run dfu_sf" is not needed
I've observed the same behaviour, the UART is not responding after flashing with run.tcl as Pluto is already in DFU mode.
I guess that your pluto is recoverable and in DFU.
Also, when I tried this, disconnecting and reconnecting power to the pluto after "xsct run.tcl" did not seem to make it boot back to DFU, so it's possible that you will need to run "xsct run.tcl" again.
Hi Dumitru, thanks for the suggestions, however running `xsct run.tcl` also failed for me:
~$ source /tools/Xilinx/Vivado/2024.1/settings64.sh
~$ cd Downloads/plutosdr-jtag-bootstrap-v0.39/
~/Downloads/plutosdr-jtag-bootstrap-v0.39$ ls
ps7_init.tcl run.tcl run-xsdb.tcl system_top.bit u-boot.elf
~/Downloads/plutosdr-jtag-bootstrap-v0.39$ xsct run.tcl
unexpected arguments: arm hw
while executing
"error "unexpected arguments: $arglist""
(procedure "::xsdb::get_options" line 69)
invoked from within
"::xsdb::get_options args $options"
(procedure "connect" line 17)
invoked from within
"connect arm hw"
(file "run.tcl" line 7)
I also tried going through the standard DFU procedure both with and without flashing `system_top.bit` from the GUI however:
As before, I tried `xsct` and each step of the DFU procedure both with and without flashing the bitstream file from the GUI (as described in the opening post) and from each of the USB ports, while monitoring any serial port with the correct serial parameters but still nothing so far.
Hi m0set ,
Sorry for the confusion, I meant to say "xsct run-xsdb.tcl". After running this command Pluto should boot into DFU mode.
When Pluto is connected with usb to your PC, does the "Analog Devices, Inc. USB download gadget" device appear when running lsusb?
Also, when booting into DFU mode, Pluto outputs a boot log to the UART port of ADALM-UARTJTAG. Test this by unplugging-plugging the USB connector that powers the Pluto.
Hi dumitruCeclan ,
I gave it another try with `xsct run-xsdb.tcl`. The program appears to complete without any obvious error message shown however it seems (at least from the command output and its effects on the hardware) to be identical to running `xsdb run-xsdb.tcl`:
~$ source /tools/Xilinx/Vivado/2024.1/settings64.sh
~$ cd Downloads/plutosdr-jtag-bootstrap-v0.39/
~/Downloads/plutosdr-jtag-bootstrap-v0.39$ xsct run-xsdb.tcl
attempting to launch hw_server
****** Xilinx hw_server v2024.1.2
**** Build date : Aug 28 2024 at 13:40:10
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application
INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121
Tried all the ports and all the combinations as before but the result seems the same i.e., no output on serial, no mass storage, the LED DS2 remains dim and DS1 remains off etc (unlike the GUI method I described above, which gives just an inkling to suggest there is still life in the unit but has its own dead end i.e. no obvious way to run `u-boot.elf` and to see it on the serial port).
Does your `xsct run-xsdb.tcl` output look the same as mine?
Hi m0set,
From above it looks like the tools could not connect to the hw_server.
Please do the following experiment.
In a terminal on which you have the paths to AMD/Xilinx tools, enter:
xsct connect target exit
Hi m0set,
From above it looks like the tools could not connect to the hw_server.
Please do the following experiment.
In a terminal on which you have the paths to AMD/Xilinx tools, enter:
xsct connect target exit
Hi m0set ,
You could also try to do the commands from 'run-xsdb.tcl' by hand and see the output from each one:
Enter the xsct cli, then follow the commands from 'run-xsdb.tcl' but with one additional reset to the APU (target 1):
# xsct
****** Software Commandline Tool (XSCT) v2023.1.0
**** SW Build 0 on 2023-05-03-16:48:11
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2023 Advanced Micro Devices, Inc. All Rights Reserved.
xsct% connect
attempting to launch hw_server
****** Xilinx hw_server v2023.1
**** Build date : May 3 2023 at 14:03:27
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2023 Advanced Micro Devices, Inc. All Rights Reserved.
INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application
INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121
tcfchan#0
xsct% target
1 APU
2 ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4 xc7z010
xsct% target 1
xsct% rst
xsct% target 2
xsct% rst
xsct% source ps7_init.tcl
xsct% ps7_init
xsct% ps7_post_config
xsct% dow u-boot.elf
Downloading Program -- /home/analog/Downloads/u-boot.elf
section, .text: 0x04000000 - 0x0403f613
section, efi_runtime_text: 0x0403f614 - 0x0403f62b
section, .rodata: 0x0403f630 - 0x0404f873
section, .hash: 0x0404f874 - 0x0404f88b
section, .dtb.init.rodata: 0x0404f890 - 0x04051c4f
section, .data: 0x04051c50 - 0x04053e77
section, .got.plt: 0x04053e78 - 0x04053e83
section, efi_runtime_data: 0x04053e88 - 0x04053f4f
section, .u_boot_list: 0x04053f50 - 0x04054d53
section, .rel.dyn: 0x04054d54 - 0x0405d7b3
section, .bss_start: 0x04054d54 - 0x04054d53
section, .bss: 0x04054d54 - 0x040a5793
section, .bss_end: 0x040a5794 - 0x040a5793
100% 0MB 0.5MB/s 00:00
Setting PC to Program Start Address 0x04000000
Successfully downloaded /home/analog/Downloads/u-boot.elf
xsct% Info: ARM Cortex-A9 MPCore #0 (target 2) Stopped at 0xffffff28 (Suspended)If you get the error:
Memory write error at 0xF8000778. Cannot flush JTAG server queue. ftdi_read_data failed: usb bulk read failed
Try to reset targets 1 and 2 again then continue with the following instructions.
After running the commands, Pluto should be in DFU mode.
Dumitru
Thanks andrei_g , it seems my hardware is indeed recognized with `xsct`:
~$ source /tools/Xilinx/Vivado/2024.1/settings64.sh
~$ xsct
rlwrap: warning: your $TERM is 'xterm-256color' but rlwrap couldn't find it in the terminfo database. Expect some problems.
****** Software Commandline Tool (XSCT) v2024.1.2
**** SW Build 0 on 2024-09-05-05:57:41
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
Warning: XSCT has been deprecated. It will still be available for several releases.It's recommended to start new projects with new python command line tool.
Use "vitis -s <script>" (script mode) and "vitis -i" (interactive mode) to load new Python CLI for Vitis.
xsct% connect
attempting to launch hw_server
****** Xilinx hw_server v2024.1.2
**** Build date : Aug 28 2024 at 13:40:10
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application
INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121
tcfchan#0
xsct% target
1 APU
2 ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4 xc7z010
xsct% exit
exit
I did manage to type in the commands but still nothing on the serial output. Here's my method:
Sometimes I reverse the last two steps but the same result. Here's my output the first time:
~$ xsct
rlwrap: warning: your $TERM is 'xterm-256color' but rlwrap couldn't find it in the terminfo database. Expect some problems.
****** Software Commandline Tool (XSCT) v2024.1.2
**** SW Build 0 on 2024-09-05-05:57:41
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
Warning: XSCT has been deprecated. It will still be available for several releases.It's recommended to start new projects with new python command line tool.
Use "vitis -s <script>" (script mode) and "vitis -i" (interactive mode) to load new Python CLI for Vitis.
xsct% connect
attempting to launch hw_server
****** Xilinx hw_server v2024.1.2
**** Build date : Aug 28 2024 at 13:40:10
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application
INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121
tcfchan#0
xsct% target
1 APU
2 ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4 xc7z010
xsct% target 1
xsct% rst
xsct% target 2
xsct% rst
xsct% source ps7_init.tcl
xsct% ps7_init
xsct% ps7_post_config
xsct% dow u-boot.elf
Downloading Program -- /home/pasha/Downloads/plutosdr-jtag-bootstrap-v0.39/u-boot.elf
section, .text: 0x04000000 - 0x0403f613
section, efi_runtime_text: 0x0403f614 - 0x0403f62b
section, .rodata: 0x0403f630 - 0x0404f873
section, .hash: 0x0404f874 - 0x0404f88b
section, .dtb.init.rodata: 0x0404f890 - 0x04051c4f
section, .data: 0x04051c50 - 0x04053e77
section, .got.plt: 0x04053e78 - 0x04053e83
section, efi_runtime_data: 0x04053e88 - 0x04053f4f
section, .u_boot_list: 0x04053f50 - 0x04054d53
section, .rel.dyn: 0x04054d54 - 0x0405d7b3
section, .bss_start: 0x04054d54 - 0x04054d53
section, .bss: 0x04054d54 - 0x040a5793
section, .bss_end: 0x040a5794 - 0x040a5793
100% 0MB 0.2MB/s 00:01
Setting PC to Program Start Address 0x04000000
Successfully downloaded /home/pasha/Downloads/plutosdr-jtag-bootstrap-v0.39/u-boot.elf
xsct% Info: ARM Cortex-A9 MPCore #0 (target 2) Stopped at 0x59c (Suspended)
Info: ARM Cortex-A9 MPCore #0 (target 2) Running (APB AP transaction error, DAP status 0xF0000021)
xsct% con
Already running
xsct% state
APB AP transaction error, DAP status 0xF0000021
xsct%
Note that I'm not using the `JTAG BOOT` jumper on the UARTJTAG (it reportedly halts the Zynq and prevents U-boot finding the SPI flash as indicated in the ADALM-UARTJTAG page) but I put the jumper on anyway this time:
~$ xsct
rlwrap: warning: your $TERM is 'xterm-256color' but rlwrap couldn't find it in the terminfo database. Expect some problems.
****** Software Commandline Tool (XSCT) v2024.1.2
**** SW Build 0 on 2024-09-05-05:57:41
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
Warning: XSCT has been deprecated. It will still be available for several releases.It's recommended to start new projects with new python command line tool.
Use "vitis -s <script>" (script mode) and "vitis -i" (interactive mode) to load new Python CLI for Vitis.
xsct% connect
attempting to launch hw_server
****** Xilinx hw_server v2024.1.2
**** Build date : Aug 28 2024 at 13:40:10
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application
INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121
tcfchan#0
xsct% target
1 APU
2 ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4 xc7z010
xsct% target 1
xsct% rst
xsct% target 2
xsct% rst
xsct% source ps7_init.tcl
xsct% ps7_init
xsct% ps7_post_config
xsct% dow u-boot.elf
Downloading Program -- /home/pasha/Downloads/plutosdr-jtag-bootstrap-v0.39/u-boot.elf
section, .text: 0x04000000 - 0x0403f613
section, efi_runtime_text: 0x0403f614 - 0x0403f62b
section, .rodata: 0x0403f630 - 0x0404f873
section, .hash: 0x0404f874 - 0x0404f88b
section, .dtb.init.rodata: 0x0404f890 - 0x04051c4f
section, .data: 0x04051c50 - 0x04053e77
section, .got.plt: 0x04053e78 - 0x04053e83
section, efi_runtime_data: 0x04053e88 - 0x04053f4f
section, .u_boot_list: 0x04053f50 - 0x04054d53
section, .rel.dyn: 0x04054d54 - 0x0405d7b3
section, .bss_start: 0x04054d54 - 0x04054d53
section, .bss: 0x04054d54 - 0x040a5793
section, .bss_end: 0x040a5794 - 0x040a5793
100% 0MB 0.2MB/s 00:01
Setting PC to Program Start Address 0x04000000
Successfully downloaded /home/pasha/Downloads/plutosdr-jtag-bootstrap-v0.39/u-boot.elf
xsct% Info: ARM Cortex-A9 MPCore #0 (target 2) Stopped at 0xffffff28 (Suspended)
xsct% con
Info: ARM Cortex-A9 MPCore #0 (target 2) Running
xsct% state
Running
xsct%
Definitely looks like one less error but still nothing on the serial. Trying another time with the jumper removed:
~$ xsct
rlwrap: warning: your $TERM is 'xterm-256color' but rlwrap couldn't find it in the terminfo database. Expect some problems.
****** Software Commandline Tool (XSCT) v2024.1.2
**** SW Build 0 on 2024-09-05-05:57:41
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
Warning: XSCT has been deprecated. It will still be available for several releases.It's recommended to start new projects with new python command line tool.
Use "vitis -s <script>" (script mode) and "vitis -i" (interactive mode) to load new Python CLI for Vitis.
xsct% connect
attempting to launch hw_server
****** Xilinx hw_server v2024.1.2
**** Build date : Aug 28 2024 at 13:40:10
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application
INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121
tcfchan#0
xsct% target
1 APU
2 ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4 xc7z010
xsct% target 1
xsct% rst
xsct% target 2
xsct% rst
xsct% source ps7_init.tcl
xsct% ps7_init
xsct% ps7_post_config
xsct% dow u-boot.elf
Downloading Program -- /home/pasha/Downloads/plutosdr-jtag-bootstrap-v0.39/u-boot.elf
section, .text: 0x04000000 - 0x0403f613
section, efi_runtime_text: 0x0403f614 - 0x0403f62b
section, .rodata: 0x0403f630 - 0x0404f873
section, .hash: 0x0404f874 - 0x0404f88b
section, .dtb.init.rodata: 0x0404f890 - 0x04051c4f
section, .data: 0x04051c50 - 0x04053e77
section, .got.plt: 0x04053e78 - 0x04053e83
section, efi_runtime_data: 0x04053e88 - 0x04053f4f
section, .u_boot_list: 0x04053f50 - 0x04054d53
section, .rel.dyn: 0x04054d54 - 0x0405d7b3
section, .bss_start: 0x04054d54 - 0x04054d53
section, .bss: 0x04054d54 - 0x040a5793
section, .bss_end: 0x040a5794 - 0x040a5793
100% 0MB 0.2MB/s 00:01
Setting PC to Program Start Address 0x04000000
Successfully downloaded /home/pasha/Downloads/plutosdr-jtag-bootstrap-v0.39/u-boot.elf
xsct% Info: ARM Cortex-A9 MPCore #0 (target 2) Stopped at 0x59c (Suspended)
xsct% state
Stopped: (Suspended)
xsct% con
Info: ARM Cortex-A9 MPCore #0 (target 2) Running
xsct% state
Running
xsct%
It's "Running" according to the status but still nothing on the serial output. Note the hex addresses are different each time so not sure what's going on there.
I sometimes tried the `xsct` commands after flashing the `system_top.bit` from the GUI (just because it feels good when DS1 lights up bright like it's coming to life...) but the `rst` command caused the LED to turn back off. I run it without `rst` as follows:
~$ xsct
rlwrap: warning: your $TERM is 'xterm-256color' but rlwrap couldn't find it in the terminfo database. Expect some problems.
****** Software Commandline Tool (XSCT) v2024.1.2
**** SW Build 0 on 2024-09-05-05:57:41
** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.
** Copyright 2022-2024 Advanced Micro Devices, Inc. All Rights Reserved.
Warning: XSCT has been deprecated. It will still be available for several releases.It's recommended to start new projects with new python command line tool.
Use "vitis -s <script>" (script mode) and "vitis -i" (interactive mode) to load new Python CLI for Vitis.
xsct% target
Invalid target. Use "connect" command to connect to hw_server/TCF agent
xsct% connect
tcfchan#0
xsct% target
1 APU
2 ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4 xc7z010
xsct% target 2
xsct% source ps7_init.tcl
xsct% ps7_init
xsct% ps7_post_config
xsct% dow u-boot.elf
Downloading Program -- /home/pasha/Downloads/plutosdr-jtag-bootstrap-v0.39/u-boot.elf
section, .text: 0x04000000 - 0x0403f613
section, efi_runtime_text: 0x0403f614 - 0x0403f62b
section, .rodata: 0x0403f630 - 0x0404f873
section, .hash: 0x0404f874 - 0x0404f88b
section, .dtb.init.rodata: 0x0404f890 - 0x04051c4f
section, .data: 0x04051c50 - 0x04053e77
section, .got.plt: 0x04053e78 - 0x04053e83
section, efi_runtime_data: 0x04053e88 - 0x04053f4f
section, .u_boot_list: 0x04053f50 - 0x04054d53
section, .rel.dyn: 0x04054d54 - 0x0405d7b3
section, .bss_start: 0x04054d54 - 0x04054d53
section, .bss: 0x04054d54 - 0x040a5793
section, .bss_end: 0x040a5794 - 0x040a5793
100% 0MB 0.2MB/s 00:01
Setting PC to Program Start Address 0x04000000
Successfully downloaded /home/pasha/Downloads/plutosdr-jtag-bootstrap-v0.39/u-boot.elf
xsct% Info: ARM Cortex-A9 MPCore #0 (target 2) Stopped at 0x59c (Suspended)
xsct% state
Stopped: (Suspended)
xsct% con
Info: ARM Cortex-A9 MPCore #0 (target 2) Running
xsct% state
Running
xsct%
but still no serial output. Still not giving up. I will keep reading and trying to work it...
After running 'dow u-boot.elf' pluto should be in DFU mode.
From what I can see, the command was completed successfully.
Did you use 'lsusb' to check for 'Analog Devices, Inc. USB download gadget'?
If you can see it continue with the instructions for flashing with DFU utils.
Dumitru
Thanks Dumitru, I checked the following things (and some steps from the DFU guide) but still can't seem to get it in the right mode it needs to be in:
Paul
Did you test this with 'JTAG BOOT' jumper on the UARTJTAG plugged in?
You should see some output on the UART from the ADALM-UARTJTAG usb port when power-cycling the Pluto if the device boots into DFU. U-Boot PlutoSDR v0.20-PlutoSDR-00066-g90401ce9ce (Nov 17 2023 - 10:28:18 +0100)
I2C: ready
DRAM: ECC disabled 512 MiB
SF: Detected N25Q256A with page size 256 Bytes, erase size 4 KiB, total 32 MiB
In: serial@e0001000
Out: serial@e0001000
Err: serial@e0001000
Model: Zynq Pluto SDR Board
Hit any key to stop autoboot: 0
Booting silently
BOOT failed entering DFU mode ...
SF: Locked
gpio: pin 15 (gpio 15) value is 1
Entering DFU SF mode ...
The last steps were done without the 'JTAG BOOT' jumper, but I tried it again with the jumper and still nothing seen on the UARTJTAG's USB UART at 115200 baud.
I also tried power-cycling the Pluto after flashing while keeping the 10-pin ribbon and UARTJTAG connected (and both with and without JTAG-HS3 connected) but again, nothing seen on the UARTJTAG USB UART still unfortunately.
Note also, probing the RX test point near the JTAG header on the Pluto with an oscilloscope shows characters being sent in from the computer to the Pluto when typed in the serial terminal at 115200, but probing TX during and after flashing (and also power cycling) shows no characters being sent from the Pluto to the computer (should be U-boot messages).
Hi,
Some ideas.
The JTAG BOOT jumper should not connected.
1. Use a second USB cable to power the Pluto on the power input micro USB. In case your main USB or power source is not reliable/sufficient.
2. You can use the system_top.xsa to create a "Hello World" app. That will let you know if the is any problem with the UART/FPGA.
maybe add some other code and some break points. To see if the zynq behaves as expected, if not, than that SoC can RIP.
Andrei
Hi Anrdei,
I tried a second USB cable to a USB plug-in charger in addition to the main port to the computer, but still nothing on the UARTJTAG USB serial (without JTAG BOOT jumper).
Searching for `system_top.xsa`, I came across building boot images - so is `system_top.xsa` an image that I generate from Vivado/Vitis/HDL code? Maybe it results in a `system_top.bit` file? Unfortunately, I haven't used a working Pluto or Xilinx tools beyond these unbricking attempts.
I can program the `system_top.bit` that came with the bootstrap zip separately from the GUI which causes the DS1 LED to light bright. Separately, I can program `u-boot.bin` from `xsct`. It all seems so close yet no serial output in either case.
I'll try to create a hello world project some time and will update whether it worked, but for now my Pluto is looking quite dead.