MYSBootloader 1.4 testing
I'm about to finalize the development of MYSBootloader 1.4 with loads of changes and improvements under the hood. If you have some spare time and willingness to test, please reply here with your node config (frequency, channel, csn pin, ce pin).
This testing is only intended for Atmega328/nRF24L01+ nodes and should not be used in a productive environment.
happy to test as well.
using all default settings v1.5 mysensors libs.
count me in!
i'll be happy putting in some effort to help MYSController!
arduino pro mini + nRF24L01+ @ 3.5v
Happy to test here. ATmega328 @ 1Mhz.
Channel: 76 / 250kbps
On-board LED on D9 (not 13)
Just starting to tinker with custom bootloaders, so available for testing.
All default settings from v1.5 mysensors libs too with pro mini 3.3V 8MHz.
@tekka I was able to get a nano setup with radio and sketch.
make sure it works (saw it on the controller)
i then burned the new bootloader and re-uploaded the sketch.
i was able to then also see it back in the controller.
however i was not able to upload an OTA
every time i reboot the device it goes into an infinite loop.
only way to stop it is to pull the power.
but if you don't reboot, just let it power up, it works fine.
only upon a reboot, or a re-id does it go into this loop.
however, it did this before. so i don't think it's related to the new bootloader
but until i can resolve that, i don't know that i can send OTA's (but i'm close)
it did work in the past. it seems it worked in 1.4 libs, but when i moved everything over, it started.
but still strange, i know i've done OTA with 1.5 lib.
hard to say.
have a look at the logs see what you think.
@mvader I do not see MYSBootloader msgs in the log, but DualOptiboot msgs - can you please double-check that you really burnt MYSBootloader?
[2015-11-25 17:10:57.728 Info] RX 4;255;4;0;0;FFFFFFFFFFFFFFFF0300
This is a Dualoptiboot message...
interesting. i will double check everything.
so i checked and it appears it's correct.. have a look at my SS
does a nano come default with dual opti? the IDE says it is burning, i see the lights blinking.
and then says done, lights stop blinking.
seems like it's working
@mvader ok, the settings are fine BUT you cannot upload a sketch directly with the Arduino IDE and MYSBootloader, hence, you have the wrong bootloader...In addition, you have MY_OTA_FIRMWARE defined in your MyConfig.h? Please comment it out since this feature may only be used with Dualoptiboot but not MYSBootloader. Can you also make sure that the MYSBootlader.hex file is the one from the PM link?
ahh i did still have OTA enabled in myconfig.
I'll get that changed and tested.
@tekka so it took a few tries, but it did work.
so looking good.
and at least now i know what is wrong with my other node that goes crazy when i reboot it.
here are my logs for the OTA session
Can I get in on the test too?
2015-11-30 23:17:59,371 DEBUG [Thread-5] [org.mycontroller.standalone.gateway.ethernet.EthernetGatewayListener:55] Message Received: 1;255;3;0;15;0 2015-11-30 23:17:59,378 WARN [Thread-3] [org.mycontroller.standalone.mysensors.ProcessRawMessage:294] Internal Message[type:I_REQUEST_SIGNING,payload:0], This type may not be supported (or) not implemented yet 2015-11-30 23:18:02,176 DEBUG [Thread-5] [org.mycontroller.standalone.gateway.ethernet.EthernetGatewayListener:55] Message Received: 1;255;3;0;22;0102A00048F7FFFEDAD51FDD001E950F01 2015-11-30 23:18:02,177 ERROR [Thread-3] [org.mycontroller.standalone.mysensors.MessageMonitorThread:68] RawMessage[NodeId:1,ChildSensorId:255,MessageType:3,Ack:0,SubType:22,Payload:0102A00048F7FFFEDAD51FDD001E950F01] throws exception while processing!, java.lang.IllegalArgumentException: 22 at org.mycontroller.standalone.mysensors.MyMessages$MESSAGE_TYPE_INTERNAL.get(MyMessages.java:123) ~[mycontroller-standalone-0.0.2-alpha6-SNAPSHOT-single.jar:na] at org.mycontroller.standalone.mysensors.ProcessRawMessage.internalSubMessageTypeSelector(ProcessRawMessage.java:160) ~[mycontroller-standalone-0.0.2-alpha6-SNAPSHOT-single.jar:na] at org.mycontroller.standalone.mysensors.ProcessRawMessage.messageTypeSelector(ProcessRawMessage.java:103) ~[mycontroller-standalone-0.0.2-alpha6-SNAPSHOT-single.jar:na] at org.mycontroller.standalone.mysensors.MessageMonitorThread.processRawMessage(MessageMonitorThread.java:60) [mycontroller-standalone-0.0.2-alpha6-SNAPSHOT-single.jar:na] at org.mycontroller.standalone.mysensors.MessageMonitorThread.run(MessageMonitorThread.java:82) [mycontroller-standalone-0.0.2-alpha6-SNAPSHOT-single.jar:na] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
I have few queries,
- Have you change message format in MYSBootloader 1.4?
- Is the source code available somewhere for the community?
- I see a message
1;255;3;0;22;0108A00048F7FFFEDAC71FDD001E950F01as per the source code in
Internalmessages we have only
0 to 21types, Here I received the type
22. What is this?
- I see
1;255;3;0;15;0I_REQUEST_SIGNING also, My setup is not configured for signing. Why I'm receiving this message?
@jkandasa I_INTERNAL/22 is an internal diagnostic message, will be removed in the final 1.4 release.
I_REQUEST_SIGNING is currently forwarded to the controller if GW has signing disabled.
If u still seeking beta tester, I'm here .
Arduino Pro Mini 328p 3,3@8 + 5@16, Channel: 108, CSN:10, CE:9
Will you update the SampleController for the new bootloader or the protocol unchanged?
I need a solution to push firmware updates from a Linux machine through a serialgateway to all nodes.
I'm happy to test and share my experiences.
Arduino Pro Mini 8/16MHz
RF: nRF24L01+, Channel: 76, CSN:10, CE:9
Hi Tekka, just to understand, the new release of MYSBOOTLOADER you are working on is 1.3 or 1.4?
Are source of one release available, even in beta?
I have a setup with ~20 nodes ready to start, but I need an OTA Bootloader, no signing required.
If you already worked on that, it's a pitty to develop my own Bootloader.
Thank for all your time spend on that project and hope we can enjoy using your MYSBOOTLOADER