You have to reinstall the Shieldbuddy add in. The toolchain will be ok.
I did reinstall the Shieldbuddy add in but still had the same problem where the PC cannot find the driver.
BTW, also, the latest add-in gives the same problems with i2c devices like before, but this time, the problems are intermittent where a reset or power cycle causes the system to be stuck on reading the FRAM and/or EEPROM or read garbage from FRAM.
Can you please send me a link to the older ShiledBuddyIDE.exe that required the writre.cpp and wire.h. This version used to work fine ...
We have FRAM and the OLED running simultaneously on the same I2C pins.
I just returned form my trip and tested the new IDE. SAME PROBLEM! FRAM and OLED stopped working. When I recycle power or reset the board, there is no display and no FRAM.
"Sometimes", when I use the SB EEPROM (no FRAM), the OLED works. Mostly, the code stops on reading the SB EEPROM.
I am really frustrated because it seems with every step I take forward, I take two steps back. How can a micro-controller board keep having i2c errors?
I have scheduled another major test on Wednesday whose failure may well cause me to abandon the work I did with the ShieldBuddy over the last 9 months. Is there anyway you can tell me how to revert my settings to something that worked before? It was with the version that required me to add Wire.cpp which I tried again now but did not work.
Is there anything else I should do? It is clear that the updated i2c stuff is buggy and does not work. How can I revert to the old one?
Where are you located? It would be useful to run your application under the debugger to find out what is really happening with the new I2C driver. If you are using the ShieldBuddy Eclipse environment, this would be quite easy.