SAMA5D3 XPLAINED Not running Yocto after reboot

Moderator: nferre

Bader97
Posts: 9
Joined: Tue Oct 30, 2018 3:02 pm

SAMA5D3 XPLAINED Not running Yocto after reboot

Fri Nov 16, 2018 5:27 pm

Hi,
I have built an Image, zImage, uImage, and dtbs for the kernel for sama5d3 xplained. I tried reprogramming the board by adding the image and database into their locations in nandflash (0x180000 for dtb and 0x200000 for kernel image) (I have tried all 3 images and all gave the same result) . The download is always successful. However, when it finishes and I reboot the board, the blue led stays on at all times; it does not blink like it normally would. Also, when I try to connect to it through GtkTerm, I cannot locate the device.
The image I am building is done by following the steps on the linux4sam website. My goal is to achieve an updated timestamp for the command:
uname -a.
How can I fix this issue?
I am currently waiting on a TTL-232 cable to provide with further information, more on that later.
Thanks.

Bader
blue_z
Location: USA
Posts: 1785
Joined: Thu Apr 19, 2007 10:15 pm

Re: SAMA5D3 XPLAINED Not running Yocto after reboot

Sat Nov 17, 2018 1:17 am

Bader97 wrote: (I have tried all 3 images and all gave the same result) .
Your executive summation provides no details to critique or to suggest advice.
BTW the Image file is the uncompressed version of the kernel, and is typically not used for booting.

Bader97 wrote: The download is always successful. However, when it finishes and I reboot the board, the blue led stays on at all times; it does not blink like it normally would. Also, when I try to connect to it through GtkTerm, I cannot locate the device.
These are not the type of details that can indicate what you are doing incorrectly.

Bader97 wrote: The image I am building is done by following the steps on the linux4sam website.
We don't know how accurately you have followed those steps.
Clearly you have improvised, or did those steps actually tell you to try three different image types?

Regards
Bader97
Posts: 9
Joined: Tue Oct 30, 2018 3:02 pm

Re: SAMA5D3 XPLAINED Not running Yocto after reboot

Mon Nov 19, 2018 2:48 pm

Thank you for your reply blue_z.
blue_z wrote:
Bader97 wrote: (I have tried all 3 images and all gave the same result) .
Your executive summation provides no details to critique or to suggest advice.
BTW the Image file is the uncompressed version of the kernel, and is typically not used for booting.

I did realize this fact after some research of why the Image is triple the size of uImage/zImage.
Can you possibly explain the difference between the uImage and zImage?

blue_z wrote:
Bader97 wrote: The download is always successful. However, when it finishes and I reboot the board, the blue led stays on at all times; it does not blink like it normally would. Also, when I try to connect to it through GtkTerm, I cannot locate the device.
These are not the type of details that can indicate what you are doing incorrectly.

I am not sure what details to provide in order to help clarify the problem. If you could kindly explain what to provide I can definitely post everything you need. Also my serial TTL cable should be available by the 21st of November.

blue_z wrote:
Bader97 wrote: (The image I am building is done by following the steps on the linux4sam website).
We don't know how accurately you have followed those steps.
Clearly you have improvised, or did those steps actually tell you to try three different image types?

The steps I did to build the kernel image are using the following commands:
export CROSS_COMPILE=arm-linux-gnueabi- (also tried arm-linux-gnueabihf-)
make ARCH=arm sama5_defconfig
(to build a zImage): -> make ARCH=arm
(to build a uImage):-> make ARCH=arm uImage LOADADDR=0x20008000
(to build d dtbs):-> make ARCH=arm dtbs

for the time being, I am skipping the make menuconfig step as I do not wish to change anything at the moment.

Also after trying to use the zImage and failing, I decided to use a trial and error method by using both uImage and zImage and neither one worked.

Thank you for your time and help. :)
blue_z
Location: USA
Posts: 1785
Joined: Thu Apr 19, 2007 10:15 pm

Re: SAMA5D3 XPLAINED Not running Yocto after reboot

Tue Nov 20, 2018 2:28 am

Bader97 wrote: Can you possibly explain the difference between the uImage and zImage?
Use a web search to answer to such a generic question.

Bader97 wrote: I am not sure what details to provide in order to help clarify the problem. If you could kindly explain what to provide I can definitely post everything you need. Also my serial TTL cable should be available by the 21st of November.
Have you performed any searches to see if anyone has had similar issues?
If you're having a boot failure, then you need to post the boot log.
If you don't have a connection to the serial DBGU/console, then you're dead in the water.

