Failed to boot AM3358 custom board

Pascal Jacquemart

Prodigy 100 points

Other Parts Discussed in Thread: AM3358

Hi,

I just received a custom hardware based on AM3358 and I am attempting the first boot from SD Card

The design is very close to the BeagleBoneBlack and the SD Card image can boot on the BeagleBone

What I observe is that the device reboots every 10 seconds. Is it normal operation when the boot fails???

Here is the output I get from boot analysis, can you see anything odd here???

Thanks in advance

CONTROL: device_id = 0x2b94402e
* AM335x family
* Silicon Revision 2.1

PRM_DEVICE: PRM_RSTST = 0x00000001
* Bit 0 : GLOBAL_COLD_RST

CONTROL: control_status = 0x00400338
* SYSBOOT[15:14] = 01b (24 MHz)
* SYSBOOT[11:10] = 00b No GPMC CS0 addr/data muxing
* Device Type = General Purpose (GP)
* SYSBOOT[7:6] = 00b MII (EMAC boot modes only)
* SYSBOOT[5] = 1 CLKOUT1 enabled
* Boot Sequence : SPI0 -> MMC0 -> USB0 -> UART0

ROM: Current tracing vector, word 1 = 0x0010009f
* Bit 0 : [General] Passed the public reset vector
* Bit 1 : [General] Entered main function
* Bit 2 : [General] Running after the cold reset
* Bit 3 : [Boot] Main booting routine entered
* Bit 4 : [Memory Boot] Memory booting started
* Bit 7 : [Boot] GP header found
* Bit 20 : [Configuration Header] CHSETTINGS found

ROM: Current tracing vector, word 1 = 0x00011000
* Bit 12 : [Memory Boot] Memory booting trial 0
* Bit 16 : [Memory Boot] Execute GP image

ROM: Current tracing vector, word 1 = 0x00001000
* Bit 12 : Memory booting device SPI

ROM: Current copy of PRM_RSTST = 0x00000000

ROM: Cold reset tracing vector, word 1 = 0x00000000

ROM: Cold reset tracing vector, word 1 = 0x00000000

ROM: Cold reset tracing vector, word 1 = 0x00000001
* Bit 0 : [Memory Boot] Memory booting device NULL

Cortex A8 Program Counter = 0x402fadb0

ROM Exception Vectors
* 0x4030CE04 Undefined
* 0x4030CE08 SWI
* 0x4030CE0C Pre-fetch abort
* 0x4030CE10 Data abort
* 0x4030CE14 Unused
* 0x4030CE18 IRQ
* 0x4030CE1C FIQ

ROM Dead Loops
* 0x00020080 Undefined exception default handler
* 0x00020084 SWI exception default handler
* 0x00020088 Pre-fetch abort exception default handler
* 0x0002008C Data exception default handler
* 0x00020090 Unused exception default handler
* 0x00020094 IRQ exception default handler
* 0x00020098 FIQ exception default handler
* 0x0002009C Validation test PASS
* 0x000200A0 Validation test FAIL
* 0x000200A4 Reserved
* 0x000200A8 Image not executed or returned
* 0x000200AC Reserved
* 0x000200B0 Reserved
* 0x000200B4 Reserved
* 0x000200B8 Reserved
* 0x000200BC Reserved

over 10 years ago

0 Biser Gatchev-XID over 10 years ago

TI__Guru**** 393215 points

Hi,

What does your console show when you try to boot? What is the Linux version that you use? Have you tuned the DDR as shown in these guides:
processors.wiki.ti.com/.../AM335x_EMIF_Configuration_tips
processors.wiki.ti.com/.../AM335x_DDR_PHY_register_configuration_for_DDR3_using_Software_Leveling
processors.wiki.ti.com/.../Sitara_Linux_Training:_Tuning_the_DDR3_Timings_on_BeagleBoneBlack

0 Pascal Jacquemart over 10 years ago in reply to Biser Gatchev-XID

Prodigy 100 points

This is the thing, nothing shows in the console (when the SD card is inserted).
Otherwise, I see "CCCCC" for UART boot but the SPL fails to upload

