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.

Developing application code with DRV8312-69M-KIT

Other Parts Discussed in Thread: MOTORWARE

I am trying to get started with developing an application in SYS/BIOS on a DRV8312-69M-KIT platform and have been trying to toggle the STATUS LED in the IDLE task so that I can observe how long the IDLE function is interrupted for things like clock interrupts.  The tutorials have been somewhat helpful but are based on another platform and assumptions.  Are there any SYS/BIOS based examples specifically designed for this platform that I can use as a template?  If not, are there some basic pieces such as an RTSC platform file for the DRV8312-69M-KIT?  Any other recommendations?

Thanks,

dmh

  • Mitch,

    I'm going to move this topic to the BIOS forum, I think you will get better responses there. I'm also interested in having someone with that expertise show an example of how to pull in a MotorWare project to a BIOS framework.  It's something that has been on our to do list, we just haven't quite executed yet.

     

  • Hi dmh,

    There are several C2000 examples that ship with SYS/BIOS.  If you select "project -> create new CCS project" you should see these under the project templates for SYS/BIOS.

    Steve

  • I will try these examples. I am not sure they will help me get past the knowledge gap I'm struggling with, however.  In trying to debug a very basic SYS/BIOS application where I run a function called from IDLE, I can't place more than one breakpoint and I cannot single step with a single breakpoint in the code without getting the following error in both cases:

    C28xx: Trouble Setting Breakpoint with the Action "Continue or Finish Stepping" at 0x3dab46: (Error -1066 @ 0x3DAB46) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.1.73.0) 

    I am wondering if it has to do with where the program code resides (hence "verify that the breakpoint address is in writable memory") but there does not appear to be a NTSC platform file which, as I understand it, is where these settings would reside.  Having such an NTSC platform file for the development platform I'm using would help me understand what it looks like in that situation and then I could more easily move to a custom hardware platform.  

    Thanks for your help,

    Mitch

  • Mitch,

    These devices can have a total of two hardware breakpoints, one of which is taken by main by default (this is how the run to main functionality works).  You can turn off the main breakpoint in the debugger settings which will allow you to use two breakpoints simultaneously.

    The platform file is actually more specific to the embedded processor you are using not so much the board.  You ought to be able to use the standard F28069 platform file for this SYS/BIOS project.

  • Hi Mitch,

    Mitch Hanks said:
    Having such an NTSC platform file for the development platform I'm using would help me understand what it looks like in that situation and then I could more easily move to a custom hardware platform.  

    Have you seen the platform wizard?  This tool will help you define a custom platform file, in which you'll be able to (re)define the memory segments and tune cache settings.  It would be very helpful for creating a platform that matches your custom board's memory layout.

    Steve