Bader97 wrote: The steps I did to build the kernel image are using the following commands:
export CROSS_COMPILE=arm-linux-gnueabi- (also tried arm-linux-gnueabihf-)
make ARCH=arm sama5_defconfig
(to build a zImage): -> make ARCH=arm
(to build a uImage):-> make ARCH=arm uImage LOADADDR=0x20008000
(to build d dtbs):-> make ARCH=arm dtbs
These are not commands for Yocto, so why does your title mention Yocto?

Regards
new2Atmel
Posts: 3
Joined: Fri Nov 30, 2018 9:36 pm

Re: SAMA5D3 XPLAINED Not running Yocto after reboot

Tue Dec 04, 2018 12:27 am

I have followed the Yocto build process:
https://www.at91.com/linux4sam/bin/view ... edMainPage

The only change was:

vim conf/local.conf
[...]
MACHINE ??= "sama5d2-xplained"

I changed it to sama5d3-xplained.

The output directory I think is:
extrn/lifeshield/poky/build-microchip/tmp/deploy/images/sama5d3-xplained/
at91bootstrap.bin
at91bootstrap-sama5d3_xplained.bin
at91-sama5d3_xplained.dtb
atmel-qt5-demo-image-sama5d3-xplained-20181202201720.rootfs.manifest
atmel-qt5-demo-image-sama5d3-xplained-20181202201720.rootfs.tar.gz
atmel-qt5-demo-image-sama5d3-xplained-20181202201720.rootfs.ubi
atmel-qt5-demo-image-sama5d3-xplained-20181202201720.rootfs.ubifs
atmel-qt5-demo-image-sama5d3-xplained-20181202201720.testdata.json
atmel-qt5-demo-image-sama5d3-xplained.manifest
atmel-qt5-demo-image-sama5d3-xplained.tar.gz
atmel-qt5-demo-image-sama5d3-xplained.testdata.json
atmel-qt5-demo-image-sama5d3-xplained.ubi
BOOT.BIN
core-image-minimal-sama5d3-xplained-20181201150201.rootfs.manifest
core-image-minimal-sama5d3-xplained-20181201150201.rootfs.tar.gz
core-image-minimal-sama5d3-xplained-20181201150201.rootfs.ubi
core-image-minimal-sama5d3-xplained-20181201150201.rootfs.ubifs
core-image-minimal-sama5d3-xplained-20181201150201.testdata.json
core-image-minimal-sama5d3-xplained.manifest
core-image-minimal-sama5d3-xplained.tar.gz
core-image-minimal-sama5d3-xplained.testdata.json
core-image-minimal-sama5d3-xplained.ubi
modules--4.14+git0+b733e44da2-r0-sama5d3-xplained-20181201150201.tgz
modules-sama5d3-xplained.tgz
sama5d3_xplained-nandflashboot-uboot-3.8.11+gitAUTOINC+e1fba3b7e3.bin
ubinize-atmel-qt5-demo-image-sama5d3-xplained-20181202201720.cfg
ubinize-core-image-minimal-sama5d3-xplained-20181201150201.cfg
u-boot.bin
u-boot-sama5d3-xplained.bin
u-boot-sama5d3-xplained-v2018.07-at91+gitAUTOINC+1e7d2e5973-r0.bin
zImage
zImage--4.14+git0+b733e44da2-r0-at91-sama5d3_xplained-20181201150201.dtb
zImage--4.14+git0+b733e44da2-r0-sama5d3-xplained-20181201150201.bin
zImage-at91-sama5d3_xplained.dtb
zImage-sama5d3-xplained.bin

The demo version 6.0 has the following:

at91bootstrap-sama5d3_xplained.bin demo_linux_nandflash_usb.qml u-boot-env.txt
atmel-xplained-demo-image-sama5d3-xplained.ubi README u-boot-sama5d3-xplained.bin
demo_linux_nandflash.bat sama5d3_xplained.itb
demo_linux_nandflash.sh u-boot-env.bin

Here are my questions:

1. How do I map what was generated by the Yocto build to the demo-linux-nandflash.sh?
2. Can I generate a itb and uboot-env.bin file? It looks like the u-boot-env.bin is not u-boot.bin since it has a unique place in the memory map.

Just to let you know. I tried to burn what I could but that just frustrated me.

I need a kernel reference to build drivers against so, I am a bit stuck.

Also, I did try to change the meta-qt5 git checkout to v5.8.0 which is a valid version but it error exits at bitbake. So, there must be more needed to build to the version that actually works. 5.8 seems to give you a kernel prompt but 6.0 is blank.


Thanks

Return to “SAMA5-based”

Who is online

Users browsing this forum: No registered users and 3 guests