MYSBootloader 1.3 pre-release & MYSController 1.0.0beta
-
@tekka yep thx, I know but for some nodes I don't always need a datastorage and had the habits to add eeprom each time mainly for ota. And eeprom footprint is pretty big to place sometimes..but yes for datastorage it's cool. for the pros and cons, I agree with you, it depends of personal needs..
Have you already tried atsam boards with mysensors? I say this because I will assemble soon few atsam boards (atsamd but L family is picopower) I have designed, I will see if I'm able to port things in bootloadr but for the moment no time, too much things already in progress..in other hand, for nonpico, I'm waiting for esp32.... -
wow impressively cool :laughing:
thx for your kindness, now I have homeworks to do!
see you soon :) -
Sorry but I dont really get what you mean by freezy ?
You mean a code is compiled but it enters an infinite loop for example ? -
yes that's it. a bug in your code, like infinite loop, ram troubles... that should be rare depending of your code. plus generally you/I test on breadboard before sending it in prod, but that can happen and is good to know ;)
-
yes that's it. a bug in your code, like infinite loop, ram troubles... that should be rare depending of your code. plus generally you/I test on breadboard before sending it in prod, but that can happen and is good to know ;)
@scalz great.
This means that MYSBootloader can handle this problem and enter the bootloader mode even if the MCU freezes.@tekka you state that the current version can handle a freeze SW. Also if the new code is corrupted during programming by unverified CRC or whatever, it will also handle that problem and resets and wait for a new flashing order.
Is this new in this version ? I am some how sure that MYSBootloader previously had a problem handling thoses types of failures, and that's why I was going to use DualOptiboot as I read before that it can handle those failuresSorry for lots of questions but I am trying to reorganise my info.
-
@rollercontainer confirmed working with W5100mqtt here!
-
I have to ask again: GatewayW5100MQTTClient or the old Broker Gateway?
I am not able to connect to my GatewayW5100MQTTClient on port 1883 or 5003 with MYSController 1.0.0beta.
The gateway is in working condition with openHAB. -
-
Hello @ all :)
first thx to tekka for the great job :)
as the release notes say with the mysbootloader 1.3pre one can use the serial upload.
is its usable via the arduino ide? Because i can upload a sketch but it seems not to start.also as rollercontainer asked is the myscontroller application usable via the old broker or with the new clientmqtt gateway?
Would be nice if there are some instructions how to use ;) -
Hello @ all :)
first thx to tekka for the great job :)
as the release notes say with the mysbootloader 1.3pre one can use the serial upload.
is its usable via the arduino ide? Because i can upload a sketch but it seems not to start.also as rollercontainer asked is the myscontroller application usable via the old broker or with the new clientmqtt gateway?
Would be nice if there are some instructions how to use ;)@n1ck1355 @rollercontainer MYSController does not support MQTT (at the moment), but have a look at MyController.org. Please provide more details regarding your issue with MYSBootloader 1.3pre.
-
thx tekka for clearing this :)
for my bootloader problem:
i burned the 1.3mysbootloader with the 8mhz config successfully from the arduino dev ide.
then i uploaded a little test sketch like this without errors:void setup() { Serial.begin(57600); Serial.println("Setup Start"); } void loop() { }but there is no output on the serial monitor. it lookes like the bootloader didn't start the sketch.
-
I try to add new hex file in MYSController 1.0 but after clicking "reload repo", it tells me 2107-15-31 is not a valid date specification. I don't have the ability to select firmware after this. And after a reboot the "reload repo" is garyed.
Arduino ide 1.6.7
csv :Type,Name,Version,File,Comments 10,Blink,1,Blink.ino.hex,blinking example 20,TimeReporter,1,TimeReporter.ino.hex,TimeReporter demo 30,SenseBender,1,SensebenderMicro.ino.hex,Sensebender microAnother 'bug". It always ask me to download a "new" version ... I install it but ask me again (1.0 beta)
I think this issue is related to the last arduino IDE version. -
I try to add new hex file in MYSController 1.0 but after clicking "reload repo", it tells me 2107-15-31 is not a valid date specification. I don't have the ability to select firmware after this. And after a reboot the "reload repo" is garyed.
Arduino ide 1.6.7
csv :Type,Name,Version,File,Comments 10,Blink,1,Blink.ino.hex,blinking example 20,TimeReporter,1,TimeReporter.ino.hex,TimeReporter demo 30,SenseBender,1,SensebenderMicro.ino.hex,Sensebender microAnother 'bug". It always ask me to download a "new" version ... I install it but ask me again (1.0 beta)
I think this issue is related to the last arduino IDE version. -
thx tekka for clearing this :)
for my bootloader problem:
i burned the 1.3mysbootloader with the 8mhz config successfully from the arduino dev ide.
then i uploaded a little test sketch like this without errors:void setup() { Serial.begin(57600); Serial.println("Setup Start"); } void loop() { }but there is no output on the serial monitor. it lookes like the bootloader didn't start the sketch.
-
@rollercontainer said:
@Takero https://github.com/mysensors/Arduino/blob/development/libraries/MySensors/MyConfig.h#L387
Yes, i know what, but this is not there I am looking for.
The Autor wrote:
Attached bootloader file, compiled with these settings:nRF24 (Channel 76, base address 0xA8A8E1FC00, data rate 250kbs)
115200 baud (16Mhz) or 57600 (8Mhz)I want a Bootloader file with Channel 105.
