Open trlafleur opened 5 years ago
Sorry, I've been busy on a project. My colleagues will try to help with some of this; otherwise I'll try to reply over the weekend.
Thanks....
On Fri, Jun 7, 2019 at 7:30 AM Terry Moore notifications@github.com wrote:
Sorry, I've been busy on a project. My colleagues will try to help with some of this; otherwise I'll try to reply over the weekend.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mcci-catena/Catena-Arduino-Platform/issues/172?email_source=notifications&email_token=ABC4EK3WPB7SIQNGJMEAQFDPZJWJTA5CNFSM4HTBEGQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXF7XQA#issuecomment-499907520, or mute the thread https://github.com/notifications/unsubscribe-auth/ABC4EK4RIB7PJ3YLCPHTSALPZJWJTANCNFSM4HTBEGQQ .
--
~~ /) ~~~~ /) ~~ _/) ~~ _/) ~~
Tom Lafleur
Hi @trlafleur, Please find our answers inline in this comment.
The log message "LoRaWAN init: ?CatenaBase::GetProvisioningStyle: failing" represents that the network parameters(appeui, deveui and appkey) are not configured. This message comes from "CatenaBase_GetProvisioningStyle.cpp" in the Catena-Arduino-Platform library.
https://github.com/mcci-catena/Catena-Arduino-Platform/blob/553dd7f81c236699e91161d18b76a9bca5bb5a90/src/lib/CatenaBase_GetProvisioningStyle.cpp#L82-L89Unfortunately, you cannot re-assign the USB Serial to Generic Serial with the current version of Board Support Package.
Yes, we have a list of Operatingflags and you can find them in "CatenaBase.h" of Catena-Arduino-Platform library.
https://github.com/mcci-catena/Catena-Arduino-Platform/blob/553dd7f81c236699e91161d18b76a9bca5bb5a90/src/CatenaBase.h#L144-L152Hardware design documents can help you in this case, you can find them from our Github repository "HW-Designs". Please refer the schematic of Catena 4460 sensor shield.
https://github.com/mcci-catena/HW-Designs/blob/master/Boards/Catena-4460/100001204b_(Catena-4460-MCCI-LW-Feather-Sensor-Shield-Schematic).pdfWe are working on your other question on FRAM. We will get back to you soon with the answer.
Best Regards, Dhinesh
The 2k FRAM support comes from a separate library, which we forked from adafruit: https://github.com/mcci-catena/Adafruit_FRAM_I2C. The address is set in the begin() routine, Adafruit_FRAM_I2C::begin(); if the input address is 0, the hardware default is used.
So you have to change: https://github.com/mcci-catena/Catena-Arduino-Platform/blob/553dd7f81c236699e91161d18b76a9bca5bb5a90/src/lib/Catena_Fram2k.cpp#L77-L79
to be:
if (! this->Super::begin() ||
! this->m_hw.begin(MY_I2C_ADDRESS, &Wire))
return false;
Define MY_I2C_ADDRESS to the address you're using on the board, and this should work.
On the SAMD BSP, it is possible to use Serial1. See how I do it in the https://github.com/mcci-catena/Modbus-for-Arduino/blob/master/examples/catena_simple_host/catena_simple_host.ino. You will have to figure out how to substitute Serial1 for Serial as needed. Once you do that, things should work; we've tested the command framework on other boards that use HW serial. There may be software compatibility issues with Serial1 vs SerialUSB, namely the while (! Serial)
idiom. On our STM32 BSP, we added a !
operator on the UartSerial ports (returning constant true
). We can consider doing that for the SAMD as well, but that's a separate ticket.
1) I'm using a 4460, but need to add an I2C device at addr: 0x50 where the Fram is located... I see the FRAM8K driver and it has its address defined in the Mb85rc64ta.h file, so I can change it there, but for completeness, I do not see the same for the Fram2k. I can re-address the part on the board, but what do I need to change to select the FRAM64 device in the 4460 code base?
Just change the reference below in: CatenaWingFram2k? to cFram8k? is there a better way??
I would expect that all reference for a particular product device would be in a common .hal or .h file for the device... like device's info, clock rates, SPI information, vbat pin, vbat scaling, led pins, any other hardware related assignments. It's a bit confusing to make change the way it is now...
2) I noticed on start up, I see LoRaWAN Init: message, where is the ?CatenaBase::GetProvisioningStyle: infor comming from.
3) can the USB serial data be re-assigned to a standard UART on the device, like Serial1 4) Is there a list of operatingflags avilable? 5) is there a document that explaned the steps needed to add a new board to the stack?
thanks...