Problem to load kernel

[PablitoSAM]

Hi All,

is long time that i don't play with ma xplained board SAMA5D2. Now i
upgrade the OS with the last version and after restarting i have the following:

RomBOOT


AT91Bootstrap 3.8.5 (Sat Apr 16 10:21:40 CEST 2016)

EEPROM: Loading AT24xx information ...
EEPROM: BoardName | [Revid] | VendorName
#0x0 SAMA5D2-XULT [AB1] ATMEL-RF0

EEPROM: Board sn: 0xd300000 revision: 0x400000

SF: Got Manufacturer and Device ID:0x1f 0x47 0x1 0x0 0x0
SF: Copy 0x80000 bytes from 0x8000 to 0x26f00000
SF: Done to load image

The system stay here and kernel is not loaded (purple led don't blink). What is going wrong?

[zdhovey2000]

Did you update u-boot as well?

[PablitoSAM]

Yes i do. I used the script "demo_linux_serialflash.bat".
The version i installed is "linux4sam-poky-sama5d2_xplained-5.7"

[PablitoSAM]

Below the complete message

AT91Bootstrap 3.8.8 (Tue Jun 13 09:45:56 CEST 2017)

EEPROM: Loading AT24xx information ...
EEPROM: BoardName | [Revid] | VendorName
#0 SAMA5D2-XULT [AB1] ATMEL-RF0

EEPROM: Board sn: 0xd300000 revision: 0x400000

SF: Got Manufacturer and Device ID: 0x1f 0x47 0x1 0x0 0x0
SF: Copy 0xa0000 bytes from 0x8000 to 0x26f00000
SF: Done to load image


AT91Bootstrap 3.8.8 (Tue Jun 13 09:45:56 CEST 2017)

EEPROM: Loading AT24xx information ...
EEPROM: BoardName | [Revid] | VendorName
#0 SAMA5D2-XULT [AB1] ATMEL-RF0

EEPROM: Board sn: 0xd300000 revision: 0x400000

SF: Got Manufacturer and Device ID: 0x1f 0x47 0x1 0x0 0x0
SF: Copy 0xa0000 bytes from 0x8000 to 0x26f00000
SF: Done to load image

[blue_z]

Now i upgrade the OS with the last version and after restarting i have the following:
...
The system stay here and kernel is not loaded (purple led don't blink).

You need to provide a clear description of what you have done done in order to get help (from me anyway).
There is no "purple led" on that board. Exactly what component are you referring to (that's why there's silkscreen)?

BTW what you call "last version" is inaccurate and ambiguous, since that is a temporal description.
On the same day that you posted, version 5.8 of the Linux4SAM demo was available on the FTP site for Microchip/Atmel boards.

Below the complete message

Why does the first boot log show the original version of AT91Bootstrap (i.e. indicating that you may have "upgraded" nothing)?
What is the significance of this second boot log (i.e. what happened in between)?

Regards

[PablitoSAM]

Good Afternoon,

You need to provide a clear description of what you have done done in order to get help (from me anyway).
There is no "purple led" on that board. Exactly what component are you referring to (that's why there's silkscreen)?

The led diode is the D2.

BTW what you call "last version" is inaccurate and ambiguous, since that is a temporal description.
On the same day that you posted, version 5.8 of the Linux4SAM demo was available on the FTP site for Microchip/Atmel boards.

The version od OS instaled is the following: linux4sam-poky-sama5d2_xplained-5.7

Why does the first boot log show the original version of AT91Bootstrap (i.e. indicating that you may have "upgraded" nothing)?
What is the significance of this second boot log (i.e. what happened in between)?

Sorry, the first log message refers to SD Card. I wrote the OS image (linux4sam-poky-sama5d27_som1_ek-5.8.img.bz2 ) by using Etcher. I placed the SD-Card in the connector and I powered the card, and the result was the one highlighted in the first log message.

The second log message refers to the on board eMMC. I have updated the Os with the eMMC version
(linux4sam-poky-sama5d2_xplained-5.8.zip). The Upgrade procedure work fine and no error is shown in the log message.
I restarted the system (without SD Card) and the debug terminal (Serial Com Port) show the message:

AT91Bootstrap 3.8.8 (Tue Jun 13 09:45:56 CEST 2017)

EEPROM: Loading AT24xx information ...
EEPROM: BoardName | [Revid] | VendorName
#0 SAMA5D2-XULT [AB1] ATMEL-RF0

EEPROM: Board sn: 0xd300000 revision: 0x400000

SF: Got Manufacturer and Device ID: 0x1f 0x47 0x1 0x0 0x0
SF: Copy 0xa0000 bytes from 0x8000 to 0x26f00000
SF: Done to load image


AT91Bootstrap 3.8.8 (Tue Jun 13 09:45:56 CEST 2017)

EEPROM: Loading AT24xx information ...
EEPROM: BoardName | [Revid] | VendorName
#0 SAMA5D2-XULT [AB1] ATMEL-RF0

EEPROM: Board sn: 0xd300000 revision: 0x400000

SF: Got Manufacturer and Device ID: 0x1f 0x47 0x1 0x0 0x0
SF: Copy 0xa0000 bytes from 0x8000 to 0x26f00000
SF: Done to load image

I hope this time i explained better the problem.

[blue_z]

I hope this time i explained better the problem.

You can hope, but you did not explain anything "better".
Instead you introduced new inaccuracies and more discrepancies.

Sorry, the first log message refers to SD Card. I wrote the OS image (linux4sam-poky-sama5d27_som1_ek-5.8.img.bz2 ) by using Etcher. I placed the SD-Card in the connector and I powered the card, and the result was the one highlighted in the first log message.

The boot log does not corroborate your sparse description.
The 5.8 image would install a different version of AT91Bootstrap than what the log shows.
FWIW that particular version and build timestamp for AT91Bootstrap matches the bootstrap originally installed in the dataflash, as well as the demo 5.3 version.
Also that image is for a different board than what you claim to have.

The second log message refers to the on board eMMC. I have updated the Os with the eMMC version
(linux4sam-poky-sama5d2_xplained-5.8.zip).

Again the boot logs do not corroborate your sparse description.
The 5.8 image would install a different version of AT91Bootstrap than what both logs show.
FYI AT91Bootstrap 3.8.8 was released with the version 5.6 of the Linux4SAM demos.

FWIW a few days ago I downloaded and flashed linux4sam-poky-sama5d2_xplained-5.7.zip (which is presumably the "version" that you claimed at one point to have used) to a SAMA5D2C-XULT board.
The board booted as expected.
So there is nothing intrinsically wrong with that image.

Regards

[PablitoSAM]

Dear blue_z,

I have the impression that you are playing the EX DEUS MACHINA rather than helping.
You are completely lacking in sensitivity towards those who are starting a journey towards the embedded world. Come back to Humans!

Now, as I explained, I am new in the world of embedded linux systems, and I can reasonably be flawed, trying to explain myself as i can. Now if you can help me, I would like to try to restore my card so I can begin to understand how it works.

Can you tell me which flash version to install on my eMMC memory card to restore everything?
Can you guide me do to this?

[blue_z]

I have the impression that you are playing the EX DEUS MACHINA rather than helping.
You are completely lacking in sensitivity towards those who are starting a journey towards the embedded world.

So instead of correcting your mistakes, you go on the offensive and critique me?
I can tolerate your misspellings and poor grammar.
I can understand omissions of fact because most people have not learned how to ask questions the smart way.
I'm inclined to point out misuse of jargon in order to remove ambiguity and restore technical accuracy.
But your plethora of misinformation and inconsistencies is not reasonable, and wastes everyone's time.
Note, I'm not obligated to answer your questions or solve your problems.

Now, as I explained, I am new in the world of embedded linux systems,

No, you have made no such explanation, unless you consider your low-quality posts an "explanation".
If you don't like your mistakes pointed out to you, then you might not want to use the Internet.

Can you tell me which flash version to install on my eMMC memory card to restore everything?

Even a straightforward question is flawed.
"Flash version" is nonsense ; you're conflating a hardware device with built image files that can to be written to several devices.
The eMMC on the SAMA5D2-XULT only stores the root filesystem.
The AT91Bootstrap, U-Boot and its environment are stored in Dataflash (aka serial flash).
Depending of the Linux4SAM demo version, the Linux kernel and the Device Tree blob are stored either in Dataflash or the root filesystem.
A literal "restore" would probably require version 5.3 of the Linux4SAM demo.
An update to the most recent (aka the latest) version would use version 5.8 of the Linux4SAM demo.

Can you guide me do to this?

No, there's already a web page with instructions.

Regards

[PablitoSAM]

I will try the restore using version 5.3. I will write any update in the morning.

[PablitoSAM]

I just downloaded the linux4sam-poky-sama5d2_xplained-5.3.
In the folder there is not the script file to flash automatically the board.
Can you help me?