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.

SYS/BIOS Driver development

Other Parts Discussed in Thread: AM1806

hi all,

I am currently trying to develop a driver (library with RTSC) which has to do the following functionalities.

1.Handle hardware and software interrupt (that is Hwi , Swi ).

2.Also semaphore posting functionality in the interrupt handler.

Herein i am facing one issue :

        The hardware interrupt hhandling functionality does not seem to work when it is  implemented inside the library. Whereas if we implement

        Interrupt handler in the application , it gets called whenever the hardware interrupt is triggered.

 

QUERIES:

1. Do you see any issue in our approach of implementing the interrupt handler in the library.

2.It would be very useful if you can share some document which explains the following

                        a. Developing a driver (library with RTSC from scratch).

                        b. Modifying an existing library to add SYS/BIOS features like interrupt handling , semaphore creation etc

 

Regards

Shrish

  • Shrish --

    Which device and board are you using?   Which version of CCS and BIOS?   Are you using one of the TI SDK products?  

    Usually, the SDK's contain examples that you can reference.  Have you seen the SYS/BIOS User's Guide and the examples that come with SYS/BIOS?

    -Karl-

  • hi Karl ,

     

    sorry for not mentioning earlier  , im working on evmc6678l , bios 6_31_04_27 and MCSDK 2_00_00_11..

    The SDK has examples on how to write sys/bios application but not on driver development.

     

    it would be great if you could share documents on sys/bios driver development.

     

    Regards

    Shrish

     

  • Shrish,

    Were you able to find an example for writing a SYS/BIOS Driver? I working on an AM1806 and thought that perhaps it might be helpful. The information in the SYS/BIOS Interprocessor Communication Guide is not sufficent.