Compiling sources and starting sama5d3xek board

[baranek]

Hello,

I try to compile sources according to the instructions on website:
http://www.at91.com/linux4sam/bin/view/ ... s_Compiler

I follow every step of instruction but when I succesfully copy the binaries to board with samba software and try to start the board i get following output on console window:

=> RomBOOT


AT91Bootstrap 3.8.9--rc1 (Thu Aug 10 02:46:33 PDT 2017)

1-Wire: Loading 1-Wire information ...
1-Wire: ROM Searching ... Done, 0 1-Wire chips found

WARNING: 1-Wire: No 1-Wire chip found

1-Wire: Using default information

1-Wire: Board sn: 0x481242a revision: 0x6a0823

NAND: ONFI flash detected
NAND: Manufacturer ID: 0x2c Chip ID: 0x32
NAND: Page Bytes: 2048, Spare Bytes: 64
NAND: ECC Correctability Bits: 4, ECC Sector Bytes: 512
NAND: Disable On-Die ECC
NAND: Initialize PMECC params, cap: 4, sector: 512
NAND: Image: Copy 0xa0000 bytes from 0x40000 to 0x26f00000
NAND: Done to load image
<debug_uart>

U-Boot 2017.03-linux4sam_5.7-rc1 (Aug 10 2017 - 03:03:33 -0700)

CPU: SAMA5D34
Crystal frequency: 12 MHz
CPU clock : 528 MHz
Master clock : 132 MHz
DRAM: 512 MiB
Flash: 16 MiB
NAND: 256 MiB
MMC: Atmel mci: 0, Atmel mci: 1
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net:
Error: ethernet@f0028000 address not set.
No ethernet found.
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x180000, size 0x80000
524288 bytes read: OK

NAND read: device 0 offset 0x200000, size 0x600000
6291456 bytes read: OK
=>

And system boot up stop. Can u give me some advices about that where is the problem and how to fix it?
My board : MYD-sama5d3x with Atmel atsama5d34.

Thanks
MB

[blue_z]

I follow every step of instruction but when I succesfully copy the binaries to board with samba software ...

Those instruction require you to make certain choices, so claiming to follow them is not a precise description of what you did.
And claiming to use "samba software" is obviously inaccurate; SAM-BA isn't "samba".

...
NAND read: device 0 offset 0x200000, size 0x600000
6291456 bytes read: OK
=>

And system boot up stop.

That boot log appears to have returned from the autoboot with a command-line prompt.
So can you still enter commands?
What does `printenv` display? (It should be the default environment with a bootcmd defined as

Code: Select all

#define CONFIG_BOOTCOMMAND		"nand read 0x21000000 0x180000 0x80000;"	\
										"nand read 0x22000000 0x200000 0x600000;"	\
										"bootz 0x22000000 - 0x21000000"

Inspect the zImage loaded in memory at 0x22000000 (?); compare that image to what you have built on your host machine.

My board : MYD-sama5d3x with Atmel atsama5d34.

Then your title is another bogus statement in this post.
What claims does MYIR make regarding SW compatibility? I can find none.

Regards

[baranek]

Hello,

Sorry for the format of my last post. I'am new in using that kind of boards, and I start to learning about them.

The output of printenv command is presented below:

=> printenv
arch=arm
baudrate=115200
board=sama5d3xek
board_name=sama5d3xek
bootargs=console=ttyS0,115200 earlyprintk mtdparts=atmel_nand:256k(bootstrap)ro,768k(uboot)ro,256K(env_redundant),256k(env),512k(dtb),6M(kernel)ro,-(rootfs) rootfstype=ubifs ubi.mtd=6 root=ubi0:rootfs
bootcmd=nand read 0x21000000 0x180000 0x80000;nand read 0x22000000 0x200000 0x600000;bootz 0x22000000 - 0x21000000
bootdelay=3
cpu=armv7
dtb_name=sama5d34ek.dtb
fdtcontroladdr=3fb4afd8
soc=at91
vendor=atmel

Environment size: 497/131067 bytes


Regards

[baranek]

In addition, the image which I compiled and transfer to the board:

marcin@ubuntu:~/Atmel/linux-at91/arch/arm/boot$ mkimage -l uImage
Image Name: Linux-4.9.38-00710-g9241dfe
Created: Thu Aug 10 05:22:08 2017
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4035192 Bytes = 3940.62 kB = 3.85 MB
Load Address: 20008000
Entry Point: 20008000

Regards

[blue_z]

I'am new in using that kind of boards, and I start to learning about them.

You're doing a poor job of responding to questions for more clarification.
Study http://www.catb.org/esr/faqs/smart-questions.html

In addition, the image which I compiled and transfer to the board:

marcin@ubuntu:~/Atmel/linux-at91/arch/arm/boot$ mkimage -l uImage
Image Name: Linux-4.9.38-00710-g9241dfe
Created: Thu Aug 10 05:22:08 2017
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4035192 Bytes = 3940.62 kB = 3.85 MB
Load Address: 20008000
Entry Point: 20008000

This additional information identifies the crux of your problem.
You have built and installed the alternate type of kernel image that is not expected by the pre-installed bootz command.

Additionally, the use of a recent version of U-Boot, version 2017.xx, exacerbates your problem because U-Boot (as configured) will silently reject the kernel image that you're trying to boot.
Prior versions of U-Boot (i.e. v2016.07 and earlier) would always display a "Bad Linux ARM zImage magic!" error message when the wrong image type is used with that bootz command.

Regards