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.

TMS320F28379D: Is the DesignDRIVE Kit required to test Build Levels 1 through 3? & a few more questions

Part Number: TMS320F28379D
Other Parts Discussed in Thread: DESIGNDRIVE, , TMDSDOCK28379D, TMDXIDDK379D, C2000WARE

Hi,

I'm currently using the TMS320F28379D with the TMDSDOCK28379D Experimenter's Kit. I have the control card using the usb debug probe along with the On-Card xds100v2 Emulator, and I am trying to test the fcl_f2837x_tmdxiddk project. When I run the debugger, and switch to real-time after restarting the CPUs, hitting restart, and importing my variables, I flip the enableFlag from 0 to 1, but nothing happens. isrTicker doesn't even increase, which should denote that time has passed since enableFlag has been initiated. I am wondering if the designDrive kit is required and you can't just test this on the standalone card.

I also seem to get this warning "#10462-D Symbol, "Q_cla", referenced in "./sources/fcl_cpu_code.obj", assumes that data is blocked but is accessing non-blocked data in "./sources/fcl_cla_code.obj". Runtime failures may result." and I've seen previous forums say to update the C2000 compiler, which I have done.

Lastly, is this an issue that could cause problems? 

"C28xx_CPU2: Trouble Removing Breakpoint with the Action "Finish Auto Run" at 0xd6cc: (Error -1066 @ 0xD6CC) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.2.0.00002)"

How do I remove breakpoints? I have it set to skip all breakpoints, but it still hits this.

Thank you,

Josh

  • You have to click Continuous Refresh in the Expressions debug window to see the variables continuously updating.

    You can ignore the message abouit Q_cla.

    The example project does not use CPU2, and should not load any code there. Pls follow the user guide.

  • Doesn't seem to work with continuous updating enabled. I will sometimes get an issue that says something is already running on the CPU when clicking restart even after resetting the CPU.

  • When you halt the CPU is it just still waiting for enableFlag or has it jumped somewhere else and gotten stuck?

    Whitney

  • I am not sure if it is getting stuck. I would assume it shouldn't be because I reset the CPU, which pauses the CPU then I hit restart and it reruns the program. Do I need to have the designDrive Kit TMDXIDDK379D?

  • When you hit the "Suspend" button in CCS to halt the execution, it should show you what line of code it stopped on. If you do that, what line is shown? Or does it give you some sort of "no debug information available" error?

    The example code is designed to work with the TMDXIDDK379D, yes. Without the IDDK board attached, you should be able to set the enableFlag and get the isrTicker to start incrementing, but I don't think you'll be testing anything more meaningful than that.

    Whitney

  • I solved the issue by reinstalling the C2000ware sdk and opening a new project using the same folder, but this time I selected only the first CPU when debugging.

    In terms of the IDDK, is there any way TI would be willing to lend a kit for my team's Electrical & Computer Engineering Senior Design project at University of Illinois Urbana-Champaign? One of our members is the Senior Electrical Advisor for Illini Formula Electric and we are designing a drive inverter capable of being efficient and low cost for our project. This project is out of the scope of our Senior Design course, but they still allowed us to tackle the challenge given our skill sets. 

  • I'm not sure I'm going to be able to help you there. We do provide a bunch of hardware files in the SDK that you can use as a reference if you haven't seen those. They're under solutions\tmdxiddk379d\hardware\IDDK_HwDevPkg_r2.2.1

    Whitney