MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

[Mickey]

@tekka
My arduino IDE: 1.6.11
The avrdude inside that arduino IDE is: 6.0.1

[tekka]

@Mickey And what is the output when it fails? Can you try the bootloader with on a 16Mhz board and 115200bps?

[Mickey]

@tekka
It's not failing the node is functional and I can upload a sketch to it via MYSController but It cannot get sketch from the arduino IDE (the IDE gives the normal output that upload complete and all OK without any Error notice but after it the node doesn't have a FW on it and even if I upload some basic sketch that spit Serial to monitor nothing happen.)
I will try to upload the bootloader to an Arduino nano node to see if on 16Mhz board and 115200bps the problem exist.
Also you mention that the hex file compiled to 16Mhz board and 115200bps , maybe it should also compile on a internal 8Mhz to fix this.

[tekka]

@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

[Lorenzo]

@tekka
Hi tekka, are the source already available. I'm moving all my setup to mysensor 2.0.1 so your new bootloader is very interesting.
But on my setup I need a small customization.
I have 3 areas with 3 GW and each area with a different RF channel.
So I add a configuration switch to my nodes to select the channel.
I already modified the mysensor Library for this feature.
That why I'm asking for source code, in order to add this on bootloader too.

Thank and nice job

[tekka]

@Lorenzo not finalized, need to revise the stk500 code

[Lorenzo]

@tekka
Hi, thank for your quick answer. Yes software are never finalized :D
Even a beta release can be ok to me in order to start testing the new setup.
I will start with some micro pro 3.3V 8MHz external quartz.
Also if I can help in coding or debugging, happy to help. I spend lot of time programming AVR. Please don't hesitate, ask (PM).
In any case up to you to decide when starting publishing the first release.

Thank for your job and looking forward to test the bootloader

[Redferne]

Ohh. I'm also very eager to have my hands on the source of the beta. Please share so that we can help finalize it. I have a bunch of sensors ready for deployment, but I need a bootloader that can upgrade them. Since software is never ready 😄

///Redferne

[shabba]

Hi all.
Hands up I have not read the whole thread so apologies! I was just wondering on status of RFM69? I am about to embark on an upgrade of all my node from rf24 -> rfm69 and 1.5 -> 2.0 and would like to also add OTA while I am at it.

Thanks!

[rubyan]

@Fabien said:

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.

@Fabien You have two or more blank lines in your firmware_config.csv. This causes the error message. If you remove them and click on Reload Repo the error will be gone.

[yd kim]

@abmantis

I have same problem. Did you solve the problem?

[abmantis]

@yd-kim What problem?

[yd kim]

@abmantis
You did post following 2months ago and I have same problem too.
If you solve the problem, please share it.

Yeah, the bootloader works well with the v2.0 release.
The major issue it has currently is that sometimes it takes quite a long time to flash a sketch. It seems that when the wireless connection is not perfect, it stops for 2 or 3 seconds multiple times. Like, send 10 packages, stop 3 seconds, send 5 packages, stop again.

Thanks.

[abmantis]

@yd-kim Ah that! Nope, unfortunately it stills takes a long time to flash. We probably need an updated bootloader.

[Anduril]

@abmantis DO you have the serial upload working? I never got it working and gave up some day. I am using the old bootloader which is uploading ota much faster than the new. Maybe you can also test and confirm this?

[yd kim]

@Anduril
I did some thest.
1.3Pre.hex in 1.0.0Beta : it works with serial upload but take too long time(about an hour) to use OTA or fail.
1.1 (?) which is in 0.1.2 folder : it takes about 10 minutes and works well but doesn't work with Serial upload which is normal way to upload firmware in Arduino.
Thank you for all help.

[dpressle]

@yd-kim said:

1.3Pre.hex in 1.0.0Beta : it works with serial upload

i couldn't get the 1.3pre work with serial upload, its interesting to see you could.

[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