Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was a LOT of work, but hopefully will be bloody well worth it!
Added:
Fixes:
first place, it is the name of the board assembly, whereas the RAK4630 is just
the name of the board)
rnode.hard_reset()
on line 2859. This is negotiable of course, but tomy knowledge having that line is unnecessary, given that a hard reset is done
in
RNode_Firmware
when the EEPROM is erased anyway. It was causing issues onmy testbed as it was trying to send the reset command whilst my board was
already resetting.
even work on AVR? If so, I could always add support for them to the PR too, but
my impression is that it doesn't.
Caveats:
Sometimes during a firmware upgrade / autoinstall process, the adafruit-nrfutil
utility may have the wrong port address (only if the RAK4631 board hops port
addresses during the reset, which happens when performing an EEPROM erase for
example), causing the flashing to fail. If this is the case, currently
rnodeconf
cannot tell and will pretend as if it succeeded. I have submitted aPR to add a non-zero exit code to
adafruit-nrfutil
in this case, but theproject looks a little dead and I doubt it'll be merged soon. I may distribute
my own version instead soon to combat this. Also, to tackle the core issue, it
would be a good idea to start using board serial addresses in
rnodeconf
when selecting the boards (e.g. in /dev/serial/by-id/), which can then be
passed to
adafruit-nrfutil
and will stop the issue of port address hopping.There is a related PR for
RNode_Firmware
I will be submitting soon, I willpost the link once I have submitted it.
Update: Link to
RNode_Firmware
PR markqvist/RNode_Firmware#77