* New Firmware OTA for NVM/mcuboot (nRF5)
- Support for mcuboot (nRF5)
- Support for run length encoded data
- Support for smaller FIRMWARE_BLOCK_SIZE, if required
* Update NVM
* New MY_LOCK_MCU for NRF5
* Test with Sensebender GW + Sensebender Micro was successful
MY_SIGNING_SIMPLE_PASSWD is now
called MY_SECURITY_SIMPLE_PASSWD.
MY_SIGNING_SIMPLE_PASSWD only affects signing,
and a new flag, MY_ENCRYPTION_SIMPLE_PASSWD
only affects encryption.
MY_SECURITY_SIMPLE_PASSWD enable both these flags.
The rPi port has been improved to support more
security settings and it is now also possible to
enable encryption for RFM69 transport.
Documentation has been improved to provide a
"Security" section under "Library customisation"
which has a table that summarize all security
related configuration flags, and the corresponding
rPi configuration flags.
The signing personalization documentation has been
updated to include the procedure for rPi.
Fixes#1055
* Fix cppcheck issues
Fixes the following cppcheck issues:
examples/SecretKnockSensor/SecretKnockSensor.ino
305 variableScope 398 style
The scope of the variable 'timeDiff' can be reduced.
examples/SensebenderGatewaySerial/SensebenderGatewaySerial.ino
127 variableScope 398 style
The scope of the variable 'led_state' can be reduced.
* Doxygenize MyMessage / Message manipulation
This should replace the static documentation at
http://korturl.nu/stupid
I have enabled existing comments and added new comments where
necessary. Feedback on syntax and contents is welcome.
As discussed in
http://korturl.nu/gitler-is-a-stubborn-bastard-1
and numerous other forum threads, many people don't understand
that id generation is done by the controller.
Many new users start out their first MySensors network with a
gateway, a single sensor node and no controller. Since MySensors
defaults to AUTO node id, the node gets stuck on TSM:ID:FAIL,
like this:
TSM:ID
TSM:ID:REQ
TSF:MSG:SEND,255-255-0-0,s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
TSM:ID
TSM:ID:REQ
TSF:MSG:SEND,255-255-0-0,s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
TSM:ID
TSM:ID:REQ
TSF:MSG:SEND,255-255-0-0,s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
TSM:ID
TSM:ID:REQ
TSF:MSG:SEND,255-255-0-0,s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
!TSM:ID:FAIL
This change adds a clarifying note about the controller in the
doxygen documentation.
To use this feature, add the following to a sketch, for example
GatewayESP8266MQTTClient:
const uint8_t bssid[] = {0x00, 0xDE, 0xAD, 0xBE, 0xEF, 0x00};
#define MY_ESP8266_BSSID bssid
This feature was requested in
https://github.com/mysensors/MySensors/issues/947
* Added support for I2C EEPROM OTA
* EEPROM OTA now uses extEEPROM as driver
* Compiler warning fix
* Style check fixes
* Fix doxygen warnings of I2CEeprom
* Use bool instead of boolean in I2CEeprom shim
* Fix re-merged style problem
added variant of MyMessage::set and sendSketchInfo that accept a
string that's stored in PROGMEM.
This avoids the need to (temporarily) store strings in memory to get
them into a message.
- Fix UDP send
- Add a default value for MY_IP_GATEWAY_ADDRESS and
MY_IP_SUBNET_ADDRESS, making them optional when using MY_IP_ADDRESS
- Add support for MY_IP_GATEWAY_ADDRESS and MY_IP_SUBNET_ADDRESS to
W5100
* Sha256 driver cosmetics
cosmetic cleanups:
- use actual define that was used to allocate the array
- remove unused file globals
* Save memory by eliminating sha256_hash array
eliminated sha256_hash array to save memory. Instead pass the
Sha256Class result pointer.
There seems to be no use for the extra sha256_hash array as it was
zeroed exactly at the same time, the Sha256Class result was invalidated
(by calling signerSha256Init)
If the result needs to stay around while another sha is calculated,
it's better to have the user taking care of this.
* Moved hmac methods and buffers to separate class
This allows saving the buffer memory if no hmac is needed ... eg. with
the public Signing API.
For soft signing, let backend handle checksum verification of
personalization data. This ensures that the backends sha256 library is
used and avoids an unnecessary instanitation of the public library.
For atsha204 signing, no checksum verification is made, just chip
locking flags.
Fixes#872