Windows GUI/Controller for MySensors

[tekka]

@robosensor said:

The MYSBootloader.hex file you are flashing has a wrong file size (=32722 bytes) in your post:

avrdude: reading input file "C:\Program Files (x86)\Arduino\hardware\arduino\avr/bootloaders/MySensors/MYSBootloader.hex"
avrdude: writing flash (32722 bytes):

MYSBootloader 1.1 should have ~2kb

From your log I assume, that you flashed the sketch instead of the bootloader.

Please pay attention to steps 3 and 13 from the step-by-step manual.

[robosensor]

@tekka I have noticed this, but I thought that this is due to the peculiarities of bootloader upload process (upper end of memory).

 Directory of C:\Program Files (x86)\Arduino\hardware\arduino\avr\bootloaders\MySensors

14.06.2015  00:08    <DIR>          .
14.06.2015  00:08    <DIR>          ..
14.06.2015  09:59             5 548 MYSBootloader.hex
               1 File(s)          5 548 bytes

For sketch size is too big (32722 bytes), real sketch size is 19928 bytes.

In any case, thanks for the help, I'll try to figure it out or try to download it manually using avrdude.

[NewFolk]

@tekka
Hello, could you help me with uploading bootloader. I stuck on Step 5 step-by-step manual and get error

Arduino: 1.6.4 (Mac OS X), Плата"ATmega328 16Mhz MYSBootloader"
avrdude: error: could not find USB device with vid=0x16c0 pid=0x5dc vendor='www.fischl.de' product='USBasp'

