|
|
Post by Admin on Nov 27, 2019 10:25:33 GMT
Please delete the wire.cpp files!
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Nov 28, 2019 20:58:45 GMT
Please delete the wire.cpp files! Thank you. Will do.
After also upgrading Arduino IDE to 1.8.10, my system is no longer finding the "DAS JTAG Shiledbuddy TC275" driver.
Do I have to reinstall the toolchain?
Thanks again.
|
|
|
|
Post by Admin on Nov 28, 2019 21:01:22 GMT
You have to reinstall the Shieldbuddy add in. The toolchain will be ok.
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Nov 29, 2019 22:50:34 GMT
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 ...
OR is there a "cleaner" way of update the add-in?
Thanks again.
|
|
|
|
Post by Admin on Nov 30, 2019 8:01:55 GMT
This is strange because the i2c driver sends a stop condition after reset to release any devices on the bus.
We will test this again.
You can reuse the wire.cpp and wire.h that you were using to go back to the earlier driver.
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Nov 30, 2019 15:07:02 GMT
This is strange because the i2c driver sends a stop condition after reset to release any devices on the bus. We will test this again. You can reuse the wire.cpp and wire.h that you were using to go back to the earlier driver. Thank you.
Once wire.cpp is added in variants/tc275, the Arduino compiler does not compile the sketch giving the error "Error Compiling for board ShieldBuddyTC275_Dx".
When wire.cpp is removed from there, the sketch compiles.
==============================================================================
BTW, do I also need to delete wire.h from
C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\libraries\Wire
and
C:\Program Files (x86)\Arduino\hardware\aurduino_Dx\aurix\libraries\Wire
Attachments:debug.txt (16.23 KB)
|
|
|
|
Post by Admin on Dec 1, 2019 15:10:10 GMT
You can put the old I2C driver back by copying Wire.h to:
C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\libraries\Wire
and
C:\Program Files (x86)\Arduino\hardware\aurduino_Dx\aurix\libraries\Wire
The copy Wire.cpp to:
C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\variants\tc275
and
C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\variants\tc275
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Dec 1, 2019 19:14:55 GMT
You can put the old I2C driver back by copying Wire.h to: C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\libraries\Wire and C:\Program Files (x86)\Arduino\hardware\aurduino_Dx\aurix\libraries\Wire The copy Wire.cpp to: C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\variants\tc275 and C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\variants\tc275
Thank you.
I meant to say in my last post that when I did that (copied Wire.h and Wire.cpp) to the locations you mentioned, Arduino fails to compile the sketch. When Wire.cpp is removed, the sketch is compiled.
|
|
|
|
Post by Admin on Dec 2, 2019 10:48:00 GMT
We can reproduce the problem with the hang-up with the FRAM if a reset of the TC275 occurs. We have implemented the recommended solution to this from the FRAM datasheet and this seems to work.
Please download the ShieldBuddy add-in again and see if it fixes your problem,
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Dec 2, 2019 16:16:34 GMT
We can reproduce the problem with the hang-up with the FRAM if a reset of the TC275 occurs. We have implemented the recommended solution to this from the FRAM datasheet and this seems to work. Please download the ShieldBuddy add-in again and see if it fixes your problem,
Thank you very much. This is good news. Will this update the problem with the OLED display. I am not sure if the i2c display also stopped working or if it was because of the FRAM problem ..
I am traveling and will try it as soon as I can.
|
|
|
|
Post by Admin on Dec 5, 2019 20:56:42 GMT
We have FRAM and the OLED running simultaneously on the same I2C pins.
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Dec 16, 2019 2:39:51 GMT
We have FRAM and the OLED running simultaneously on the same I2C pins. Hello,
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?
Any help is appreciated.
|
|
|
|
Post by Admin on Dec 16, 2019 9:14:13 GMT
This is really weird. We have tested this specifically and it works with the new I2C driver on our rig with resets and restarts. Here is the current ShieldBuddy library built with the old I2C driver: www.hitex.co.uk/fileadmin/uk-files/downloads/ShieldBuddy/libAurduino.aCopy this to: C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\variants\tc275 adn; C:\Program Files (x86)\Arduino\hardware\aurduino_Dx\aurix\variants\tc275 You will need to use the old Wire.h: Wire.h (3.28 KB) Copy this to: C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\libraries\Wire and; C:\Program Files (x86)\Arduino\hardware\aurduino_Dx\aurix\libraries\Wire 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. |
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Dec 16, 2019 11:43:15 GMT
Thank you. I have replaced the Wire.h file with the one you sent along with the .a file as you described (I have never used Eclipse). After compiling with the Arduino IDE, the Serial monitor is showing all garbage characters so it is worse than before.
Is it useful to start from a clean install of the ShieldBuddy? What should I uninstall? I am located in the United States (EST) and available tomorrow any time. |
|
|
|
Post by Admin on Dec 16, 2019 11:46:48 GMT
Just copy libAurduino.a to:
C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\variants\tc275
and;
C:\Program Files (x86)\Arduino\hardware\aurduino_Dx\aurix\variants\tc275
This file contains all the ShieldBuddy drivers pre-compiled into a library to speed up the compilation. This is a special version that uses the old I2C driver.
|
|
