jimmie
Junior Member
Posts: 86
|
Post by jimmie on Nov 8, 2019 8:02:26 GMT
My development has come to a dead stop!
Due to problems with the old variants.h file, I made the mistake of upgrading to toolchain 4.9.3. I have also obtained a new license which I placed in the licenses folder. I deleted the old 4.9.1 license.
Now I can not compile anything due to the error: license check: No valid license!
|
|
|
|
Post by Admin on Nov 8, 2019 10:14:15 GMT
Please contact Hightec's support at support@hightec-rt.com!
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Nov 15, 2019 15:33:08 GMT
Please contact Hightec's support at support@hightec-rt.com!
Thank you.
I contacted Technical Support and they upgraded my license.
But now, all my i2c devices are not working. The program would compile fine but then all i2c devices were not working. I then spent several hours debugging the board, solders and so on and could not find anything. I found out that the ShieldBuddy installed had the old version(for 4.9.1). When I updated to the latest version, I am now getting the compile error "SerialClass2" has not been declared.
Then I tried to reprogram the board with another machine that has 4.9.1 and everything came back alive.
=========================================
Since 4.9.1 was working just fine, how can I downgrade given that the license is for 4.9.3?
|
|
|
|
Post by Admin on Nov 15, 2019 16:09:58 GMT
You will no longer need:
#define HardwareSerial SerialClass2
You can use the standard leddar library source code. We have tested the ShieldBuddy with the Leddar examples and they all compile now.
It seems strange that the I2C has stopped working. Which I2C pins are you using?
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Nov 15, 2019 23:45:25 GMT
You will no longer need: #define HardwareSerial SerialClass2 You can use the standard leddar library source code. We have tested the ShieldBuddy with the Leddar examples and they all compile now. It seems strange that the I2C has stopped working. Which I2C pins are you using?
Thank you, will try it.
I am using the standard pins, SDA and SCL. I have two i2c devices that worked fine with 4.9.1 but both stopped working with 4.9.3.
|
|
|
|
Post by Admin on Nov 16, 2019 15:02:16 GMT
This changed in the last release. The default was SDA and SCL but it was changed to SDA1 and SCL1. Make sure that you set the I2C to use SDA and SCL. These are pins 20 and 21 on the ShieldBuddy.
E.g.
Wire.setWirePins(UsePins_20_21); // Default pins for Arduino Due/MEGA
Wire.begin();
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Nov 18, 2019 1:36:18 GMT
This changed in the last release. The default was SDA and SCL but it was changed to SDA1 and SCL1. Make sure that you set the I2C to use SDA and SCL. These are pins 20 and 21 on the ShieldBuddy. E.g. Wire.setWirePins(UsePins_20_21); // Default pins for Arduino Due/MEGA Wire.begin();
Thank you for letting me know.
I am extremely puzzled as to why that change was made?! There appears to be a complete disregard to the havoc this causes to the ShieldBuddy customers!
I have two i2c devices, a SH1106 OLED and an i2c FRAM memory (https://www.adafruit.com/product/1895). Both had stopped working.
I included the code above but now the screen is garbled and the FRAM memory reads junk. I have attached the OLED library and the FRAM library and would appreciate your help is finding out what is going on.
Thanks again for all your time and help. .
|
|
|
|
Post by Admin on Nov 18, 2019 9:18:20 GMT
The version you have is not formally released and was for testing the Leddar solution. In this test version, the I2C driver has been completely re-written as there were some issues with the original one. We will test the new I2C driver with the SH1106 and FRAM to see what the problem is. The default I2C pins will be put back to SCL and SDA. It will take a few days to get the FRAM and OLED for testing. You can put the old I2C driver back by copying these files to: C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\libraries\Wire and C:\Program Files (x86)\Arduino\hardware\aurduino_Dx\aurix\libraries\Wire Wire.cpp (8.28 KB) Wire.h (3.28 KB) |
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Nov 18, 2019 11:27:50 GMT
I will try your solution immediately.
You say "....The version you have is not formally released". Which version of which program are you referring to?
Thank you.
=========================================== |
|
|
|
Post by Admin on Nov 18, 2019 11:29:37 GMT
The version is the ShieldBuddy add-in, not the compiler.
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Nov 18, 2019 11:43:35 GMT
Update:
I replaced the wire.h file and added the wire.cpp file to the two directories above but the problems persists. The screen remained garbled.
|
|
|
|
Post by Admin on Nov 18, 2019 13:05:18 GMT
Try copying Wire.cpp to:
C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\variants\tc275
And;
C:\Program Files (x86)\Arduino\hardware\aurduino_Dx\aurix\variants\tc275
It seems that the Arduino IDE no longer compiles .cpp files located elsewhere!
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Nov 19, 2019 1:56:27 GMT
Try copying Wire.cpp to: C:\Program Files (x86)\Arduino\hardware\aurduino\aurix\variants\tc275 And; C:\Program Files (x86)\Arduino\hardware\aurduino_Dx\aurix\variants\tc275 It seems that the Arduino IDE no longer compiles .cpp files located elsewhere!
Thank you. This approach worked and now the FRAM and OLED work.
===========================
On a separate issue, I thought I was having memory corruption problems but it was related to a bug in my own code.
Thank you again for your help.
Will there by any updates to fix the i2C problems above?
|
|
|
|
Post by Admin on Nov 25, 2019 11:47:56 GMT
|
|
jimmie
Junior Member
Posts: 86
|
Post by jimmie on Nov 27, 2019 10:24:41 GMT
Thank you. This is great news.
Should I delete the wire.cpp files added per your instructions above or will the new ShieldBuddyMulticoreIDE.exe restore everything?
|
|