I`m using 16Mhz pro mini clone and FTDI232

[robosensor]

@tekka I have googled for [avrdude bootloader "bytes of flash written"] and found many answers about big upload size for bootloader (> 32000 bytes). It seems that big size is the way it should be.

I have solved problem. I must power up node with newly burned bootloader but without sensor node firmware and upload firmware using MYSController

Incorrect way is: burn bootloader, burn sensor node firmware, powerup sensor.

Thank you for great software! :)

[tekka]

@NewFolk You'll need e.g. USBasp or ArduinoISP to flash a new bootloader. If you have a spare Arduino and FTDI232, follow this tutorial to program a new bootloader using the Arduino IDE.

Good luck! :)

[tekka]

@robosensor Yes, the sensor firmware is uploaded OTA via MYSController.

[mvader]

Hi - I need some clarification.
I have mysensors connected to my vera lite (working)
I bought 3 of the sensebender micro boards and got them talking with the gateway (working)
loaded up myscontroller it's running and see the gateway and all 3 nodes.
yay!
the issue is the sensors are reporting in C instead of F, so i modified the sketch, compiled it, found the hex file (66k)
and moved it to the correct folder per instructions.
when i says "assign FW" nothing happens.
am i understanding correctly that "firmware" is just a compiled sketch?
if i need to make changes to my device, is this the correct way?
modify sketch - > compile -> move hex to myscontroller folder - > edit firmware_config file -> right click assign fw -> pick new firmware
is that correct?
nothing is happening for me when i do that..
please clarify.
thanks!

edit: file size says 66k in win7
but in the compiler it says
Sketch uses 23,724 bytes (77%) of program storage space. Maximum is 30,720 bytes.
Global variables use 822 bytes (40%) of dynamic memory, leaving 1,226 bytes for local variables. Maximum is 2,048 bytes.

the file i grabbed was SensebenderMicro.cpp.hex

[tekka]

@mvader said:

when i says "assign FW" nothing happens.
am i understanding correctly that "firmware" is just a compiled sketch?
if i need to make changes to my device, is this the correct way?
modify sketch - > compile -> move hex to myscontroller folder - > edit firmware_config file -> right click assign fw -> pick new firmware
is that correct?
nothing is happening for me when i do that..

For OTA updates you need to burn the MYSBootloader (instructions here). Once done, assign FW, reboot node and wait until FW is transferred.

edit: file size says 66k in win7
but in the compiler it says
Sketch uses 23,724 bytes (77%) of program storage space. Maximum is 30,720 bytes.

Yup, because the .hex file is not binary but a hex (hence the suffix) format with headers and checksums.

[mvader]

@tekka said:

@mvader said:

when i says "assign FW" nothing happens.
am i understanding correctly that "firmware" is just a compiled sketch?
if i need to make changes to my device, is this the correct way?
modify sketch - > compile -> move hex to myscontroller folder - > edit firmware_config file -> right click assign fw -> pick new firmware
is that correct?
nothing is happening for me when i do that..

For OTA updates you need to burn the MYSBootloader (instructions here). Once done, assign FW, reboot node and wait until FW is transferred.

edit: file size says 66k in win7
but in the compiler it says
Sketch uses 23,724 bytes (77%) of program storage space. Maximum is 30,720 bytes.

Yup, because the .hex file is not binary but a hex (hence the suffix) format with headers and checksums.

I thought i read those sensebender boards were going to come pre-burned with the MYSBootloader from the mfg? that why you wouldn't need a programmer. i'll check with those folks..

edit: i found where they said it was pre-programmed..

@hek said:

Yes, FTDI, ISCP or over-the-air updates.

It comes pre-programmed with MySensors variant of the DualOptiboot-bootloader.
https://github.com/mysensors/DualOptiboot
Which can take advantage of the extra flash memory to do a safe over-the-air firmware update.
It comes pre-programmed with MySensors variant of the DualOptiboot-bootloader.
https://github.com/mysensors/DualOptiboot
Which can take advantage of the extra flash memory to do a safe over-the-air firmware update.

[mvader]

This post is deleted!

[gigaguy]

I have a some questions. Couldnt find answer anywhere.

If I am using an arduino connected to the serial port on a Raspberry pi (w/openhab) How do I assign fw, reboot, etc?

Do I need to disconnect the GW and use windows temporarily to reboot, update fw? or can I have 2 GW's?

I updated my nano with the MYS bootloader, and after I power it on, it never shows up in MYSController.

[Fredrik Carlsson]

@tekka Hey, it seems like the downloadlink is broken. Can you check?

[n3ro]

i dont understand how to use this...
Can somebody explain it?

[tekka]

@Fredrik-Carlsson link works for me (https://goo.gl/48Yn6y)

[Fredrik Carlsson]

Yes I tried now again an now it works. Maybe something temporary with Dropbox yesterday

[cdr]

It is possible to burn the bootloader to an Arduino Uno right? (if not please skip below and I will rtfm some more)

Could anyone please explain me what I am doing wrong here? I use avrdudess (http://blog.zakkemble.co.uk/avrdudess-a-gui-for-avrdude/) to program the bootloader.hex (also tried the supplied method) but no dice;

Writing the bootloader seems to work;

Detected 1e950f = ATmega328P
MYSBootloader.hex: 2.002 / 32.768 Bytes (6,11%)
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 

avrdude.exe: set SCK frequency to 1500000 Hz
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude.exe: Device signature = 0x1e950f
avrdude.exe: erasing chip
avrdude.exe: set SCK frequency to 1500000 Hz
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: reading input file "C:\Users\codar\Desktop\MYSController_0_1_2_280\Bootloader\MYSBootloader.hex"
avrdude.exe: input file C:\Users\codar\Desktop\MYSController_0_1_2_280\Bootloader\MYSBootloader.hex auto detected as Intel Hex
avrdude.exe: writing flash (32722 bytes):

Writing | ################################################## | 100% 0.00s

avrdude.exe: 32722 bytes of flash written
avrdude.exe: verifying flash memory against C:\Users\codar\Desktop\MYSController_0_1_2_280\Bootloader\MYSBootloader.hex:
avrdude.exe: load data flash data from input file C:\Users\codar\Desktop\MYSController_0_1_2_280\Bootloader\MYSBootloader.hex:
avrdude.exe: input file C:\Users\codar\Desktop\MYSController_0_1_2_280\Bootloader\MYSBootloader.hex auto detected as Intel Hex
avrdude.exe: input file C:\Users\codar\Desktop\MYSController_0_1_2_280\Bootloader\MYSBootloader.hex contains 32722 bytes
avrdude.exe: reading on-chip flash data:

Reading | ################################################## | 100% 0.00s

avrdude.exe: verifying ...
avrdude.exe: 32722 bytes of flash verified

However tech life wouldn't be techlife without days of endless debugging

Setting the extended fuse fails verification

avrdude.exe: reading on-chip flash data:

Reading | ################################################## | 100% 0.00s

avrdude.exe: verifying ...
avrdude.exe: 32722 bytes of flash verified
avrdude.exe: reading input file "0xF7"
avrdude.exe: writing lfuse (1 bytes):

Writing | ################################################## | 100% 0.00s

avrdude.exe: 1 bytes of lfuse written
avrdude.exe: verifying lfuse memory against 0xF7:
avrdude.exe: load data lfuse data from input file 0xF7:
avrdude.exe: input file 0xF7 contains 1 bytes
avrdude.exe: reading on-chip lfuse data:

Reading | ################################################## | 100% 0.00s

avrdude.exe: verifying ...
avrdude.exe: 1 bytes of lfuse verified
avrdude.exe: reading input file "0xDA"
avrdude.exe: writing hfuse (1 bytes):

Writing | ################################################## | 100% 0.00s

avrdude.exe: 1 bytes of hfuse written
avrdude.exe: verifying hfuse memory against 0xDA:
avrdude.exe: load data hfuse data from input file 0xDA:
avrdude.exe: input file 0xDA contains 1 bytes
avrdude.exe: reading on-chip hfuse data:

Reading | ################################################## | 100% 0.00s

avrdude.exe: verifying ...
avrdude.exe: 1 bytes of hfuse verified
avrdude.exe: reading input file "0xFE"
avrdude.exe: writing efuse (1 bytes):

Writing |  ***failed;  
################################################## | 100% 0.03s

avrdude.exe: 1 bytes of efuse written
avrdude.exe: verifying efuse memory against 0xFE:
avrdude.exe: load data efuse data from input file 0xFE:
avrdude.exe: input file 0xFE contains 1 bytes
avrdude.exe: reading on-chip efuse data:

Reading | ################################################## | 100% 0.00s

avrdude.exe: verifying ...
avrdude.exe: verification error, first mismatch at byte 0x0000
             0x06 != 0xfe
avrdude.exe: verification error; content mismatch

avrdude.exe done.  Thank you.

This last error is giving me headaches, why the "first mismatch at byte 0x0000 0x06 != 0xfe" error?

Really hope someone can enlighten me...

[tekka]

@cdr the efuse only uses the lower 3 bits: with AVRDude set 0x06, with AVRStudio set 0xFE. You can verify this with the fuse calculator.

[Fabien]

I try to uplaod sketch via OTA but it doesn''t work.
I have sensebender with stock bootloader. Gateway is connect to an ODROID C1 with ser2net and i connect to ser2net. I can see all incoming traffic for my sensors.
I upload sensebender default sketch from dev branch using MySensors dev branch too.
I tell MYSController sensors is battery powered.
I try with the two provided example but nothing happen in log or anything else

[mvader]

@Fabien said:

I try to uplaod sketch via OTA but it doesn''t work.
I have sensebender with stock bootloader. Gateway is connect to an ODROID C1 with ser2net and i connect to ser2net. I can see all incoming traffic for my sensors.
I upload sensebender default sketch from dev branch using MySensors dev branch too.
I tell MYSController sensors is battery powered.
I try with the two provided example but nothing happen in log or anything else

check in the sensebender announcement thread. I had the same question. Hek responded with what needed to be done to make it work.
I didn't get a chance to try his solutions yet to see if it works. if you do, post and let us know.

edit: here
http://forum.mysensors.org/topic/1345/sensebender-micro/139

[Dirk_H]

@Fabien
I dont understand what you mean by "I told MysController" that the node is battery powered. It should find that out automatically I think. Anyway I'm pretty sure that I read somewhere that battery powered sensors cant be updated OTA. (If it relly is battery powered). I think I read a define somewhere that disables the firmware low level commands in the MySensors Library if the Node is battery powered.