Thanks for the links about DDR3 tuning, I plan to do it, but I think it is too early.
Also I can only use the JTAG for few seconds before it reboots, so it seems very hard to complete the process
Linux version does not matter, only u-boot really matters for now!

Can anyone paste the output of the boot analysis for successful booting from SD card???
I think it would help....

0 Biser Gatchev-XID over 10 years ago in reply to Pascal Jacquemart

TI__Guru**** 393215 points

This sounds like you may have a hardware issue on MMC0. From what you describe I think that this is the Watchdog timer resetting the board. Can you post the portion of the schematic that has MMC0 connections? Is this a single board or you see the same issue on several boards?

0 Pascal Jacquemart over 10 years ago in reply to Biser Gatchev-XID

Prodigy 100 points

I think this part involving the SD card cage was kept for debug and is the exact copy of the beagleBone design.
I could check with the oscilloscope that the clock is enabled for a short time and we see activity on data 0 as well
Any other idea? So if the AM3358 fails to boot it is expected that the watchdog would reboot the device endlessly?

0 Biser Gatchev-XID over 10 years ago in reply to Pascal Jacquemart

TI__Guru**** 393215 points

Yes, it will restart endlessly. Could you try an UART boot? It's described here: processors.wiki.ti.com/.../Linux_Core_U-Boot_User's_Guide

0 Pascal Jacquemart over 10 years ago in reply to Biser Gatchev-XID

Prodigy 100 points

I tried already to boot over UART, I start sending the SPL but the transfer fails at some point...
I thought this could be a DDR3 memory issue but in fact the TRM clearly explains the SPL is downloaded inside the internal L2 memory.

I think something is causing the device to reset and it has to be something else than the watchdog.
because I can connect using the JTAG but it always disconnect after few seconds (and the JTAG disables the watchdog right?)

0 Biser Gatchev-XID over 10 years ago in reply to Pascal Jacquemart

TI__Guru**** 393215 points

Let me ask again - is this a single board, or you see the issue on multiple boards?

0 Pascal Jacquemart over 10 years ago in reply to Biser Gatchev-XID

Prodigy 100 points

It is a legitimate question. We have few samples but so far only one used for preliminary checks...

Anyone can check the tracing vectors from my first post? Maybe I am missing something obvious?

Can you upload the same script output for a successful boot from SD Card?

0 Biser Gatchev-XID over 10 years ago in reply to Pascal Jacquemart

TI__Guru**** 393215 points

Pascal,

Just looked at your first post again. I see that your first boot device is SPI0. Do you have anything mounted on SPI0? If you have, could you change the boot order so that MMC0 comes first?

0 Pascal Jacquemart over 10 years ago in reply to Biser Gatchev-XID

Prodigy 100 points

Thanks for checking that. Yes we do have something on SPI but it should not be an issue.
We managed to resolve the reboot issue every 8 seconds today. Was a missing pull up on PMIC reset.
The SPL is still not booting and it is surprising because it seems to hangup in the following u-boot function:

void set_mux_conf_regs(void)
{
__maybe_unused struct am335x_baseboard_id header;

if (read_eeprom(&header) < 0)
puts("Could not get board ID.\n");

enable_board_pin_mux(&header);
}

U-boot tries to detect the board type by reading a specific structure in the eeprom?
Then enable_board_pin_mux() have some conditionals for each board type (evm, beagleBone etc) but we are none of them....

0 Biser Gatchev-XID over 10 years ago in reply to Pascal Jacquemart

TI__Guru**** 393215 points

OK, that's a big step forward. This next obstacle is quite normal. TI EVMs have a board ID EEPROM, which is used by Linux to check what is the board that it's running on, and configure accordingly. You can either skip these checks, or hardcode the EEPROM data as decribed here: e2e.ti.com/.../876780

0 Pascal Jacquemart over 10 years ago in reply to Biser Gatchev-XID

Prodigy 100 points

Thanks for your help, it works now that I am pretending to be a BeagleBone board

0 Biser Gatchev-XID over 10 years ago in reply to Pascal Jacquemart

TI__Guru**** 393215 points

Great! Thanks for the update!

Processors

Processors forum

Failed to boot AM3358 custom board