CCS/TM4C1294NCPDT: Falsely behavior when using UniFlash against CCS debugging

Volker,

First, can you state the exact version of CCS and UniFlash you are using?

After that, there is a couple of things we can try to start off:

1. In both the CCS and UniFlash case, can you try to initialize a standalone verification after loading you .out file. In UniFlash, there is a "Verify Image" button next to the Load button. In CCS, you can go to 'Run -> Load -> Verify Program...' You might also want to turn on "Full Verification" first under 'Tools -> Debugger Options -> Program/Memory Load Options'.

You can also try loading with CCS and verifying with UniFlash and vice versa just to make sure both tools are loading the same application onto your device.

2. Another thing to try is to import the CCXML you are using from CCS into UniFlash just to make sure you are using the same configuration to talk to your device.

Hopefully we can find some differences during these steps, as in general CCS and UniFlash should load your program the same way otherwise.

Thanks,
Ricky

Hi Ricky,

thanks for your input and your quick reply. Unfortunatly your advice did not solve the thing:

1. All combinations of loading and verfication did pass successfully, even loading with the UniFlash tool and verifiying with CSS
2. Loading the target configuration file with UniFlash also did not solve the problem

However, I have some further questions:
a) The difference between the two methods is the memory section it is loaded in (Flash vs. RAM), isnt it?
-> I recognized that in both cases the image is loaded into the flash memory...

b) Is it wanted that I have to power cycle my device after flashing the out.File with the UniFlash tool?

c) coming along with the conclusion of point a) I realized that it does not depend on the flashing method. Furthermore it depends on the state of the controller: running powered up via CCS it works, after a power cycle it provides the error mentioned above...

Thanks in advance,
Volker

Volker,

b) UniFlash disconnects from the device after program load. That's probably the main difference between CCS and UniFlash, as CCS remains connected to the device after program load so you can debug your application. If you want to run the program you loaded in UniFlash, you can power cycle your device.

c) If power cycling your device results in errors, maybe there are some problems with your program (ie; relies on volatile memory), or with your device's boot settings?

Thanks,
Ricky

Hi Ricky,

b) I see, so it is mandatory to power cycle the device – besides of a reset.
c) Your points here sound interesting. I assumed that loading procedures regarding the memory sections should be the same – not dependent on the state of the controller (already running – startup). What leads to my question:
d) What points do you have in mind when talking about problems with boot settings?

Thanks again,
Volker

Hi Ricky,

ok, i will see whether your collegues there can help me.

Anyway, thanks for all of your help,
Volker