• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 694 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Setting SYS/BIOS up to use C674 instead of C64P

Kevin Elwood
Prodigy 100 points

Hello,

I am using CCS 5.5 and am new to SYS/BIOS. I have always used DSP/BIOS. I am trying to create a project that will allow me to use either processor on the OMAP L-138/C6748 device. I have setup my project to use the C674 processor at this time. When I add hardware interrupt definitions to the project I am running into problems. I am attempting to define an interrupt handler for interrupt 94 (UPP) of the device. SYS/BIOS is throwing an error since this interrupt level is outside the bounds of the C64P processor. I don't want to use the C64P, I want to use the C674 processor. I do I get SYS/BIOS to not use the C64P device?

Thanks in advance

Elwood

  • 0
    Prodigy 100 points

    More info....

    When I click on the C674 hyperlink under the Target Specific Support area of the SYS/BIOS tool, I can get to the setup screen for the C674

    But when I click the Hwi hyperlink, I am vectored off to the screen for the C64P.....

  • 0 in reply to Kevin Elwood
    Prodigy 100 points
    I have found the answer to one of my problems. I was inputting the event number into the interrupt number. Once I set the event number (94 for uPP) and set the interrupt number to the proper value, I am no longer receiving the error message.

    I do not however understand why the C64P target specific support comes up for exceptions, hwi, cache, event combiner, and memory protect instead of the C674.
  • 0
    TI__Mastermind 32475 points
    All C674 and C64P share the same Hwi module. On these C6000 parts, there is only 12 available hardware CPU interrupts. You can route any event betwee 0-127 to any of these 12 available interrupt. Please see the cdoc in your installation for more details.

    You can't create an interrupt 94 but you can route event 94 to 1 of the 12 CPU interrupts. I think that's what you want to do right?

    Judah
  • 0 in reply to judahvang
    Prodigy 100 points
    Thanks, I have already made the appropriate change.