meta-xilinx-bsp: Update checksums of kc705 reference design download #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Build tested ok with bitbake core-image-minimal,
MACHINE = kc705-microblazeel
LICENSE_FLAGS_WHITELIST += "xilinx"
BBLAYERS ?= " \
/home/sune/Yocto/poky/meta \
/home/sune/Yocto/poky/meta-poky \
/home/sune/Yocto/poky/meta-xilinx/meta-xilinx-bsp \
/home/sune/Yocto/poky/meta-xilinx/meta-microblaze \
"
Booting from JTAG (following README.booting) does _not_ work,
possibly due to a wrong default u-boot-xlnx configuration?
The RAM should start at 0x80000000 according to the .dts
included in xilinx-kc705-v2020.2-final.bsp:
memory@80000000 {
device_type = "memory";
reg = <0x80000000 0x40000000>;
};
But the generated u-boot.elf, is loaded to address 0x29000000:
readelf -S tmp/deploy/images/kc705-microblazeel/u-boot.elf
There are 24 section headers, starting at offset 0x393a04:
Section Headers:
[Nr] Name Type Addr Off Size ES Flg Lk Inf Al
[ 0] NULL 00000000 000000 000000 00 0 0 0
[ 1] .text PROGBITS 29000000 001000 0783f0 00 AX 0 0 4
[ 2] .rodata PROGBITS 290783f0 0793f0 012010 00 A 0 0 8
[ 3] .dtb.init.rodata PROGBITS 2908a400 08b400 0010f0 00 A 0 0 16
...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Build tested ok with bitbake core-image-minimal,
MACHINE = kc705-microblazeel
LICENSE_FLAGS_WHITELIST += "xilinx"
BBLAYERS ?= "
/home/sune/Yocto/poky/meta
/home/sune/Yocto/poky/meta-poky
/home/sune/Yocto/poky/meta-xilinx/meta-xilinx-bsp
/home/sune/Yocto/poky/meta-xilinx/meta-microblaze
"
Booting from JTAG (following README.booting) does not work,
possibly due to a wrong default u-boot-xlnx configuration?
The RAM should start at 0x80000000 according to the .dts
included in xilinx-kc705-v2020.2-final.bsp:
memory@80000000 {
device_type = "memory";
reg = <0x80000000 0x40000000>;
};
But the generated u-boot.elf, is loaded to address 0x29000000:
readelf -S tmp/deploy/images/kc705-microblazeel/u-boot.elf
There are 24 section headers, starting at offset 0x393a04:
Section Headers:
[Nr] Name Type Addr Off Size ES Flg Lk Inf Al
[ 0] NULL 00000000 000000 000000 00 0 0 0
[ 1] .text PROGBITS 29000000 001000 0783f0 00 AX 0 0 4
[ 2] .rodata PROGBITS 290783f0 0793f0 012010 00 A 0 0 8
[ 3] .dtb.init.rodata PROGBITS 2908a400 08b400 0010f0 00 A 0 0 16
...