08-15-2018 07:54 AM
- I would like to use TRACE32 debugger with Zynq Ultrascale on Avnet EG-SOM
- Using Buildroot and linux-xilinx git repository to build .elf files
(sd card boot is up and running).
- fsbl.elf, pmufw.elf, bl131.elf, vmalinux.elf are available.
Can someone give an idea, like:
- how to download elf files, in which order and addresses to download
I would like to bring up the system, using TRACE32 debugger, just like the way it gets booted using sd card
Thanks in advance.
08-27-2018 02:52 AM
Are you still working on this? XIlinx SDK does not support TRACE32 so not sure how you can download the ELF and BIN files into the target using it...
From XSDB point of view (Xilinx Debugger) you can download files into target memory using "dow" command. The process should be something like this:
08-27-2018 08:29 AM
Thanks for your attention.
TRACE32 provides .cmm script files to download an ELF file.
For example, when fsbl.elf file is downloaded, it was loaded into OCM memory location and then I could execute it.
But I am not sure what the order of downloads is?
Can I assume the order you mentioned is the proper order to download?
when u-boot, device tree (dtb), kernel images are downloaded into RAM:
- can I get the RAM locations to download each from u-boot environment variables?
or is there any other method?
08-27-2018 08:33 AM
The mentioned order is the right one although PMU firmware by itself can be downloaded/executed after of before the FSBL (differences are related more to secure boot staff).
I don't think you can get the RAM locations from U-Boot environment and use them afterwards in TRACE32 for downloading purpose... As workaround I think you might be able to load those addresses in a known memory location and use those values in TRACE32.