• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 97 subscribers
  • Views 376 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 SPI in OMAP L-138 EVM using ccs4

ranchu
Guru 20755 points
Other Parts Discussed in Thread: OMAP-L138

Hello,

I am using OMAPL-138 EVM and try to flash u-boot.bin into the SPI using the instructions in http://processors.wiki.ti.com/index.php/GSG:_DA8x/OMAP-L1/AM1x_DVEVM_Additional_Procedures . I see in the console of the CCS v4.2 that "reading file for verification... files matched." I then supposed that this is the succesful end of the process and everything is OK, but  then booting from SPI will result in the serial terminal "no magic number found.. SPI Memory Boot failed. Aborting".

I can add that flashing the SPI using the "flash and boot utility" using the same u-boot.bin file from TI works well, which means that the file I am using and the flash is OK. "

I also see in the spi-flash-writer-03.20.00.11 code that the magicnumber written there is different then the one that is verified... quite strange. When I try to change and compile(source of ccs4) I then get another problem: the flash writer fail to detects the spi flash. it say in the console of the code composer that "stmicro id 00... no flash detected"

Any help is appreciated,

Ran

  • 0
    TI__Mastermind 27585 points

    Can you try downloaded the last version of the SDK? I know the tools that come with SDK4 should match the magic numbers used by the UBL.

    Also you could try the serial flashing method if you run into issues recompiling the CCS-based project.

    Jeff

  • 0 in reply to jc-ti
    Guru 20755 points

    Hi Jeff,

    I solved it(partly) : the problem was that I did not flash the ARM AIS image (boot-strap), only the u-boot from the PSP package. After doing that, I then succudded in booting from spi in the EVM board. I still have a problem now with the custom board, when I flash the u-boot, I get unsupported flash idcode "1f 27 09" . Can it be that the flash writer does not support the custom SPI flash in my board?

    Regards,

     Ran

  • 0 in reply to ranchu
    TI__Mastermind 27585 points

    That may be the case. Can you check that the flash ID code you read matches the device datasheet?

    Jeff

  • 0 in reply to jc-ti
    Guru 20755 points
    Hi Jeff, The idcode is for ATMEL, and ATMEL flash is not supported. I had to add the atmel.c into the code. Thanks! Ran
  • 0 in reply to jc-ti
    Guru 20755 points
    Hi Jeff, I still have some strange things with the OMAP-L138 EVM: when I load and run spi-flashwriter.out from the PSP../image the software detects the idcode (STMICRO) and flashing works great, when I just compile the flash writer with CCS4 - without still making any single change in the code - and then running the .out file generated, I recieve that idcode is 00 00 00. Do you have any idea why is it different then the .out from the image/utils of PSP ? Thank you very much for the help and time, Ran
  • 0 in reply to ranchu
    TI__Mastermind 27585 points

    No I'm not sure about that. Can you try changing the project settings to not use any optimizations? Perhaps some code is being optimized out incorrectly by the compiler.

    Jeff

  • 0 in reply to jc-ti
    Guru 20755 points
    Hi jeff, I succeeded in flashing at last. I had to choose in project build manager spi1 (it by default was spi0), then the flash was detected, I later had to make more changes becuase I use atmel with page size of 528, had to enlarge the tx, rx, buffer in main. Thank you for your guidance, Ran