BOOTING from SPI1 Omap L137

Elodie,

    The Application Image Script (AIS) commands can be find in the OMAP-L137 Bootloader Application Report.

Elodie Pauly said:

I have burned DSP AIS IMAGE, ARM UBL and U boot, i have verified the writing all is OK.

Can you clarify what you mean here?

Elodie Pauly said:

I do not have modified the ais file and arm ubl. Only U boot has been modified.

Did you modify the U-Boot post AIS file generation? AIS has a CRC built into the script, so if you modified U boot, but did not rebuild the AIS file, I would expect an error?

Can you describe how you burned in the DSP AIS image? Did you use the CCS flasher or the serial flasher?

The ROM error code indicates that it did not find the magic number at address 0x0 of the SPI flash on SPI1.

Jeff

Hello

thanks for your answer...

I wrote files with CCS serial flasher writer program. Then I read memory and compared with original files  so as to be sure that all files are written.

Now we no longer have this error but the boot does not work, there is nothing in the hyperterminal and I can open CCS whereas I should not be able to...

Drew Abuan said:

Did you modify the U-Boot post AIS file generation? AIS has a CRC built into the script, so if you modified U boot, but did not rebuild the AIS file, I would expect an error?

U boot and AIS file are independant files, aren't  they? So we did not think it was necessary to rebuild ais file? Why do we have to rebuild ais file?

Best regards

Elodie

Please provide more details on what you have changed to remove the error, what baud rate you are set to on Hyperterminal, and why you should not be able to open CCS. Thanks,

Jeff

So what is the output of the debug GEL file when you connect to the ARM or DSP? Are you seeing any ROM errors or any activity on the UART lines?
Jeff

Hello Jeff

There is no longer error in the output of the gel file. 

---------------------------------------------
|               BOOTROM Info                |
---------------------------------------------
ROM ID: d800k001 
Silicon Revision 1.0
Boot Mode: SPI1 Flash

ROM Status Code: 0x00000000 

On UART lines we do not see activity so we think the board does not boot but we do not know where the problem is...

We have modified the uboot :

to change UART0(our custom board)  instead of UART2(EVM)

/*====================*/

/* Serial Driver info */

/*====================*/

#define CFG_NS16550

#define CFG_NS16550_SERIAL

#define CFG_NS16550_REG_SIZE 4 /* NS16550 register size */

#define CFG_NS16550_COM1 DAVINCI_UART0_BASE              /* Base address of UART0 */

#define CFG_NS16550_CLK clk_get(DAVINCI_UART2_CLKID) /* Input clock to NS16550 */

#define CONFIG_CONS_INDEX 1 /* use UART0 for console */

#define CONFIG_BAUDRATE 115200 /* Default baud rate */

#define CFG_BAUDRATE_TABLE { 9600, 19200, 38400, 57600, 115200 }

If you do not see a ROM error, we need to know what the PC value is. Please provide the entire output of the debug GEL file which will give this. Thanks

Jeff

Hello Jeff

Program Counter : PC: 0x800113A4

Elodie

That is in the shared memory region of the memory map, so it looks like your program has booted successfully. Connect in CCS and do "Load Symbols" of your original .out file and you should be able to step through your code.

You might want to check the pinmux registers if you are not seeing the IO behave correctly. Remember that you must be in supervisor mode in order to change those SYSCFG registers.

Jeff

Hello Jeff,

when we look in shared memory, we should read the arm ubl file but there is nothing. It seems the arm ubl would not be loaded in shared mermory.

Do you have an idea about it?

Regards

Elodie

What is the address of the entry point of your program? Put a hardware breakpoint at that address and reset your board while connected in CCS. When you hit that breakpoint you should see your code in the disassembly.

Jeff

Hello

first we have modified the spi flash writer in order to write ais, ubl and uboot files in the ROM of our custom board. In fact the ROM is different from the ROM of EVM. We have to unprotect sector before writing.

We have checked that files were writing as they read the rom and we compare the reading with the original file.

Now we have seen that at the boot the ais did not read well the rom because the reading buffer was always at FFFF also for rom identifier.

We search where we have doing modifications in dsp ubl project so as to resolve this problem.

Elodie 

Elodie, can you give an update on the status of your debug? Are you still in the same place?

Jeff