OMAPL137-HT: Booting Problems from FLASH

Marius Raducanu

Intellectual 660 points

Part Number: OMAPL137-HT
Other Parts Discussed in Thread: OMAP-L137

I have problems with booting from flash using the Processor SDK RTOS 06_03_00_106 documentation.

I got this error using the spi_flash_writer.out from Processor SDK RTOS 06_03_00_106:

*** PDK SPI Flash Writer ***

Opening SPI handle...

SPI init failed!

I got this error using the original spiflash_writer.out, where I can set the offsets of the MLO (0) and app (0x80000):

**** PDK SBL ****
SBL Revision: 01.00.09.02 (Sep 30 2020 - 17:12:59)
Begin parsing user application
Invalid magic number in Single image header
Jumping to user application...

I've checked the header of the app file and it has the magic number:

4d 53 54 52 01 20 20 20 37 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 4d 45 4e 44

My conclusion is that the 0x80000=524288 offset in flash (MLO offset=0, app offset is 0x80000) is not correct in MLO.

Can somebody confirm this?

Thanks

over 3 years ago

0 Marius Raducanu over 3 years ago

Intellectual 660 points

Found in sbl_spi.c:

#define SPI_OFFSET_SI (0x80000)

The 0x80000 app offset in flash is correct.

Both MLO and app are correct written in flash with offsets 0 and 0x80000:

Starting SPIWriter.
Enter the image type (one of "dspais" "armubl" "uboot" "other")
other
Enter the File Name
c:\temp\boot2\app
Enter the Offset in bytes (decimal)
524288
Erasing flash at byte offset: 524288, byte length: 102400
SE: cmd = { 0x20 0x080000 }
SE: cmd = { 0x20 0x081000 }

................................................................................................

PP: 0xc0011b7c => cmd = { 0x02 0x098e00 } chunk_len = 256
SF: Winbond: Successfully programmed 256 bytes @ 0x98f00
Reading verifying the file.. Files matched

I don't know why I am getting this error:

**** PDK SBL ****
SBL Revision: 01.00.09.02 (Sep 30 2020 - 17:12:59)
Begin parsing user application
Invalid magic number in Single image header
Jumping to user application...

Regards,

Marius Raducanu

0 Marius Raducanu over 3 years ago in reply to Marius Raducanu

Intellectual 660 points

I suppose, I am getting the error because the MLO FLASH doesn't match the FLASH on my EVMOMAP-L137.

I will check/debug this in the sbl source.

0 Marius Raducanu over 3 years ago in reply to Marius Raducanu

Intellectual 660 points

My evaluation board is OMAP-L137 ASSY 511340 REV H.

The FLASH memory on it is 25x32VFIG. From the data sheet, the DEVICE-ID is 0x3016.

In the pdk software for the OMAP-L137 evaluation board is defined in board_flash.h and w25x32vsfig.h:

#define BOARD_FLASH_ID_W25X32VSFIG 0x4016 /**< w25x32 SPI Flash Device ID */

#define NOR_DEVICE_ID (0x4016) /* Device ID */

0x4016 is the DEVICE-ID for W25Q32.

This explains why my eval board doesn't work with pdk but works with the older software.

I've looked in the software and there are different init functions: SPI_init() vs QSPI_init_v0 and QSPI_init_v1.

I will order a new FLASH memory and replace my 25x32 with 25Q32 on the eval board.

Regards,

Marius Raducanu

0 Marius Raducanu over 3 years ago in reply to Marius Raducanu

Intellectual 660 points

After I replaced the FLASH memory on my OMAP-L137 evaluation board with W25Q32JVSFIQ-ND, (DigiKey), I was able to write the MLO and app in FLASH using the spi_flash_writer from pdk.

The eval. board had W25x32 FLASH memory that didn't work with any pdk. I have to spend a loooooooooot of time to figure this out. It would be much better if TI provide a less compact source files (a lot of defines that are difficult to figure them out), each processor with its own sources files - it is much easier to debug.

In the next step I will modify the source code to make the eval board to work with other FLASH memories - I need one, temperature rated at least 175C.

Regards,

Marius Raducanu

Processors

Processors forum

OMAPL137-HT: Booting Problems from FLASH