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.

DEV_createDevice ( or similar ) runtime device creation support

Other Parts Discussed in Thread: OMAP-L138

In another thread:

http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/115/p/12493/48979.aspx#48979

Mariana, a TI employee, referenced P107 of spru403o where it states that DEV_createDevice will not be supported above BIOS 5.32.

She subsequently stated that there was no supported alternative to this system call, and that as far as she knew, in future, TI would only support static device creation.

Robert, the user whom she was assisting stated this would be a big problem for him.

It will also be a big problem for us - for the same reasons as Robert's.

Static creation is fine if you always know the peripheral configuration. However, as in Robert's case, we do not - our application is composed of:

1 - a "Processor" board containing an OMAP-L138, ethernet, memory etc.

2 - one or more ADC or DAC boards, each with a Stereo ADC or DAC on it. These connect to the processor board via I2C ( for configuration ) and I2S ( for data transfer via the McASP ). They are field-installable, and we have no way of knowing at compile time how many will be installed, or what type they are, or which McASP "slots" they are connected to.

Our software needs to "discover" the I/O boards that are there and configure them at runtime. I cannot see any practical means of doing this without DEV_createDevice ( or something functionally equivalent ).

The IMPRACTICAL alternative would seem to be to have to have multiple DSP program images, one with each possible I/O configuration statically compiled into them, run a "Discovery" program to see what is there and then select an appropriate image to load. I wouldn't even want to consider having to do such a thing.

Would someone from TI please confirm the future of DEV_createDevice?

If it is to become unsupported, is TI really withdrawing support for runtime device creation? Or is there a functionally equivalent means of doing such configuration?

You'll understand that discovery of this thread has caused us considerable disquiet. We ( and Robert ) surely are not the only users of DSP/BIOS that need to do runtime device creation?

 

  • Alister --

    The original plan was to not support the DEV APIs in SYS/BIOS 6.x.   After feedback like yours, the requirements were changed.   SYS/BIOS 6.x now supports nearly all of the APIs from BIOS 5.x, include the DEV module.  The SYS/BIOS 6.x appendix summarizes the few exceptions.

    BIOS 5.41 is a proper superset of BIOS 5.32.  All of the APIs provided by 5.32 continue to be supported in 5.41.  We will continue to maintain and support BIOS 5.4x for foreseeable future.    Bug fixes and minor device variants will be supported in future releases.

    The document that Mariana mentions has since been updated to remove the warning.  

    The latest version is here:

    http://focus.ti.com/lit/ug/spru403q/spru403q.pdf

     

    Regards,
    -Karl-

  • Karl,

    Thank you very much for the clarification.