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.

failed to load program to DSP RAM via emulator: data verification at address 0x8023

Other Parts Discussed in Thread: CONTROLSUITE

Hi, guys, I'm thirsty for your help!

Recently I have been suffered from the the problem described in the title. Actually I tried to change the CMD file like below:

Replace 

RAML0 : origin = 0x008000, length = 0x001000
RAML1 : origin = 0x009000, length = 0x001000
RAML2 : origin = 0x00A000, length = 0x001000
RAML3 : origin = 0x00B000, length = 0x001000

by

RAML : origin = 0x008000, length = 0x004000

Then, the error indication would change from "data verification at address 0x84AC" to '"data verification at address 0x8023". I don't understand the difference between those two above.

Btw, the initial error is "data verification at address 0x8000", it just changed after do power reset.

I'm confused by this phenomenon, why? In my opinion, this kind of error will appear because of CSM. Then, why it will transfer to other address within RAML0 ?

How can I load the program to RAM successfully?

Thanks for any help sincerely!

Wenlong Lee

  • What device and CCS version are you using?  If you're trying to load to flash and your CCS does not have the flash plugin for the device you are using I believe you may see this error.

    Kris

  • Sorry for my indefinite description. I'm using F28335 and CCS 3.3 with all update installed.

    I just try to debug my program via emulator -- I'm trying to load the program to RAM.

    Thank you for your further help.

    BR/ Wenlong Lee

  • Assuming you haven't programmed CSM passwords and you are using the correct linker command / GEL files (designed for F28335), then you probably just need to read the CSM password locations to unlock the device.

    Read the CSM Password locations at 0x33FFF8-0x33FFFF to unlock L0 (0x8000) so you can load to it.  There may be a GEL function which performs this as well.  See the System Control user's guide for your device for more details.

    Kris

  • Hi, Kris Parrent

    I have found the dummy read code in the .gel file used in my project.The GEL function also write 1 to all the bits in CSM.

    My device is a new one. I didn't use the CSM in my project till now.

    I'm quite confused by the change of address in the error indication, from "data verification at address 0x8023" to "data verification at address 0x84AC"? How it can be this?

    Then, is there any other reason for this kind of error?

    Thanks a lot for your help!

    Wenlong Lee 

  • In modern day CCS, you can run the GEL function at anytime by going to a scripts menu and selecting the function.  This should exist somewhere in 3.3 as well.  Can you try to locate this, and explicitly run the unlock CSM function prior to loading?  If you look at the password locations in the memory browser, what do you see programmed there?

    Is this a custom project or a controlSUITE project?  If custom, is it possible you are overrunning the allocated RAM space?  Can you try loading a controlSUITE project to verify it works properly?

    Kris

  • Hi, Kris

    I have just manually run the unlock function as you said, however, there is no effect. And I also watched the CSMSCR register and noticed that the SECURE bit is always 1. And all PWL registers returened 0x0000. Does it mean that the device has been locked, even permanetly locked? 

    I'm sure I did no other actions except load program to RAM. Then how it can be this?

    As for controlSUITE project, I don't found any project having the .pjt file under the directory of controlSUITE. there are only .project file. Is the problem of CCS's version?

    Thanks a lot.

    Wenlong Li