"Waiting for SFT on the OMAP-L138..."

See the last section of the wiki page for the serial flasher, which will tell you what files to modify:

http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138#Considerations_for_Custom_Boards

Yes you can boot directly to u-boot without a UBL. Just run the u-boot file through the AISgen program and setup the mDDR and SPI like you said. I also had to set the pinmuxing for the UART pins when I tried this out. Check out this thread which has the config file I used on the OMAP-L138 EVM:

http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/56589.aspx

Thanks for your reply.

If I want to use AISGen for generating the config for uboot directly, then which version of the tool should I use for AM1808? The one that I have complains that the frequency is higher then 300Mhz if I try to put the appropriate settings for the AM1808 (runs at 456Mhz).

Regards,

Niclas

Niclas,

It will be possible to configure PLL0 to run faster than 300 MHz in version 1.7 of the AISgen tool.  We're in the process of publishing that tool right now, but it probably isn't live on ti.com just yet.  I'm attaching the new installer so you can get started.  Please try it out and let me know if you have any trouble.

Hope this helps.

It did help, now I am able to generate the startup information to u-boot, however I still get Waiting for SFT on the OMAP-L138. Could the reason be that the DDR timings are wrong? Or what do you think it could be?

(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(AIS Parse): Performing Ping Opcode Sync...
(AIS Parse): Processing command 0: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 8656-Byte section to address 0x80000000.
(AIS Parse): Processing command 1: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 768-Byte section to address 0x800021D0.
(AIS Parse): Processing command 2: 0x58535906.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Performing jump and close...
(AIS Parse): AIS complete. Jump to address 0x80000000.
(AIS Parse): Waiting for DONE...
(AIS Parse): Boot completed successfully.

Waiting for SFT on the OMAP-L138...

It could be the DDR. Connect via emulation to the ARM and try to read and write to memory location 0xC0000000. If that doesnt work it means the DDR is not configured correctly. The wiki shows how to change the settings and rebuild for that as well.

Jeff

I got it booting from SPI:

Booting TI User Boot Loader

        UBL Version: 1.65

        UBL Flashtype: SPI
Starting SPI Memory Copy...
Valid magicnum, 0xA1ACED00, found at offset 0x00010000.
   DONE
Jumping to entry point at 0xC1080000.

But it will not start booting from a u-boot that I uploaded, I used this command:

E:\>sfh_OMAP-L138.exe -flash -targetType AM1808 -flashType SPI_MEM ubl_AM1808_SP
I_MEM.bin u-boot.bin

The U-Boot has been configured to use UART1 (it is my debug port on a home made system).

Best Regards,

Niclas

If you have an emulator can you connect and load symbols for u-boot and see where in the code you are?

I would suspect that the pinmuxing for UART1 is not configured correctly by u-boot. Can you check the PINMUX4 register (0x01C14130) and make sure the UART1 functions are enabled?

Jeff

I don't have an emulator, but I am pretty sure that this is the problem. Or maybe the u-boot tries to run at the wrong frequency?

Where in u-boot can I check the speed it thinks it is running at?

Where can I set the UART to use?

Best Regards,

Niclas Knuts

Hi,Niclas , I want to  know where did you amend the code?? 

Hi Nicolas,

How did you get it booted from SPI? What was wrong? Was DDR not initialized?

Best Regards,

Vinod

Hi,

The problem I had was not with the SPI, I had a problem getting UART1 to work, I needed it to be able to flash the firmware to the SPI memory. SPI worked fine if I preprogrammed the SPI memory.

Best Regards,

Niclas

What exactly was the pinmux change for the uart?