Are there conflicts with Starterware's use of interrupts or cache with DSP/BIOS? I am hoping to integrate the Starterware USB libraries into my existing DSP/BIOS-based project.
Thx,
MikeH
Mike,
We don't recommend mixing the StarterWare and DSP/BIOS APIs for interrupts and/or cache in the same application. That said, there should not be any issue using StarterWare (including the peripheral driver and USB stack libraries) in DSP/BIOS applications.
Please let me know if you encounter any difficulty, and I will do my best to help you resolve it.
Please click the Verify Answer button on this post if it answers your question.
Joe,
Joe CoombsPlease let me know if you encounter any difficulty, and I will do my best to help you resolve it.
This appears to be related to the mixed use of DSP/BIOS and Startware, but I can't tell for sure. Can someone take a look?
http://e2e.ti.com/support/embedded/f/790/t/147423.aspx
I'm not sure whether or not the issue in the linked thread is related to the combination of StarterWare and DSP/BIOS. I took another look at the USBLIB source code, and I don't see any place where the library could be enabling an interrupt "behind the scenes." It looks like the only interrupt-related actions taken in the USBLIB are:
So, it should be safe to use the USBLIB with DSP/BIOS even if you use BIOS to setup and control your interrupts for the overall application. I will need to do some more testing to make sure there are really no issues here.