• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 183 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Issues on the AIS binary running on the OMAPL137

pramodbk
Prodigy 220 points
Other Parts Discussed in Thread: OMAP-L137

Hi,

 

My customer is trying to run a simple standalone application with the CCS disconnected. on the OMAPL137 EVM. He has created a AIS binary which he has flashed to SPI flash . But the application doesn't seems to run. The steps he has followed to run the standalone application is given below. Any idea why it doesn't work.

 

Regards,

Pramod

 

Here’s a recount of all I’ve done:

 

I have a working standard application using NDK 2.0.0. I have prepared for standalone execution adding the following capabilities to main():

  • The equivalent of the GEL initialization is now done 1st.
  • Setup of UART2 and a short message sent to UART2

 

This works under CCS hooked up to the EVM board using an XDS510 USB JTAG connection. I then attempt to make this work standalone by the following steps:

 

  • Using the resultant app.out of the above application I have created an AIS binary using AISgen for D800K003 (the EVM board has D800K001 version by the way, but is still supposed to be compatible). This is to standard setting setup by selecting “Configure for EVM”. These values appear correct. AISgen denotes that it has created the app.bin file successfully.
  • The JTAG connector is disconnected and the boot dipswitches are set for UART2 boot. A null modem serial port cable connects the PC to EVM board.
  • The SPI flash is presented the app.bin file using the utility sfh_OMAP-L137.exe by the following steps:
    • sfh_OMAP-L137 –p COM3 –spierase
    • sfh_OMAP-L137 –p COM3 –spiflashnoubl app.bin

 

At this point the application should be in SPI flash start address 0. Put the boot dipswitches to boot from SPI flash. All of this from the documentation I’ve been able to find with the result:

 

  • It doesn’t work. I do not see the message from UART2 and the Ethernet operations do not occur.
  • I’m blind as I’m disconnected from the JTAG. Is there any way to debug this? I’m not sure CCS connects without being invasive and dictating it’s own resources on the app(?)

 

I’ve not seen references to the above troubles in any documentation or blogs I’ve encountered. Any ideas on how to get this app to work – or to properly debug it?