Trenz Electronic Products > Trenz Electronic FPGA Modules

Boot issue with VxWorks on TE0715/TE0701

(1/3) > >>

Chris12:
Hello,
I'm trying to boot a VxWorks kernel on TE0715, but it's not loading...
I'm using FSBL and u-boot from Trenz Reference Design (2018.3) - https://shop.trenz-electronic.de/en/Download/?path=Trenz_Electronic/Modules_and_Module_Carriers/4x5/TE0715/Reference_Design/2018.3

I had no issue doing this on TE0808 so i'm wondering if there is anything specific on TE0715 which could prevent the kernel from loading. The crash seems to happen very early in the boot process, even before loading the device tree...

Any clue would be much appreciated,
thanks!

JH:
Hi,

can you send me the boot log? Maybe I can find something.

Bu I haven't any experience with VxWorks, so I can't help much more.

Maybe you should also check:
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18842063/VxWorks
https://www.xilinx.com/support/documentation/application_notes/xapp1158-zynq-7000-vxworks-bsp.pdf

br
John

Chris12:
Thanks, i'll check these links.

The boot log doesn't say much, here is what I get:

Zynq> tftpb 0x5000000 uVxWorks && tftpb 0x4000000 zynq-test.dtb && bootm 0x5000000 - 0x4000000
Using ethernet@e000b000 device
TFTP from server 172.16.0.42; our IP address is 172.16.0.30
Filename 'uVxWorks'.
Load address: 0x5000000
Loading: #################################################################
         #################################################################
         ##############################
         566.4 KiB/s
done
Bytes transferred = 2342628 (23bee4 hex)
Using ethernet@e000b000 device
TFTP from server 172.16.0.42; our IP address is 172.16.0.30
Filename 'zynq-zc702.dtb'.
Load address: 0x4000000
Loading: #
         268.6 KiB/s
done
Bytes transferred = 3576 (df8 hex)
## Booting kernel from Legacy Image at 05000000 ...
   Image Name:   vxWorks
   Image Type:   ARM VxWorks Kernel Image (uncompressed)
   Data Size:    2342564 Bytes = 2.2 MiB
   Load Address: 00200000
   Entry Point:  00200000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 04000000
   Booting using the fdt blob at 0x4000000
   Loading Kernel Image ... OK
   Loading Device Tree to 07ffc000, end 07fffdf7 ... OK
## Starting vxWorks at 0x00200000, device tree at 0x07ffc000 ...

JH:
Hi,
how did you generate the device tree dtb file? Is the content correct for your TE0715 configuration?

did you check that part of Linux is not overwrite by device tree:
Linux load address        : 0x0020 0000
Device tree load address: 0x007ff c000

br
John

Chris12:
I'm using a custom device tree based on a Xilinx ZC702 board. I removed what was not required to keep only the key SoC configuration.
The exact same kernel/dtb works on many other hardware (similar SoC, different board)

But the thing is that I don't think that the DTB is the root cause.
It seems to fail very early in the boot process, I don't have a single log, even with all debug options activated in the kernel.
Actually, it doesn't even enter the CPU initialization phase.
That's why I'm trying to understand what could cause this and if there is some hardware config on this board that would require specific customization on VxWorks side

I also tried booting directly, without uboot (just FSBL + vxworks), and also with the DTB embedded in the kernel. same result.

Thanks

Navigation

[0] Message Index

[#] Next page

Go to full version