Re: A ¡°pluggable¡± firmware architecture?
|
Hello Mike
I think it's a nice idea but I don't know how to accomplish that in practice. What you're talking about is kind of the old PC "DLL" concept. Native code that has to be in a relocatable library. Not just that but there then has to be some way to load it onto the Flash - which can't be done in any way I know of, certainly not with the current bootloader. There are a lot of obstacles to that and again, I think the idea might not be easily transferable?to a small microcontroller system. The BASIC runs in a Virtual Machine not natively on the CPU. So how you bridge that gap, and how you construct microcontroller DLL's and how you get those into the Flash, those would be a lot of complex problems to solve.?
Here's a related (potentially "bad", I don't think so) idea.
Will there be a way to build our own "native" functions that can be called from QPRLabs BASIC?
Specifically, could it be possible to write our own optimized functions in C or assembly for STM32 and "link" them with a BASIC program or register them from BASIC?
That would potentially enable us to add our custom signal processing blocks to your pipeline.
For example, if we have a noise suppression algorithm that we particularly like it might let us (with proper hooks provided by you) insert it into the audio pipeline.
If we screwed something up then, say, a firmware reset could remove the registered custom components, and restore to the default pipeline.
What do you think?
?
73, Mike KK7ER
?
|
