I built U-boot following the instructions written in the wiki.
export ARCH=arm
export PATH=~/bin/gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf/bin:$PATH
make -j8 2>&1 | tee build.log[link text][1]
I jointed build.log
I took the source from this tag:
https://git.toradex.com/cgit/u-boot-toradex.git/tag/?h=Colibri-iMX7-eMMC_Console-Image_3.0b3.118-20200101
I managed to compile and boot the linux kernel with this toolchain: Downloads | GNU-A Downloads – Arm Developer
https://developer.arm.com/-/media/Files/downloads/gnu-a/9.2-2019.12/binrel/gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf.tar.xz
I flashed the system using toradex easy Installer.
Everything works expect three things which works with the u-boot from the BSP 2020.01.01.
I can’t start any firmware to the Cortex-m4
Following the instructions FreeRTOS on the Cortex-M4 of a Colibri iMX7 | Toradex Developer Center
Colibri iMX7 # fatload mmc 0:1 ${loadaddr} hello_world.elf
...
Colibri iMX7 # bootaux ${loadaddr}
...
## Starting auxiliary core at 0x1FFF8311 ...
Colibri iMX7 #
It works with the u-boot directly compiled from the BSP but not from the one I compiled. I got this message.
Colibri iMX7 # fatload mmc 0:1 ${loadaddr} hello_world.elf
2428444 bytes read in 52 ms (44.5 MiB/s)
Colibri iMX7 # booteaux ${loadaddr}
Invalid aux core address: 98000000
The screen doesn’t work while I am one U-boot. As soon linux started, It works.
I don’t have any boot.scr file. How do I generate it ?
I think, I made something wrong. How to compile correctly u-boot ?
Edit: I found a workaround. I rolled back to an old version, then everything works. u-boot-toradex.git - U-Boot bootloader for Apalis and Colibri modules
I found a workaround. I reverted u-boot to an old version.
https://git.toradex.com/cgit/u-boot-toradex.git/tree/?h=2016.11-toradex-next&id=1b121c6ab548a9af0a27876e9eaa0c654c1dc3e1
Then, everything works ! But I would prefer to use a current version of u-boot.
I just discovered, this bug has been known.
Looking forward to getting any new !
HI @arnaud_infoteam
BSP 2020.01.01.
Which version of Bsp is this ( uanme -a
) ?
I can’t start any firmware to the Cortex-m4
Actually this issue is fixed in 3.0b3.
The screen doesn’t work while I am one U-boot. As soon linux started, It works.
Yeah, currently Display are not supported in the U-Boot version 2019.07.
I don’t have any boot.scr file. How do I generate it ?
Please check this for the instructions.
I think, I made something wrong. How to compile correctly u-boot ?
What exactly have you done?
Best regards,
Jaski
Thanks a lot for the reply,
Sorry for the delay, I don’t any update from the community since I changed e-mail, I wil corect this.
Which version of Bsp is this ( uanme -a ) ?
I directly donwloaded u-boot from this BSP version: Colibri-iMX7-eMMC_Console-Image_3.0b3.118-20200101
Once I took the compiled one and I tried to compile myself. Same result. I also compile the kernel myselft so uname -a is not consistent for my case.
# uname -a
Linux mizar 4.14.159 #1 SMP Thu Feb 13 19:24:09 CET 2020 armv7l GNU/Linux
Actually this issue is fixed in 3.0b3
Can you give me the git tag I should use ? I currently use this one u-boot-toradex.git - U-Boot bootloader for Apalis and Colibri modules. Everything works when I compile myself.
I took this one for the new version u-boot-toradex.git - U-Boot bootloader for Apalis and Colibri modules. Then I got the issue.
I will try again this week. I let you know.
Yeah, currently Display are not supported in the U-Boot version 2019.07.
Thanks for the information. I don’t need the screen anymore. I just thought It was a clue that something was wrong.
Please check this for the instructions.
Thanks a lot, I will.
What exactly have you done?
- I downloaded the BSP there BSP Layers and Reference Images for Yocto Project Software | Toradex Developer Center
- I subsitute the bootfs and rootfs with my versions in image.json
- I tried to load my firmware from u-boot tftp ${loadaddr} alcor.elf, bootaux ${loadaddr}
- Doesn’t work
I will retry this week, I let you know. Thanks for all the precious informations
HI @arnaud_infoteam
Please let us know if you still have the issues?
Best regards,
Jaski