MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

[abmantis]

@Алексей-Гусаров Thank you! Will try that soon :)
Any updates regarding the bootloader?

[dpressle]

I managed to use the bootloader with version 2.0, thanks.

[abmantis]

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.

[n1ck1355]

any news about 1.3 final release?

[Mickey]

@tekka
I used the MYSBootloader 1.3pre with version 2.0.0
I managed to upload FW to nodes with MYSController.

As mention:
"supports OTA FW AND serial FW updates"

But I cannot get anything to serial port with the nodes.
Is the serial option really works on this bootloader?
the specs:
1.board - my own developed board with atmega328p au without external clock.
2.board.txt:

######## settings for 8Mhz internal clock, EESAVE, BOD1V8, no lock
proMYSBL8.name=ATmega328 internal 8Mhz with MYSBootloader
proMYSBL8.upload.tool=avrdude
proMYSBL8.upload.protocol=arduino
proMYSBL8.upload.maximum_size=30720
proMYSBL8.upload.maximum_data_size=2048
proMYSBL8.upload.speed=57600
proMYSBL8.bootloader.tool=avrdude
proMYSBL8.bootloader.low_fuses=0xE2
proMYSBL8.bootloader.high_fuses=0xD2
proMYSBL8.bootloader.extended_fuses=0x06
proMYSBL8.bootloader.unlock_bits=0x3F
proMYSBL8.bootloader.lock_bits=0x3F
proMYSBL8.bootloader.file=MySensors/MYSBootloaderV13pre.hex
proMYSBL8.build.mcu=atmega328p
proMYSBL8.build.f_cpu=8000000L
proMYSBL8.build.board=AVR_UNO
proMYSBL8.build.core=arduino
proMYSBL8.build.variant=standard 

3. the bootloader hex file is : MYSBootloaderV13pre.hex from MYSController 1.0.0beta

So is serial possible or/and should I change something?

[n1ck1355]

@Mickey :
It's the same problem i've posted about 4 months ago here.. i also cant run sketches i've uploaded via serial..
i hope it is solved with a new release...maybe the final already @tekka?

[tekka]

@Mickey There are some issues with Arduino IDE 1.6.10 and avrdude 6.3 - do you happen to have 1.6.10 installed?

[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.