LAUNCHXL-F280049C: LAUNCHXL-F280049C

Chris,

Thank you for your response, however the examples provided, which were supposed to be for the F2800049C but instead were written for the F2800049M. I found out only by looking at Target Config.

The blinky was one of the ones that failed to upload. However, some of those did get uploaded but still not for the C version. Im thinking they might have caused some firmware corruption.

Darryl 

Darryl

The C2000Ware examples may say F280049M but with a different target config work on F280049C. The examples aren't designed for a specific version of F28004x.

Best regards

Chris

Chris,

Those programs may have worked elsewhere but they error'd out on me. Please read the first thread, link at the top. It might help you to more fully understand the trouble I'm having.

Below you will see two captures. The first one is the proper initial state after upload. It's a bit hard to see but the left block is a single zero. The right block reads ".005". This is how it boots correctly from ccs .

The next capture it the state after which I press the on board reset button with the board disconnected from the PC but powered otherwise. The four leds on the far right are flickering but you can't tell from the photo. And it reads 0  .086 and those numbers flicker as well.

This is why I think the firmware or the memory on the board is somehow corrupted.

I need to know if TI can supply me a flash utility along with a firmware file and instructions. Where do I find these items? Or who shall I ask? If I can't fix this board, I'll have to buy another. (waste of money and time)

Any help is appreciated

Darryl

Darryl

I've reviewed your previous thread, is all that resolved? Not clear how they may be affecting you now.

Can you load the application with debugger, perform a debugger reset through CCS, configure the emulation boot (to flash I assume for you app) and then run? I'd like to know if your application is working properly when booting through boot code.

The flash utility is in CCS, until Tools at the top when connected to the device. You can erase flash with that.

If it works when after running through boot and erasing flash doesn't resolve it. It could possibly be a hardware issue, in which I'll bring in other experts.

Best regards

Chris

hey Chris,

I'm pretty sure what was the problem. First let me say that I marked the last thread resolved because I no longer needed to work on the examples. I had been waiting for all the components to arrive and when they did I stopped playing with examples and began assembly and proofing the program.

At that point I discovered the problem that started this thread. That is, that I could download a fresh program and without rebooting the board I could see behavior. But then if I reboot the board I would see different behavior.

Tonight I found the erase function and preformed it several times. I then re-loaded the program and it preformed perfectly. I then rebooted the board and now nothing happens. It does not boot up because the program I loaded would reside in volatile memory and thus rebooting erased the program. Yesterday when I  would upload and reboot I got some behavior as I said before. I believe that there was part of my program stuck in non-volatile memory or flash memory. However, today, since I erased the flash memory, I can upload and the program executes properly. But then I reboot and it does not function at all. As if there is no program loaded. I think that's because I erased it.

Does that sound possible or am I reaching?

So now I need to find out why I can't retain the program in memory. Should I start another thread to address this problem??? (just joking)

I may have a hardware problem after all.

I look forward to your thoughts.

Darryl

Chris,

Thank you so much for your help. It's working again. hurray!

Darryl