-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
using Wire1 on the core v 2.0.5 [probably needed to program the Artemis Global Tracker] #347
Comments
Ok, looking here: Arduino_Apollo3/libraries/Wire/src/Wire.h Lines 68 to 85 in fbb2eac
and there: Arduino_Apollo3/libraries/Wire/src/Wire.cpp Lines 161 to 178 in fbb2eac
gives me good hope that this should be an easy fix. |
Ok, got some help on the tracker website, it should be possible to set up a I2C with custom pins, looking at it now. |
Ok, more problems coming up due to wrong pinmaps; taking the discussion on the Global Tracker issue though, feel free to help there. |
This is probably another symptom of the same bug.
|
Alright. I went back thru the targets and added wire interfaces for some of the Wire interfaces that were labelled on the board but not defined in the software. This means that @jry-slc Wire1 should be available on the thing plus without you needing to define it yourself. I wanted to clarify how to define a custom Wire when we don't have one defined on the pins you would like already.
|
I think (to be confirmed there by the experts :) ) that I need to be able to access specifically Wire1 to be able to use the GPS on the Artemis Global Tracker (see issue sparkfunX/Artemis_Global_Tracker#18 ).
In the core v 2.0.5, doing:
as was doable in the core v1 seems to be impossible:
The text was updated successfully, but these errors were encountered: