💬 MySensors NRF5 Platform

d00616

I have updated the radio driver with fixes for some hardware errata.
I have updated the https://github.com/mysensors/ArduinoHwNRF5 with an enhanced definition format. File name and contents are changed! The board description is compatible with the NRF5 variant provided by Arduino, but it's not possible to use this variant at the moment.

NeverDie

@d00616 said in MySensors NRF5 Platform:

I have updated the radio driver with fixes for some hardware errata.

Where do we find the update? i.e. is it baked into the regular MySensors development code thread, or is it elsewhere?

NeverDie

I'm guessing it's this one? https://github.com/mysensors/ArduinoHwNRF5

NeverDie

I refreshed all the libraries. I'm able to compile and upload my sketches, but now it complains a lot about "invalid libraries."

WARNING: Spurious .ci folder in 'MySensors' library
WARNING: Spurious .mystools folder in 'MySensors' library
Sketch uses 3836 bytes (0%) of program storage space. Maximum is 524288 bytes.
Open On-Chip Debugger 0.10.0-dev-00254-g696fc0a (2016-04-10-10:13)
Licensed under GNU GPL v2
For bug reports, read
   http://openocd.org/doc/doxygen/bugs.html
debug_level: 0
0
adapter speed: 10000 kHz
cortex_m reset_config sysresetreq
nrf52.cpu: target state: halted
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x000006e8 msp: 0x20010000
** Programming Started **
auto erase enabled
wrote 4096 bytes from file C:\Users\David\AppData\Local\Temp\arduino_build_255419/Interrupt_button_test_v005.ino.hex in 0.800001s (5.000 KiB/s)
** Programming Finished **
** Verify Started **
verified 3964 bytes in 0.060000s (64.518 KiB/s)
** Verified OK **
** Resetting Target **
shutdown command invoked
Invalid library found in C:\Users\David\Documents\Arduino\libraries\arduino-nRF5: C:\Users\David\Documents\Arduino\libraries\arduino-nRF5
Invalid library found in C:\Users\David\Documents\Arduino\libraries\ArduinoHwNRF5: C:\Users\David\Documents\Arduino\libraries\ArduinoHwNRF5
Invalid library found in C:\Users\David\Documents\Arduino\libraries\arduino-nRF5: C:\Users\David\Documents\Arduino\libraries\arduino-nRF5
Invalid library found in C:\Users\David\Documents\Arduino\libraries\ArduinoHwNRF5: C:\Users\David\Documents\Arduino\libraries\ArduinoHwNRF5

d00616

@NeverDie said in MySensors NRF5 Platform:

I refreshed all the libraries. I'm able to compile and upload my sketches, but now it complains a lot about "invalid libraries."

At the moment, I cannot reproduce this with Linux and Arduino 1.8.2. I try to find out what's wrong.

d00616

@d00616 said in MySensors NRF5 Platform:

@NeverDie said in MySensors NRF5 Platform:

I refreshed all the libraries. I'm able to compile and upload my sketches, but now it complains a lot about "invalid libraries."

At the moment, I cannot reproduce this with Linux and Arduino 1.8.2. I try to find out what's wrong.

Can you try to remove the .ci and .mystools folders?

NeverDie

@d00616 said in MySensors NRF5 Platform:

Can you try to remove the .ci and .mystools folders?

Done. So, here it is now:

Archiving built core (caching) in: C:\Users\David\AppData\Local\Temp\arduino_cache_16539\core\core_MySensors_nRF5_MyBoard_nRF52832_bootcode_none,lfclk_lfxo,reset_notenable_2d457965a40837233e636c052c58b359.a
Sketch uses 3872 bytes (0%) of program storage space. Maximum is 524288 bytes.
Open On-Chip Debugger 0.10.0-dev-00254-g696fc0a (2016-04-10-10:13)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
debug_level: 0
0
adapter speed: 10000 kHz
cortex_m reset_config sysresetreq
nrf52.cpu: target state: halted
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x0000070c msp: 0x20010000
** Programming Started **
auto erase enabled
wrote 4096 bytes from file C:\Users\David\AppData\Local\Temp\arduino_build_610023/Interrupt_button_test_v006.ino.hex in 0.800001s (5.000 KiB/s)
** Programming Finished **
** Verify Started **
verified 4000 bytes in 0.060000s (65.104 KiB/s)
** Verified OK **
** Resetting Target **
shutdown command invoked
Invalid library found in C:\Users\David\Documents\Arduino\libraries\arduino-nRF5: C:\Users\David\Documents\Arduino\libraries\arduino-nRF5
Invalid library found in C:\Users\David\Documents\Arduino\libraries\ArduinoHwNRF5: C:\Users\David\Documents\Arduino\libraries\ArduinoHwNRF5
Invalid library found in C:\Users\David\Documents\Arduino\libraries\arduino-nRF5: C:\Users\David\Documents\Arduino\libraries\arduino-nRF5
Invalid library found in C:\Users\David\Documents\Arduino\libraries\ArduinoHwNRF5: C:\Users\David\Documents\Arduino\libraries\ArduinoHwNRF5

BTW, I'm using the Windows version of Arduino IDE 1.8.5, which is the most current.

d00616

@NeverDie said in MySensors NRF5 Platform:

BTW, I'm using the Windows version of Arduino IDE 1.8.5, which is the most current.

I don't know the correct path on an Windows system. On my system the Sketches are in the ~/Arduino folder in my home directory (~). The arduino-nrf5 is in ~/.arduino15/packages/sandeepmistry/hardware/nRF5/0.4.0 and the ArduinoHwNRF5 files are in ~/.arduino15/packages/MySensors/hardware/nRF5/0.2.1

mfalkvidd

on my Windows machine, all boards are located in c:\Users<username>\AppData\Local\Arduino15\packages
Strange that they've been installed to C:\Users\David\Documents\Arduino\libraries\ on your machine.

Maybe just delete the folders and re-install using the board manager?

NeverDie

@mfalkvidd All I know is that if I put a library in the folder: C:\Users\David\Documents\Arduino\libraries
it always gets detected and used. It also means you can completely uninstall/re-install the arduino IDE, and nothing gets lost. I'm not sure about other locations.

Am I the only one doing it this way?

mfalkvidd

@NeverDie for libraries, doing what you do should result in the same behavior as when using the Library Manager.
But I'm not sure it works with boards (especially given that the Arduino IDE complains when you put boards in the libraries folder).

NeverDie

I use the board manager to manage the boards. I believe it connects directly into github.

Anyhow, I stripped out all the non-library stuff, and now Windows IDE works without complaining.

NeverDie

Has anyone here yet figured out how to have more than one type of interrupt at a time wake-up the MCU from sleep? Based on the examples so far, it seems as though only one type at a time can be active. I'm sure there must be some way to do it. For instance, it would be desirable if the MCU could wake up not just from a timer event every, say, 5 minutes, to take a temperature reading, but also immediately if there is a leak detected. Right now it's just one or the other.

rmtucker

@NeverDie

So we can not use the normal statement

int8_t sleep(int interrupt, int mode, unsigned long ms=0);

I did not realize that was the case as i have never tried it.

NeverDie

I believe hwSleep(..) is the preferred incantation, but beyond that I'm not sure of anything. Maybe @d00616 can comment?

I should be receiving a number of different PCB projects tomorrow for final assembly and test, and if I can't resolve this soon, I'm simply going to release them without full demo code.

scalz

@NeverDie said in MySensors NRF5 Platform:

I believe hwSleep(..) is the preferred incantation, but beyond that I'm not sure of anything.

In MySensors, the regular way to use sleep mode is by using the sleep() functions:
https://www.mysensors.org/download/sensor_api_20#sleeping

But like you said, you can also use the raw hwSleep() from the hw abstraction layer. Or you could also rewrite it!
Which means at each abstraction layer, there are additional logics. sleep() functions have more logics (regarding MySensors states and features) than the raw hwSleep for example (like testing if there is an ongoing ota, smartsleep, heartbeat etc..). I have nodes where i use raw or not, but it's good to know what's behind.

rmtucker

@scalz
So the statement
int8_t sleep(int interrupt, int mode, unsigned long ms=0);
Can be used for timer and pin interrupt at he same time on the NRF5 platform just like the arduino?

NeverDie

I'll try it, but I have strong doubts that it's going to work.

FWIW, here's the pin mapping currently being supplied by digitalPinToInterrupt(..) for the nRF5:
Digital pin 0 = interrupt pin 0
Digital pin 1 = interrupt pin 1
Digital pin 2 = interrupt pin 2
Digital pin 3 = interrupt pin 3
Digital pin 4 = interrupt pin 4
Digital pin 5 = interrupt pin 5
Digital pin 6 = interrupt pin 6
Digital pin 7 = interrupt pin 7
Digital pin 8 = interrupt pin 8
Digital pin 9 = interrupt pin 9
Digital pin 10 = interrupt pin 10
Digital pin 11 = interrupt pin 11
Digital pin 12 = interrupt pin 12
Digital pin 13 = interrupt pin 13
Digital pin 14 = interrupt pin 14
Digital pin 15 = interrupt pin 15
Digital pin 16 = interrupt pin 16
Digital pin 17 = interrupt pin 17
Digital pin 18 = interrupt pin 18
Digital pin 19 = interrupt pin 19
Digital pin 20 = interrupt pin 20
Digital pin 21 = interrupt pin 21
Digital pin 22 = interrupt pin 22
Digital pin 23 = interrupt pin 23
Digital pin 24 = interrupt pin 24
Digital pin 25 = interrupt pin 25
Digital pin 26 = interrupt pin 26
Digital pin 27 = interrupt pin 27
Digital pin 28 = interrupt pin 28
Digital pin 29 = interrupt pin 29
Digital pin 30 = interrupt pin 30

NeverDie

The last I heard, from @d00616 , we had to supply code such as:

    // Enable interrupt
  NVIC_SetPriority(RTC0_IRQn, 15);
  NVIC_ClearPendingIRQ(RTC0_IRQn);
  NVIC_EnableIRQ(RTC0_IRQn);

and

// This must be in one line
extern "C" { void RTC0_IRQHandler(void) {rtcInterruptCounter++; NRF5_RESET_EVENT(NRF_RTC0->EVENTS_OVRFLW); NRF_RTC0->EVENTS_OVRFLW=0; }}

to get interrupts to work. Even with that approach, though, I haven't gotten it to support any interrupts in addition to a timed sleeping, though I have gotten it to support one interrupt that's separate from a timed sleeping (basically, sleeps indefinitely until the interrupt happens).

NeverDie

OK, I just now tried:

  sleep(3,CHANGE,3000);

and, as I suspected, it does nothing but sleep for 3 seconds. It's not responsive to any changes on pin P03 on an nRF52.

@scalz Are you getting a different result? It seems like there's a strong disconnect somewhere between what you're recommending and what I am experiencing.

scalz

@NeverDie said in MySensors NRF5 Platform:

@scalz Are you getting a different result? It seems like there's a strong disconnect somewhere between what you're recommending and what I am experiencing.

I didn't give any recommandation, you misread. I just said the regular way to use sleep feature in mysensors, for users, is with sleep(..). But I agree, I misread you too! when you were asking for the specific nrf52 case I guess

That said, I got this working when I made my recessed node for door (accelerometer and hall effect sensor with sleeping). Maybe things have changed in the lib?? or not. I'm struggling between different version of the lib, and some are different from the dev branch.. I'll recheck this asap (not sure for this evening).

NeverDie

I tried toying around with it a bit, and I got a useful result:

#define MY_CORE_ONLY

#include <nrf.h>
#include <MySensors.h>


const byte ledPin = LED_BUILTIN;
const byte interruptPin = 3;
volatile byte state = LOW;

void blinkityBlink(uint8_t pulses, uint8_t repetitions) {
  for (int x=0;x<repetitions;x++) {
    for (int i=0;i<pulses;i++) {
      digitalWrite(LED_BUILTIN,HIGH);
      wait(20);
      digitalWrite(LED_BUILTIN,LOW);
      wait(100);
    }    
      wait(500);
  }
}

void setup() {
  hwPinMode(LED_BUILTIN,OUTPUT_D0H1);
  hwPinMode(interruptPin, INPUT);
  attachInterrupt(digitalPinToInterrupt(interruptPin), blink, RISING);
  blinkityBlink(2,1);  //signify power-on and start of main loop
}

volatile bool buttonPressed=false;
void loop() {
  state = !state;
  digitalWrite(ledPin, state);
  sleep(digitalPinToInterrupt(interruptPin), RISING, 3000);
  wait(20);  //wait 20 milliseconds for button to debounce if it was pressed
  if (digitalRead(interruptPin)) { //if button is pressed
    blinkityBlink(2,1);
  }
  if (buttonPressed) {
    buttonPressed=false;
    blinkityBlink(20,1);
  }
}

void blink() {
  buttonPressed=true;
}

So, with this approach, pushing the button on pin 3 does wake up the nRF52 from sleep, whereupon the button press can still be detected and serviced, but it also demonstrates that the ISR per se isn't working.

Anyhow, with this I'm able to get the PIR or leak sensor or magnet sensor or light sensor doing useful things in a timely manner, even if it isn't ideal. That puts me further ahead than I was before.

rmtucker

@NeverDie
This is a test program that wakes up from either that i was using some time ago.

/**
   The MySensors Arduino library handles the wireless radio link and protocol
   between your home built sensors/actuators and HA controller of choice.
   The sensors forms a self healing radio network with optional repeaters. Each
   repeater and gateway builds a routing tables in EEPROM which keeps track of the
   network topology allowing messages to be routed to nodes.

   Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
   Copyright (C) 2013-2015 Sensnology AB
   Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors

   Documentation: http://www.mysensors.org
   Support Forum: http://forum.mysensors.org

   This program is free software; you can redistribute it and/or
   modify it under the terms of the GNU General Public License
   version 2 as published by the Free Software Foundation.

 *******************************

   REVISION HISTORY
   Version 1.0 - Henrik EKblad

   DESCRIPTION
   This sketch provides an example how to implement a distance sensor using HC-SR04
   Use this sensor to measure KWH and Watt of your house meeter
   You need to set the correct pulsefactor of your meeter (blinks per KWH).
   The sensor starts by fetching current KWH value from gateway.
   Reports both KWH and Watt back to gateway.

   Unfortunately millis() won't increment when the Arduino is in
   sleepmode. So we cannot make this sensor sleep if we also want
   to calculate/report watt-number.
   http://www.mysensors.org/build/pulse_power
*/

// Enable debug prints
#define MY_DEBUG

// Enable and select radio type attached
//#define MY_RADIO_NRF24
#define MY_RADIO_NRF5_ESB
//#define MY_RADIO_RFM69
//#define MY_RADIO_RFM95

#include <MySensors.h>
#include <Wire.h> // must be included here so that Arduino library object file references work
#include <RtcDS3231.h>
RtcDS3231<TwoWire> Rtc(Wire);

#define DIGITAL_INPUT_SENSOR 2  // The digital input you attached your light sensor.  (Only 2 and 3 generates interrupt!)
#define PULSE_FACTOR 1000       // Nummber of blinks per KWH of your meeter
//#define SLEEP_MODE false        // Watt-value can only be reported when sleep mode is false.
#define MAX_WATT 10000          // Max watt value to report. This filetrs outliers.
#define CHILD_ID 1              // Id of the sensor child

unsigned long SEND_FREQUENCY = 20000; // Minimum time between send (in milliseconds). We don't wnat to spam the gateway.
double ppwh = ((double)PULSE_FACTOR) / 1000; // Pulses per watt hour
//bool pcReceived = false;
volatile unsigned long pulseCount = 0;
volatile unsigned long lastBlink = 0;
volatile unsigned long watt = 0;
volatile unsigned long kwh = 0;
unsigned long oldWatt = 0;
double oldKwh;
unsigned long lastSend;
MyMessage wattMsg(CHILD_ID, V_WATT);
MyMessage kwhMsg(CHILD_ID, V_KWH);


void setup()
{
  Serial.begin(115200);
  Rtc.Begin();
  Rtc.Enable32kHzPin(false);
  Rtc.SetSquareWavePinClockFrequency(DS3231SquareWaveClock_1Hz);
  Rtc.SetSquareWavePin(DS3231SquareWavePin_ModeClock);

  // Use the internal pullup to be able to hook up this sketch directly to an energy meter with S0 output
  // If no pullup is used, the reported usage will be too high because of the floating pin
  hwPinMode(DIGITAL_INPUT_SENSOR, INPUT_PULLUP);

  attachInterrupt(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), onPulse, FALLING);
  //pcReceived = true;
  lastSend = millis();
}

void presentation()
{
  // Send the sketch version information to the gateway and Controller
  sendSketchInfo("Energy Meter", "1.0");

  // Register this device as power sensor
  present(CHILD_ID, S_POWER);
}

void loop()
{
  unsigned long now = millis();
  // Only send values at a maximum frequency or woken up from sleep
  bool sendTime = now - lastSend > SEND_FREQUENCY;
  if (sendTime) {
    // New watt value has been calculated
    if (watt != oldWatt) {
      // Check that we dont get unresonable large watt value.
      // could hapen when long wraps or false interrupt triggered
      if (watt < ((unsigned long)MAX_WATT)) {
        send(wattMsg.set(watt));  // Send watt value to gw
      }
      Serial.print("Watt:");
      Serial.println(watt);
      oldWatt = watt;
    }

    // Pulse count has changed
    //kwh = pulseCount;
    //double kwh = ((double)pulseCount / ((double)PULSE_FACTOR));
    send(kwhMsg.set(pulseCount));  // Send kwh value to gw
    Serial.print("Wh = ");
    Serial.println(pulseCount);
    pulseCount = 0;
    lastSend = now;
  }
  sleep(SEND_FREQUENCY);
}

void receive(const MyMessage &message)
{
}

void onPulse()
{
  unsigned long newBlink = micros();
  unsigned long interval = newBlink - lastBlink;
  if (interval < 50000L) { // Sometimes we get interrupt on RISING
    return;
  }
  watt = (3600000000.0 / interval) / ppwh;
  lastBlink = newBlink;
  pulseCount++;
}

NeverDie

Well, that's interesting. In the sketch I posted, I invoked sleep with:

  sleep(digitalPinToInterrupt(interruptPin), RISING, 3000);

which caused the mcu to wake up immediately after I press the button, but it didn't process the ISR.

Using an invocation like yours in the sketch you just posted above:

  sleep(3000);

the ISR executes and then terminates when I press the button, but the MCU doesn't wake and continue with the loop as it did with the prior incantation. Instead, it has to wait for the timer cycle to finish.

What I want is for it to wake up, do the ISR, and continue with the loop where it left off until it is explicitly put back to sleep again. How do I do that?

d00616

@NeverDie I have checked the sleep routine in all three variants. It's working with my setup.

There is no API stopping the sleep() by another ISR. Sleep only ends at one of the given conditions.

When you use the MY_CORE_ONLY define, please add "hwInit();" into the setup() routine.

NeverDie

@d00616 said in MySensors NRF5 Platform:

@NeverDie I have checked the sleep routine in all three variants. It's working with my setup.

There is no API stopping the sleep() by another ISR. Sleep only ends at one of the given conditions.

When you use the MY_CORE_ONLY define, please add "hwInit();" into the setup() routine.

Would you please post the three demo code examples that you tested?

NeverDie

@d00616 said in MySensors NRF5 Platform:

add "hwInit();" into the setup() routine.

OK, I just now did that, but I'm not getting any difference in the results.

NeverDie

In any case, I'm sure the question will ultimately turn from "How do I wake up based on a pin change?" to "How do I wake up based on the LPCOMP output, which has that pin as its input?" The reason: as covered earlier in this thread, much lower current consumption while sleeping if doing it via LPCOMP rather than the more straightforward pin monitoring.

d00616

@NeverDie said in MySensors NRF5 Platform:

In any case, I'm sure the question will ultimately turn from "How do I wake up based on a pin change?" to "How do I wake up based on the LPCOMP output, which has that pin as its input?" The reason: as covered earlier in this thread, much lower current consumption while sleeping if doing it via LPCOMP rather than the more straightforward pin monitoring.

It's a good question about, how to design the API to do this. I have no good idea.
Until an API, you can set MY_HW_RTC->CC[0] to (MY_HW_RTC->COUNTER+2). This ends sleep with some latency.

NeverDie

This post is deleted!

NeverDie

This post is deleted!

NeverDie

This post is deleted!

NeverDie

Is it just me, or does the myBoardNrf5 cause I2c to fail during initialization? I have code which worked fine on mNrf5Board but which now hangs during initialization when using myBoardNrf5. Is it working for anyone else?

NeverDie

@NeverDie said in MySensors NRF5 Platform:

Is it just me, or does the myBoardNrf5 cause I2c to fail during initialization? I have code which worked fine on mNrf5Board but which now hangs during initialization when using myBoardNrf5. Is it working for anyone else?

I've re-installed everything and am still getting no joy using I2C currently. The non-I2C stuff seems to be working fine though.
So, before I spin more cycles trying to figure it out, is i2c working for anyone else right now using the latest builds and myBoardNrf5? Or, is I2C currently broken?

NeverDie

It appears that the place where it hangs is this line here in Wire_nRF52.cpp:

  while(!_p_twim->EVENTS_LASTTX && !_p_twim->EVENTS_ERROR);

This is too bad, as I2C seemed to work fine prior to around a couple weeks ago. I think maybe (?) the latest update somehow broke it.

Please advise.

NeverDie

Well, since I'm dead in the water as things stand, I moved the code over to run on an nRF52 DK. Then, usingy Sandeep's code and none of the mysensors code, I was able to get the nRF52 DK to read an attached Si7021 temperature-humidity sensor. i.e. that worked without hanging.

So, it would appear that there's something about the mysensors code that is causing the problems. @d00616 Can we please get it fixed?

d00616

@NeverDie said in MySensors NRF5 Platform:

So, it would appear that there's something about the mysensors code that is causing the problems. @d00616 Can we please get it fixed?

I have no I2C Hardware for testing, but I take a look into the I2C and MySensors code soon.

NeverDie

The sooner the better. I'm pretty much stuck until it gets fixed.

rmtucker

@neverdie
I have been using The NRF5 with mysensors for a number of weeks with the si7021.
So it must be just a recent problem with the mysensors code?

NeverDie

@rmtucker said in MySensors NRF5 Platform:

@neverdie
I have been using The NRF5 with mysensors for a number of weeks with the si7021.
So it must be just a recent problem with the mysensors code?

I think so. Are you running the most current version? si7021 was working for me too on earlier versions. The latest update seems to have broken it. It's the one that uses myBoardNrf5 instead of myNrf5Board.

NeverDie

@rmtucker said in MySensors NRF5 Platform:

@neverdie
I have been using The NRF5 with mysensors for a number of weeks with the si7021.
So it must be just a recent problem with the mysensors code?

Would you mind trying the most recent version also to see if it breaks on you too? That would at least confirm it.

Right now my only alternative is to roll-back to the earlier version and just never upgrade again.

rmtucker

@neverdie
Where is myBoardNrf5 so i can check?

NeverDie

@rmtucker said in MySensors NRF5 Platform:

@neverdie
Where is myBoardNrf5 so i can check?

https://github.com/d00616/ArduinoHwNRF5

rmtucker

@neverdie
That explains it i am not using code from d00616.
I am only using the mysensors library and sandeeps stuff.
Sorry mate.

NeverDie

Well, in general, it's very handy for handling the pin mappings. Up until the latest release, it has worked fine. It still works fine now, except for the I2C pin mappings.

rmtucker

@neverdie
Hmmm at what cost?
Maybe i will stick with what i have got as it just works.

NeverDie

@d00616 Maybe you can just make it like it was before, where there was only one pair of I2c pins, not two as in your upgraded version? Maybe then it would work again.

scalz

@rmtucker said in MySensors NRF5 Platform:

That explains it i am not using code from d00616.
I am only using the mysensors library and sandeeps stuff.
Sorry mate.

If you're using mysensors, then you're using d00616 code (i'm kidding)

@NeverDie I can only confirm, it is related to the ArduinoHwNRF5 code as I have not the problem (I'm not using this part yet. I'm still using my own custom board definitions for the moment).
This should be fixed soon (december can be a busy month..)

d00616

@rmtucker said in MySensors NRF5 Platform:

Where is myBoardNrf5 so i can check?

This is the better repository: https://github.com/mysensors/ArduinoHwNRF5

@neverdie said in MySensors NRF5 Platform:

@d00616 Maybe you can just make it like it was before, where there was only one pair of I2c pins, not two as in your upgraded version? Maybe then it would work again.

Please give me some time. After an debug session with @scalz and @Yveaux, I think this is a tool chain (GCC 5.3) problem. The pin mapping array is part of the binary, but the Wire constructor gets an array with 0 while the Wire instance has pin mapping information.

Yesterday, I had a try to port ArduinoHwNRF5 back to the same tool chain (GCC 4.8) used by Arduino Primo and SAMD boards. I think for compatibility, this is the best option.

If I have no luck, I either remove the option of the pin remapping table or I go back to the old version. I think going back is no good idea, because the NRF52840 has more than one 32 GPIO, which requires advanced parameters.

d00616

@d00616 said in MySensors NRF5 Platform:
Back from the compiler hell. There is no chance getting the GCC 4.8 to work without forking the arduino-nrf5 code. Compiling with GCC 4.8 has the same result.

I have changed the templates a little bit and moved the code for pin mapping generation. Now it works for me. Please give me some time to clear the code and create a new package (0.3.0). With the new package, you have to add '#include <compat_pin_mapping.h>' before '#end" in MyBoardNRF5.cpp. You have to rename the '#ifdefs' and '#define' in both board files to match MYBOARDNRF5 instead of MYNRF5BOARD.

d00616

@d00616 said in MySensors NRF5 Platform:

I have changed the templates a little bit and moved the code for pin mapping generation. Now it works for me. Please give me some time to clear the code and create a new package (0.3.0). With the new package, you have to add '#include <compat_pin_mapping.h>' before '#end" in MyBoardNRF5.cpp. You have to rename the '#ifdefs' and '#define' in both board files to match MYBOARDNRF5 instead of MYNRF5BOARD.

Now, there is a new Version 0.3.0 for MyBoardNRF5 available. It can be installed via the Board Manager. Please change the templates like described above. I think, now the board definition is stable and ready to support other Arduino variants without changing the board definition.

NeverDie

@d00616

I think I made the changes you recommended, but now I'm getting:

Board MyBoard_nRF51822 (platform nRF5, package MySensors) is unknown

Error compiling for board MyBoardNRF5 nRF51822.

d00616

@neverdie said in MySensors NRF5 Platform:

I think I made the changes you recommended, but now I'm getting:
Board MyBoard_nRF51822 (platform nRF5, package MySensors) is unknown

Error compiling for board MyBoardNRF5 nRF51822.

I had the same message. In my case, I have uninstalled arduino-nrf5, cleared files, which are not removed from packages directory (the 0.2.1 MyBoard files) and reinstalled arduino-nrf5. After restarting Arduino it was fine.

NeverDie

@d00616
I'm still getting the error. I tried deleting arduino-nrf5 library and re-installing it fresh, but I don't know how, on Windows, to clear files and remove them from the packages directory. I'm not even aware of their being a "packages directory." Sorry.

NeverDie

@d00616 You mentioned that it works only with a particular version of GCC. Does that mean I need to have a particular version of the Arduino IDE installed? I'm currently running the latest version of Windows Arduino IDE, which is 1.8.5.

NeverDie

The irony of it all is that the earlier setup from 3 or so weeks ago seemed to work just fine. Unfortunately, I no longer have any idea how to get back to that.

scalz

@NeverDie
C:\Users...\AppData\Local\Arduino15\packages\MySensors\

NeverDie

@scalz said in MySensors NRF5 Platform:

@NeverDie
C:\Users...\AppData\Local\Arduino15\packages\MySensors\

Thanks!

The good news is that it compiles now. Also, the pin mapping for an LED is working. However, the bad news is that pin mapping for Serial Rx and Tx doesn't seem to be working, so I can't read any serial debug messages. Therefore, not sure if I2C is working or not.

NeverDie

I did another purge and reinsatall of the boards, and now serial is working.

NeverDie

Unfortunately, it does not appear that I2C is working.

NeverDie

Curiously, I2c does seem to work on a nRF52 DK using the myboard board definition.

NeverDie

However, it doesn't seem to be working on the nrf51.

d00616

@neverdie said in MySensors NRF5 Platform:

@d00616 You mentioned that it works only with a particular version of GCC. Does that mean I need to have a particular version of the Arduino IDE installed? I'm currently running the latest version of Windows Arduino IDE, which is 1.8.5.

The GCC version is part of the arduino-nrf5 distribution.

@neverdie said in MySensors NRF5 Platform:

Unfortunately, it does not appear that I2C is working.

I have I2C and serial running with a NRF52832.
You can try to remove the compat_pin_mapping line and add the 0.1.0 pin map at this place. Then the board definition is nearly the 0.1.0 version.

@neverdie said in MySensors NRF5 Platform:

However, it doesn't seem to be working on the nrf51.

I check the NRF51 board. What do you mean with no working?

NeverDie

I hope that narrows down the likely cause of the problem. The fact that it's working on the nRF52 gives me some hope it can be made to work on the nRF51.

NeverDie

@d00616 said in MySensors NRF5 Platform:

I check the NRF51 board. What do you mean with no working?

The nRF51 can't find the si7021 device, even though it's connected.

NeverDie

@d00616 said in MySensors NRF5 Platform:

I have I2C and serial running with a NRF52832.

Yes, it does seem to work on the nRF52832. Just not presently on the nRF51822.

NeverDie

@d00616 said in MySensors NRF5 Platform:

I check the NRF51 board. What do you mean with no working?

I'm running the sparkfun si7021 code. When I run it on the nrf52832, it yields:

Si7021 Found
Temp:70.51F, Humidity:40.71%

which is correct, but when I run it on the nRF51822, the result is:

No Devices Detected
Temp:-51.85F, Humidity:-5.81%

which is incorrect.

d00616

@neverdie said in MySensors NRF5 Platform:

@d00616 said in MySensors NRF5 Platform:

I have I2C and serial running with a NRF52832.

Yes, it does seem to work on the nRF52832. Just not presently on the nRF51822.

Can you check, if the device works with the "Generic NRF51822" board? You can edit the variant files in the arduino-nrf5\variants directory.
C:\Users...\AppData\Local\Arduino15\packages\sandeepmistry\hardware\nRF5\0.4.0\variants\Generic

NeverDie

@d00616 said in MySensors NRF5 Platform:

@neverdie said in MySensors NRF5 Platform:

@d00616 said in MySensors NRF5 Platform:

I have I2C and serial running with a NRF52832.

Yes, it does seem to work on the nRF52832. Just not presently on the nRF51822.

Can you check, if the device works with the "Generic NRF51822" board? You can edit the variant files in the arduino-nrf5\variants directory.
C:\Users...\AppData\Local\Arduino15\packages\sandeepmistry\hardware\nRF5\0.4.0\variants\Generic

I tried, but I guess I'm not doing it right. I couldn't even get it to blink an LED that way.

NeverDie

@d00616 said in MySensors NRF5 Platform:

You can try to remove the compat_pin_mapping line and add the 0.1.0 pin map at this place. Then the board definition is nearly the 0.1.0 version.

So, I take it you are suggesting that in myboardnrf5.cpp, where it says:

#ifdef MYBOARDNRF5
#include <variant.h>
#include <compat_pin_mapping.h>

I replace

#include <compat_pin_mapping.h>

with what exactly? At this point I'm not even sure where 0.1.0 pin-map is, or even what it's called.

NeverDie

@neverdie said in MySensors NRF5 Platform:

I tried, but I guess I'm not doing it right. I couldn't even get it to blink an LED that way.

After I modify the generic variant board definition, is there some trick to making it go "live"?

scalz

@NeverDie
there is no trick.. it should work.
d00616 said, for a test, to not use his defines, the method that you're used to.
So change the defines you need in the generic variant file, then in arduino:

NeverDie

I think this must be where the disconnect is happening. Where do I find the files or directory for Generic nRF51? The closest I see is a directory called just "Generic":

That's the one I tried modifying:

and it had no effect. So, I suspect there must be a different "generic nRF51" somewhere which is closely tied with the menu item you show the picture of. However, I don't see where.

Nca78

@neverdie did you check there ?

NeverDie

I didn't try that one, but it's a similar dilemma:

i.e. Does "Generic" do double duty for both "Generic nRF51" and "Generic nRF52"?

NeverDie

Aha! That did it. Thanks @NCA78. It's working now, including the I2C.

I had to switch nodes though. It's possible that the mysensors code does work, as the node I was testing it on may have had a bad si7021 module on it. I'll post again after I retry with this different node.

NeverDie

I'm back with the results. The same node where I2C works using the customized "Generic nRF51" does not have working I2c if using the mysensors "MyBoardnRF5 nRF51822".

So, I think I've taken this as far as I can. Hopefully this info helps you solve whatever the problem is.

I'm grateful I can keep moving along now using a modified "Generic nRF51822". Thanks everybody!

NeverDie

Ashes on my head. The mysensors code is working with I2c after all. I confirmed it on the second (alternate) node. I had switched two of the wires in the myboardnrf5 pinout, but hadn't on the generic nRF51 pinout. Correcting for that, it now works.

What threw me completely off was the defective si7021 module on the first node. Well, now everything is sorted.

d00616

@neverdie said in MySensors NRF5 Platform:

Ashes on my head. The mysensors code is working with I2c after all. I confirmed it on the second (alternate) node. I had switched two of the wires in the myboardnrf5 pinout, but hadn't on the generic nRF51 pinout. Correcting for that, it now works.

Thank you for reporting this. Great news to hear this.

NeverDie

@d00616 said in MySensors NRF5 Platform:

Thank you for reporting this. Great news to hear this.

You're welcome, of course. Though it was a little bit of a wild goose chase, at least your code is now pretty well tested and proven to be "known good," so others can start using it without fear.

With this now out of the way, please do continue your excellent work!

Omemanti

This post is deleted!

Yveaux

@omemanti Shot in the dark: did you swap Tx/Rx by accident?

Omemanti

This post is deleted!

Omemanti

I'm not sure if I destroyed something on the board.ill try another one.. to not fill-up this forum threat I'll delete my previous posts

monte

Hello, @d00616. Could you tell me which ESB library did you use to port it to arduino environment? The one that comes with Nordic SDK? After searching for few hours I haven't find any other realization of ESB mode for arduino IDE except your port included with MySensors. It's a pity. Are you going to release general purpose library, maybe?

d00616

@monte said in MySensors NRF5 Platform:

Hello, @d00616. Could you tell me which ESB library did you use to port it to arduino environment? The one that comes with Nordic SDK? After searching for few hours I haven't find any other realization of ESB mode for arduino IDE except your port included with MySensors. It's a pity. Are you going to release general purpose library, maybe?

The ESB library is written from scratch. At the time of of starting the Nordic SDK license was incompatible with open source projects. I have no plans to release this as stand-alone library. At the moment there is only an subset of the ESB protocol implemented. Enough to be compatible with MySensors RF24 devices.

Feel free to use my code to create a stand-alone library. If required, we can talk about dual licensing to code with an additional open source license.

monte

@d00616 thanks for a reply. I will evaluate my skills for this task, when I actually will get a chip to try it on. I need some really small pcb for my project, and single chip with mcu and rf with the size of nrf51 fits perfectly, but it requires quiet simple communications and full MySensors library will be overkill and hard to adapt for my needs.

d00616

@monte said in MySensors NRF5 Platform:

@d00616 thanks for a reply. I will evaluate my skills for this task, when I actually will get a chip to try it on. I need some really small pcb for my project, and single chip with mcu and rf with the size of nrf51 fits perfectly, but it requires quiet simple communications and full MySensors library will be overkill and hard to adapt for my needs.

You can use the MY_CORE_ONLY mode -> https://forum.mysensors.org/post/76627

monte

@d00616 great tip, thanks! I didn't know about that option, to bad it's buried on the deepest level of documentation. I guess this will do the thing. I greatly appreciate your help, it's a pleasure when people are willing to share their knowledge with others

monte

@d00616 one more question. Is your driver able to send broadcast messages, without defined address, or should I just use the same node address on multiple receiving nodes?

d00616

@monte Thank you.

@monte said in MySensors NRF5 Platform:

@d00616 one more question. Is your driver able to send broadcast messages, without defined address, or should I just use the same node address on multiple receiving nodes?

The broad cast address is hard coded to 0xff (255). Each node must have a uniqe address, because it's not possible to send packages to a node with the same address.

d00616

@monte said in MySensors NRF5 Platform:

@d00616 thanks for a reply. I will evaluate my skills for this task, when I actually will get a chip to try it on. I need some really small pcb for my project, and single chip with mcu and rf with the size of nrf51 fits perfectly, but it requires quiet simple communications and full MySensors library will be overkill and hard to adapt for my needs.

If possible use the nRF52 series. There are some improvements like better radio sensivity, lower current consumption, more RAM and flash, better ADC and a better CPU. Maybe in the future there is a Firmware update OTA functionality which is easier to adapt to the NRF52 than the NRF51 platform. Another reason to use the NRF52 is, that the official Arduino NRF5 port only supports the NRF52. This port has a lot more capabilities than the arduino-nrf5 port, but MySensors is not compatible at the moment.

Nca78

Should we worry about that ?

d00616

@nca78 said in MySensors NRF5 Platform:

Should we worry about that ?

No. There are some ports of Arduino for NRF5. At the moment MySensors is not compatible with the Primo Port, because it comes with the SoftDevice. It changes nothing for the current state.

Omemanti

What is the best way to use a pin interrupt to wake up form a sleep?

like for instance, I got some sort of motion connected to PIN 8.

NeverDie

The source code for the PIR project gives one possible answer.

Omemanti

@neverdie
I've been dealing with that code but for some reason, I don't get it to work, code-wise it seems I'm lacking..

First i get this error: struct NRF_UARTE_Type' has no member named 'TASKS_SUSPEND
And when I comment that out it seems like its not waking up.

I made a test sketch, which reported the status every 1000ms. this worked accurately for the last 3 days so it doesn't look like it is a sensor problem.

So my hope was that there was an easier methode available..

NeverDie

@omemanti Sounds like maybe you're either missing a library or else not linking to one that's required.

Omemanti

@neverdie

What am I missing, I just reinstalled the whole shabang.

Arduino IDE
Sandeep
Mysensors 2.2.0

thats all there is installed..

NeverDie

@omemanti You want the mysensors development fork.

💬 MySensors NRF5 Platform

Suggested Topics

💬 MyThermostat
OpenHardware.io • mysensors arduino rfm69 thermostat pid heater • • openhardware.io

💬 OH Easy Advanced Gateway
OpenHardware.io • mysensors contest2017 • • openhardware.io

MySensors - oldskool electronic components - doorbell chime
OpenHardware.io • mysensors doorbell sensor mutuable doorbell chime doorbell chime • • openhardware.io

💬 Small arduino pro mini rfm69 shield
OpenHardware.io • mysensors rfm69 arduino pro mini • • openhardware.io

💬 Itron Aquadis+ watermeter sensor V1.0
OpenHardware.io • mysensors watermeter • • openhardware.io

Yet another MQTT gateway for MySensors :)
Development • mysensors mqtt • • scurb

💬 Ikea Molgan Hack
OpenHardware.io • mysensors motion pir hack ikea molgan • • openhardware.io

8
Online

11.4k
Users

11.1k
Topics

112.7k
Posts

💬 MySensors NRF5 Platform

Suggested Topics

💬 MyThermostat OpenHardware.io • mysensors arduino rfm69 thermostat pid heater • • openhardware.io

💬 OH Easy Advanced Gateway OpenHardware.io • mysensors contest2017 • • openhardware.io

MySensors - oldskool electronic components - doorbell chime OpenHardware.io • mysensors doorbell sensor mutuable doorbell chime doorbell chime • • openhardware.io

💬 Small arduino pro mini rfm69 shield OpenHardware.io • mysensors rfm69 arduino pro mini • • openhardware.io

💬 Itron Aquadis+ watermeter sensor V1.0 OpenHardware.io • mysensors watermeter • • openhardware.io

Yet another MQTT gateway for MySensors :) Development • mysensors mqtt • • scurb

💬 Ikea Molgan Hack OpenHardware.io • mysensors motion pir hack ikea molgan • • openhardware.io

8Online

11.4kUsers

11.1kTopics

112.7kPosts

💬 MyThermostat
OpenHardware.io • mysensors arduino rfm69 thermostat pid heater • • openhardware.io

💬 OH Easy Advanced Gateway
OpenHardware.io • mysensors contest2017 • • openhardware.io

MySensors - oldskool electronic components - doorbell chime
OpenHardware.io • mysensors doorbell sensor mutuable doorbell chime doorbell chime • • openhardware.io

💬 Small arduino pro mini rfm69 shield
OpenHardware.io • mysensors rfm69 arduino pro mini • • openhardware.io

💬 Itron Aquadis+ watermeter sensor V1.0
OpenHardware.io • mysensors watermeter • • openhardware.io

Yet another MQTT gateway for MySensors :)
Development • mysensors mqtt • • scurb

💬 Ikea Molgan Hack
OpenHardware.io • mysensors motion pir hack ikea molgan • • openhardware.io

8
Online

11.4k
Users

11.1k
Topics

112.7k
Posts