• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 97 subscribers
  • Views 623 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.

Flashing bootloaders on SPI FLASH for OMAPL137EVM

Oscar Herranz
Intellectual 770 points
Other Parts Discussed in Thread: OMAP-L137

Hi guys,

We have an OMAPL137 EVM (rev H) and we are trying to flashing the SPI FLASH memory by means the tools of DaVinci-PSP-SDK-03.20.00.14 package. We used the pre-built images (dsp-spi-ais.bin, ubl-spi.bin and u-boot.bin) and everything was ok. We were able to run a Linux distribution. Besides, we built an expansion board with a MT29F16G08CBACA NAND FLASH asynchronous memory which will be connected through EMIF-A by means the expansion port.

We want to generate the three bootloaders with EMIF A support. So, we have used the AISGEN tool in order to configure the PINMUX registers (from PINMUX13 to PINMUX19). See below:

PINMUX13 = 0x11888888;
PINMUX14 = 0x11111111;
PINMUX15 = 0x18111111;
PINMUX16 = 0x88888881;
PINMUX17 = 0x88888888;
PINMUX18 = 0x88111818;
PINMUX19 = 0x00000001;

To achieve that, we followed the next steps:

  1. Compile the source code of the three bootloaders (DaVinci-PSP-SDK-03.20.00.14 package) to obtain the .out file.
  2. Convert these .out files into .bin files by means the "AISGEN for D800K005" tool. We have checked the ROM ID of OMAPL137 and its value is D800K003. Also, we have changed the PINMUX(13 to 19) register values for having EMIF A support. (See attached screenshot)
  3. Flash the three bootloaders using the "sfh_OMAP-L137.exe" tool of OMAP-L137_FlashAndBootUtils_2_40 package.

After that procedure, the EVM does not show the u-boot prompt or any other message. However, if we use the pre-built .bin images and repeat the same procedure above, we are able to see the u-boot prompt.

Are these configuration and procedure right? 

Any idea why it does not boot?

Thank you for your help!

Regards

Óscar

  • 0
    Guru 26430 points

    Not sure if I can help. Just to clarify. You use AISGEN on all all 3 bootloaders? You should only use AISGEN on the DSPUBL. The ARMUBL is converted by hex470. The ARMUBL project has a linker command file for it and the project itself should have additional step to invoke hex470. uboot should automatically produce a bin file.

  • 0 in reply to Norman Wong
    Intellectual 770 points

    Norman Wong said:

    Not sure if I can help. Just to clarify. You use AISGEN on all all 3 bootloaders? You should only use AISGEN on the DSPUBL. The ARMUBL is converted by hex470. The ARMUBL project has a linker command file for it and the project itself should have additional step to invoke hex470. uboot should automatically produce a bin file.

    Thanks for your answer Norman, but your advise did not work. We followed your steps, first using the AISGEN tool to convert the .out first bootloader (dspubl) into .bin file; second  converting the .out second bootloader (armubl) into .bin file by means the next command:

    tiobj2bin.bat c:\Users\GTSC\workspace_CCSv5_4\ubl-omapl1x7\ubl-spi.out c:\Users\GTSC\Desktop\arm007_ubl-spi.bin c:\ti\ccsv5\tools\compiler\arm_5.0.4\bin\armofd.exe c:\ti\ccsv5\tools\compiler\arm_5.0.4\bin\armhex.exe c:\ti\ccsv5\utils\tiobj2bin\mkhex4bin.exe

    We are using these tools from cg_xml package. We obtained the .bin file and finally we flashed the SPIFLASH memory with al three bootloaders by means sfh_OMAPL137 utility from  OMAP-L137_FlashAndBootUtils_2_40 package. We are still without seeing any message when we start up the EVM...

    Any other suggestion or advise? Thanks in advance

    Regards

    Óscar

  • 0 in reply to Oscar Herranz
    Guru 26430 points

    Sorry, not much to add. I'm not familiar with tiobj2bin.bat. I don't know what tool it is using. Perhaps you should try changing one thing at a time. Use just the pre-built images with your AISGEN settings on the DSPUBL. You might have to rebuild the stock DSPUBL to get the .out file for AISGEN. If that works swap out the images from last to first, ie. your u-boot, your ARMUBL, then your DSPUBL.

  • 0 in reply to Oscar Herranz
    Guru 26430 points

    Here's the command line that ARMUBL CCS project uses to convert .out to .bin

    hex470.exe $(Proj_dir)\ubl2bin.cmd -o $(Proj_dir)\ubl-spi.bin $(Proj_dir)\spi\ubl-spi.out

    I used CCSv3.3 and it did build something that rad with the pre-built DSPUBL.