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

standalone program loading problems

Antony Barton
Intellectual 735 points

Hi everyone,

I wonder if someone could help me as im having big problems with loading programs onto my EVM5515 board.

I have tried using both the programmer included on the disc with the dev kit and the one offered on the wiki.

I first tried to get familiar with the process by cleaning the I2S EEPROM such that there is no program on boot, then reloading the demo code that came with the board, remembering to set the pll. Both of these steps were successful, but everything went bad from there.

The next program I tried to load (some of my own code)  then failed with the following output from the program, including the error:

Choose the device...
1<filepath> - NOR Flash
2<filepath> - NAND Flash
3<filepath> - SPI
4<filepath> - IIC EEPROM
5<filepath> - MMC
6<filepath> - SD
3E:\5515evm\EVM_Sample.bin
SPI...
Writing data to device...
Opening E:\5515evm\EVM_Sample.bin...
Input file opened
WRITE ERROR! at 0x00000000
Wrote 0x0003  Read 0x0000

This happens with any bin file I have tried, and on all target devices (although I have not tried MMC/SD).

Now, when I load my target configuration then try to connect I get the following error dialogue:

Error connecting to the target:
Error 0x80000244/-1143
Fatal Error during: Register, Initialization, OCS,
The memory at 0x00000000 continually indicated it was 'not ready'
All memory operations currently in progress were aborted in order
to regain control of the processor.
This is considered a catastrophic event, but the debugger should
still be able to access memory and CPU registers.
System state has been altered.  It is strongly advised
that the processor should be reset before resuming execution,

With cancel or retry as options. When I click retry, it then connects properly and I can debug code properly, but I still get the same check error when I try to load a program onto the flash memory.

Does anyone have any idea what is going on?

Any help would be appreciated!

 

 

 

  • 0
    TI__Intellectual 1755 points

    Antony,

    One thing you can do is run the cleaner.bin program to wipe out any bad data on the memory.

    If the error still occurs, the problem may be with the boot image. What settings did you use to create it?

  • 0 in reply to Juliana Mansell
    Intellectual 735 points

    Juliana,

    Thanks for the fast response.

    Yes, unfortunately I get the same problem when running cleaner.bin also.

    I used the command line suggested by the wiki, as follows:

    hex55 -i filename.out -o boot_image_file_name.bin -boot -v5505 -b -serial8

     

    ... Having just written this, cleaner.bin just functioned properly. I'm not sure what changed to allow this to happen as I had rebooted everything, but all seems to be fine now.

    Perhaps by loading debug code first and halting it the system (although im not sure I didnt try it that way before) was not getting stuck in some location somehow...

  • 0 in reply to Antony Barton
    TI__Intellectual 1755 points

    I'm glad you resolved the issue.

    Usually if you get that kind of error (Wrote:0x???? Read:0x0000) it means that there was data corruption while loading the code, and only after cleaning the peripheral (cleaner writes all 0x0000 to the memory) it will successfully program your EVM.

     

  • 0 in reply to Antony Barton
    Intellectual 735 points

    Upon further testing, it does seem to be my bin file causing all the problems as I was able to repeat it.

    I am not certain why my file does not work, I do set PLL registers in the beginning of my main code, etc. I am sure that it is something that I have not learned how to configure properly yet, but I'm glad I have got back to where I was anyway!