#PICDESIGN BACKPACK HOW TO#
#PICDESIGN BACKPACK SERIAL#

The good thing is, the basic communication protocol is the same as the 2110, so the efforts so far are interchangeable. Make the Prop an I2C slave like you said, and have direct access to the EEPROM to write it for firmware updates. I think the Cp2112 is a great idea, Silabs suggested the same today.

We also counted chars out/back, as we found some code/settings combinations dropped chars. You can see low bauds send continually, and as the requested baud climbs, the finite engine speed starts to slip to the next bit slot.Дuplex (simple readback) has more overhead that shows on higher bauds. I dug about and found my test notes from CP2105 testing (VCP driver) so it will be interesting to compare the CP2110 speeds via HID, when you have it working.Д¬P2105 File of LOOP BACK b413 Right-click Paste I have a test board in the works for the SiLabs>Prop tester, which is a week or so out if anyone is interested let me know I will send it if someone wants to work on this.

#PICDESIGN BACKPACK SERIAL#

Here is some serial loader info Mike Green posted, but this is surely way over my head. The odds of crashing during an I2C eeprom transfer from higher address to lower address are small. The field replacement will always be with my own mac/pc GUI, so it is not such a big deal to me to handle the Prop load protocol. For shop development, there can be a FT232 based board if the Silabs is not going to be programmable via BST(bstl). The real goal is a driverless field replaceable firmware method with my own GUI. If it is too much work to tackle, then the other will be to just upload 32k to spare eeprom space from my own GUI, verify the transfer, then move the 32k to eeprom bootload space.

#PICDESIGN BACKPACK HOW TO#

I will have this tomorrow and am looking for info on where to start learning how to make this work for a Prop loader direct out of BST or other IDE.

Picdesign backpack