fsimx6-B2024.04 on board armStoneA9 Rev 1.10 - Can't boot

alfred · Jul 18th 2024

Hi,

I can't boot with your buildroot test SD on the boards: armStoneA9 Rev 1.10. I use armstonea9q.dtb

On armStoneA9's above this revision I have no problem.

U-Boot 2018.03 (Sep 21 2022 - 16:43:03 +0000) for F&S

CPU: Freescale i.MX6Q rev1.3, 996 MHz (running at 792 MHz)

CPU: Extended Commercial temperature grade (-20C to 105C)

Reset: POR

Board: armStoneA9 Rev 1.10 (LAN, 4x DRAM)

I2C: ready

DRAM: 1 GiB

NAND: 256 MiB

MMC: FSL_SDHC: 0

Loading Environment from NAND... OK

In: serial

Out: serial

Err: serial

Net: FEC [PRIME]

Normal Boot

Loading from nand0, offset 0x240000

zImage detected

NAND read: device 0 offset 0xa40000, size 0x1c0000

1835008 bytes read: OK

---- update COMPLETE! ----

armStoneA9

When I do the NAND write in uboot i see:

## Booting kernel from Legacy Image at 11000000 ...

Image Name:

Image Type: ARM Linux Script (uncompressed)

Data Size: 3730 Bytes = 3.6 KiB

Load Address: 00000000

Entry Point: 00000000

Contents:

Image 0: 3722 Bytes = 3.6 KiB

Verifying Checksum ... OK

Wrong Image Type for bootm command

ERROR: can't get kernel image!

Saving Environment to NAND... Erasing NAND...

Erasing at 0x220000 -- 100% complete.

Writing to NAND... OK

OK

do you know what might be happening?

These are my uboot variables

Code

arch=fsimx6
baudrate=115200
bootargs=console=ttymxc1,115200 login_tty=ttymxc1,115200 mtdparts=gpmi-nand:256k(NBoot)ro,768k(UserDef),256k(Refresh)ro,768k(UBoot)ro,256k(UBootEnv)ro,8m(Kernel)ro,1792k(FDT)ro,-(TargetFS) undef rw
bootcmd=run set_bootargs; run kernel; run fdt
bootdelay=3
bootfdt=armstonea9q.dtb
bootfile=zImage
console=console=ttymxc1,115200
ethact=FEC
ethaddr=00:05:51:07:55:83
ethprime=FEC
fdt=nand read 12000000 FDT; bootm 11000000 - 12000000
fdt_high=ffffffff
fdtaddr=12000000
fileaddr=11000000
filesize=fffffe00
gatewayip=10.0.0.5
installcheck=ram@10300000,mmc,usb
ipaddr=10.0.0.252
kernel=nboot Kernel
loadaddr=11000000
login=login_tty=ttymxc1,115200
mem=1046528k
mmcdev=/
mode=rw
mtddevname=NBoot
mtddevnum=0
mtdids=nand0=gpmi-nand
mtdparts=mtdparts=gpmi-nand:256k(NBoot)ro,768k(UserDef),256k(Refresh)ro,768k(UBoot)ro,256k(UBootEnv)ro,8m(Kernel)ro,1792k(FDT)ro,-(TargetFS)
netdev=eth0
netmask=255.255.255.0
partition=nand0,0
platform=armstonea9q
recovercheck=mmc,usb
rootfs=rootfstype=ubifs ubi.mtd=TargetFS root=ubi0:rootfs
rootpath=/rootfs
sercon=ttymxc1
serverip=10.0.0.122
set_bootargs=setenv bootargs ${console} ${login} ${mtdparts} ${network} ${rootfs} ${mode} ${init} ${extra}
set_bootfdt=setenv bootfdt ${platform}.dtb
stderr=serial
stdin=serial
stdout=serial
updatecheck=mmc,usb
usdhcdev=/

Display More

fs-support_PG · Jul 19th 2024

Hello,

I have tested the update process to fsimx6-B2024.04 with an armstonea9 Rev 1.11, and it worked

Is your board a Rev 1.11 or Rev 1.10 ? Please check on the PCB.

Also, please add a log of the full update process.

It seemed, that you have written an update script to the Kernel partition. This would explain the

Code

## Booting kernel from Legacy Image at 11000000 ...
Image Name:
Image Type: ARM Linux Script (uncompressed)
Data Size: 3730 Bytes = 3.6 KiB
Load Address: 00000000
Entry Point: 00000000
Contents:
Image 0: 3722 Bytes = 3.6 KiB
Verifying Checksum ... OK
Wrong Image Type for bootm command
ERROR: can't get kernel image!
Saving Environment to NAND... Erasing NAND...
Erasing at 0x220000 -- 100% complete.
Writing to NAND... OK
OK

Display More

Your F&S Support Team

alfred · Jul 19th 2024

Hi,

In uboot I see armStoneA9 Rev 1.10 but really, on PCB are armStoneA9 Rev 1.11

I have discovered the difference between armstoneA9's that do record the SD image correctly and boot and those that do not.

In the armstoneA9 that the SD is not recorded properly, in the recording process appears: ## Error: “.fdt_nand” not defined

The SD is your SD buildroot 2024.

What could the error be due to: ## Error: “.fdt_nand” not defined ?

Thank you.

alfred · Jul 20th 2024

This in my update.src file to save the image in the NAND. It works correctly in all the armstonea9 revisions except revision 1.11.

Link: https://drive.google.com/uc?ex…TjiE_3sJAEpLH651y4DVa7Diz

alfred · Jul 22nd 2024

I attach installation logs from the same SD, with two revision 1.11 boards.

One installs correctly and the other does not.

My SD files: https://drive.google.com/file/…EeuwY/view?usp=drive_link

fs-support_HK · Jul 22nd 2024

The variable .fdt_nand is available since device tree support was added to fsimx6, i.e. since release fsimx6-V3.0 in the year 2016. If the variable is missing in your environment, you may have deleted it accidentally.

Your F&S Support Team

alfred · Jul 23rd 2024

Hello,

That was the problem. They are 2015 boards and did not have several hidden variables defined in uboot, such as .fdt_nand and others.

Now it's working.

Thank you very much.

fs-support_HK · Jul 23rd 2024

Maybe it is a good idea to reset the environment with env default -a when updating U-Boot and then set your own variables again after that. Then you have all variables that were added (or removed) in the new version. However you have to take care of two things in this case:

The network addresses (eth*addr) have to be preserved in this case, for example by exporting them to RAM first with env export, then resetting the environment, and then importing them again from RAM with env import.
Some variables have the value "undef" after resetting. They will only get their board-specific values at the next start.

Your F&S Support Team

fsimx6-B2024.04 on board armStoneA9 Rev 1.10 - Can't boot

alfred Jul 18th 2024

Share

Tags