Well after a few weeks of work, I may be there. The software component lefty to implement is the script manager. This is mostly software with a dependency on the Non-Voltaile Memory driver. Since that is working with the config data, what remains is verifying it works on the larger memory needs of the script manager.
The last problem child was the Bluetooth and the RN487x interface. First the UART driver did not work anything like the previous model. As a result the Tx function is blocking, kind of, for now. Not sure how important that is. In the RN487x implementation, I wait around for the CMD prompt before executing the next instruction. I could have the ISR process the flag the main loop when this happens, but this is only important on initialization. For now I am just going to leave it as an inline process that runs to completion.
The Rx function works like before with an ISR that processed the Rx queue from Harmony. I did have to use the Ring Buffer implementation. The normal implementation required that you submit a read request, instead of just using the call back when a byte came in.
There was another problem, but this had to do with Android software I had thought I had solved this problem several years ago, but it came back. It has to do with how many bytes are transmitted when writing a Bluetooth Characteristic. Once transmit 8 (the maximum I set up), then in that session it will always transmit 8. If you send 4 bytes, it will just stuff the other 4 bytes with the last 8 byte transmission. You can read about this issue here.
Time to move on and finish this to the point I can start to assemble the new PCBs. I have a place for at lest on of these 15 channel LED controllers.
No comments:
Post a Comment