• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 579 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.

HWI error

shrish mv
Prodigy 180 points
Other Parts Discussed in Thread: TMS320C6457

hi ,

In the platform_lib library (platform_lib_evmc6678l library project) , I had hooked a hardware interrupt (simple GPIO) and built the library.

In my application i was triggering the GPIO (configured as a interrupt) with a pulse , but the Hwi was not serviced ? (earlier i had hooked the hwi in the application itself , and it worked) .

Please help me out !

(im using sys/bios version bios_6_31_04_27 on evmc6678 platform )

 

Regards

Shrish

 

  • 0
    TI__Genius 9915 points

    Hi Shrish,

    Can you give the portion of the code where you are doing the ISR?

     

    Thanks,

    Arun.

  • 0 in reply to ArunMani
    Prodigy 180 points

    hi Arun,

    Thanks for the reply.

    here is exactly i am doing.

    1) originally the  platform_lib_evmc6678l library project ("C:\Program Files\Texas Instruments\pdk_C6678_1_0_0_11\packages\ti\platform\evmc6678l\platform_lib") was not a RTSC project ...so i added a .cfg file and converted it to a RTSC project so that i can add SYS/BIOS support.

    2) i added my custom .c and .h files to the project and built the library ..tested the library by calling some functions (from an application which included this library) defined in my custom .c file ..working fine.

    3)in the .cfg file of the application i statically hooked a HWI (simple GPIO) and triggered it with a pulse...HWI isr was serviced properly.

    4)now i removed the HWI from the application and added it in the library .cfg file..built the library ...built the project ...HWI was not serviced ..

    What could be the mistake ? 

  • 0 in reply to shrish mv
    TI__Genius 9915 points

    Hi Sirish,

    Is there a specific reason why you want to move the HWI configuration into the library? We haven't tried it like this and I just want to make sure that this is a valid scenario.

     

    Thanks,

    Arun.

  • 0 in reply to ArunMani
    Prodigy 180 points

    hi Arun

    I want to move the Hwi configuration and the Interrupt routine to library so the overhead involved in context switching when function call from library is reduced ..( if hwi routine is in application ..and it calls functions from library , then lot of overhead is involved)

    I should have explained the whole problem earlier ...i have attached a picture which briefly describes the problem ( Hwi is not serviced )

    Also Is it valid to convert a existing library to a RTSC project and add sys/bios features (like semaphore_pend , Hwi etc) .It is possible as i have done it already.. just want to know if it is the right thing to do ?

     

  • 0 in reply to shrish mv
    TI__Genius 9915 points

    We haven't tested the platform lib like this. I would suggest to keep the platform lib flat and have all the HW interrupts in your application. This also makes sense as you can change the ISR based on your application.

     

    Thanks,

    Arun.

  • 0 in reply to shrish mv
    Intellectual 290 points

    I need to know the details of how this was done:

    3)in the .cfg file of the application i statically hooked a HWI (simple GPIO) and triggered it with a pulse...HWI isr was serviced properly.

    I am trying to use the GPIO pins to trigger interrupts, but I don't know how to tie the GPIO to the HWI (using the Event Id?).

    I am using:

    C6457
    bios_6_32_05_54
    CCS 5.1

    Can you help me out?

    Thank you,

    Brian

  • 0 in reply to Brian Lacy
    Intellectual 290 points

    There is a table of Interrupt events (Event IDs) in the TMS320C6457 datasheet (SPRS582B).  The table is Table 7-12 TMS320C6457 System Event Mapping.  You can use the designated event number to  set the hwiParams.eventId value..