MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

[Mickey]

@tekka said:

@Mickey Ok, I see, this is something related to the internal checksum, need to adjust that. In short: the bootloader doesn't hand over to the sketch

Has this adjusted already?

[kalina]

Hi @tekka, can you help me?
I want to start exchanging between my MDMSGate device and MYSController via Ethernet. But I don't use Ethernet Shield W5100 in my MDMSGate, I use microcontroller PIC18F67J60 instead. I have uploaded to the PIC18F67J60 firmware which converts TCP/IP packets to serial and conversely.

In atmega328P I use the serial gateway sketch. So, I can't connect MYSController to my MDMSGate. Can you explain me, how MYSController exchanges with gateway generally? In an exchange through CP2102 (as a serial gateway mode) everything works well.

[kk02067]

In the "firmware_config.csv" file, on the first line it says:

Type,Name,Version,File,Comments

I know that it is there to explain how to add new lines to the file.
But I don't know what "Type" is used for.
The two examples have the numbers 10 and 20. I added a 30 and it seems to work but I would like to know what it's for.

Thanks

[abmantis]

@Anduril Haven't tried serial yet. The old bootloader seemed indeed a bit faster. I also noticed that if I touch pin 10 with my finger, it gets really fast! It just sends the packages continuously without stoping. As soon as I stop touching pin 10, it pauses.

The gw and the node were like 1 meter, so it is not a distance problem. Also tried moving them closer and apart.

[Lorenzo]

This post is deleted!

[yd kim]

@abmantis Interesting. Can you let me know a little bit further detail?
You mean Arduino pro mini pin 10? That pin is connected to CSN on NRF24L01.
I'm keen to find the issue why it get slow.. It took 20-30minutes to upload new firmware....

[abmantis]

@yd-kim Yes, just touch Arduino's pin 10. Dunno if it is a particularity with this Arduino or radio. It updates the node in about 20 seconds!

[Jan Hicl]

Hi @tekka, I'm having the very same issue as @Mickey so I just wanted to ask if there is any workaround to that or if happen to make the adjustment to the bootloader. Thanks a lot! Original comment

[tekka]

@Jan-Hicl This has been fixed - did you try the most recent version from github?

[Jan Hicl]

Hi @tekka and thanks for getting back to me! I tried the latest version however with no success. The node that I update is still marked as "Booting" even though I upload Blink.hex. Strangely enough, the led is blinking as it's supposed to blink and if I request presentation the node replies with correct sketch name but then it goes back to Booting. I'm using Arduino IDE 1.8.1, AVRdude v6.1 and MYScontroller v1.0.0 beta (build 3314). I'm using Arduino mini pro, 3V3, 8MHz. I have 5 different nodes but all of them with the same behavior so it does not seem as an HW issue.

Here is my log from the upload of Blink.hex: http://pastebin.com/9grgHb27 Would you have any idea how could I fix that? Thanks!

[tekka]

@Jan-Hicl The blink sketch is somewhat special - it only blinks the built-in LED until the watchdog kicks in and resets the node. What happens if you upload one of your sketches? Please post the full debug log + source. Thanks

[yd kim]

I did success with MySBootloader 1.3 beta 3 (https://github.com/mysensors/MySensorsBootloaderRF24 )
It works both arduino and OTA firmware upgrade however it takes longer to boot up (means switch to firmware) about 3-5seconds.
I'm using MYSensors 2.1.0 and MYController (http://www.mycontroller.org) on arduino pro mini 8Mhz 3.3V.

How many sensor you try at the same time?
From memory When I do firmware update for 3-4 sensors, I have to change "Tx message processing delay" to 300ms.
If it's shorter than 300ms, keep rebooting some stage.

I didn't use MYScontroller but probably it has similar setting.

[Jan Hicl]

Thanks @tekka for a prompt response!

I tried to upload https://github.com/mysensors/MySensors/blob/master/examples/AirQualitySensor/AirQualitySensor.ino
here is the log: http://pastebin.com/Tc5vhEnF
You can see that the node is successfully running with TimeReporter but AirQualitySensor cannot make it from booting. However, this is happening even with highly modified AirQualitySensor sketch or some of my custom sketches. In the log, you can also see that if I request presentation of that node it replies with correct sketch name.

Please let me know if you need some more info. Thanks in advance!

[tekka]

@Jan-Hicl Please also post the full debug log of the node (running AirQualitySensor).

[Jan Hicl]

@tekka here is the AirQualitySensor node log: http://pastebin.com/XWfFCbUx

[tekka]

@Jan-Hicl The GW and node logs are inconsistent: your GW log shows a rebooting node 1 - the node log shows a running node trying to establish the uplink. Do you have logs from GW and node taken simultaneously?

[Jan Hicl]

Sorry @tekka, should've sent this in the first post. Here is AirQuality sensor node log: http://pastebin.com/9MVtfRNV
Here is gateway log: http://pastebin.com/QNpmBz4m
Both of them logged simultaneously. Node Id I'm updating is 1. In the log you can again see that TimeReporter is working well before the flashing. Please let me know if there is anything I can provide you with in order to solve this... Thanks!

[Nicolas Charrier]

Hello
I succed to program booloader but y can not add my sketch to arduino with serial or USB line.
Is is activated by default?
Thanks.

[Jan Hicl]

Hi @tekka any update what could be wrong with the upload? Any advice on a workaround? Thanks!

[tekka]

@Jan-Hicl The upload via bootloader is ok (the sketch is running - based on your debug log) - so no issue here.
However, you may have some issues with the CPU frequency (wrong board selected when compiling?) - there are scrambled chars in the debug output:

Starting óensor (RNNNA-, 2.0.0)
TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=1)
TSM:FPAR
TSP:MSG:ÓEND 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSP:MSG:READ 0-0-1 s=255,c=3,t=8,pt=1,l=1,sg=0:0
TSP:MSG:FPAR RES (IÄ=0, dist=0)
TSP:MSG:PAR OK (ÉD=0, dist=1)
TSM:FPAR:OK
TSM:ID
TSM:CHKID:OË (ID=1)
TSM:UPL
TSP:PING:SEND (dest=0)
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=ok:1
TSP:CHKUPL:FAIL (hops=255)
!TSM:UPL:FAIÌ
TSM:FPAR
TSP:MSG:SEND 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSP:MSG:READ 2-2-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
TSP:MSG:BC
TSP:MSG:ÒEAD 0-0-1 s=255,c=3,t=8,pt=1,l=1,sg=0:0
ÔSP:MSG:FPAR RES (ID=0, dist=0)
TSP:MSG:PAR OK (ID=0, diót=1)
TSM:ÆPAR:OK