Windows GUI/Controller for MySensors

[rvendrame]

@f1dev, I'm just trying to thinking 'out of the box'. I really don't know why the MYSBootloader doesn't work (while the original arduino bootloader does).

@scalz, @tekka, looking at MYSBootloader makefile at github, I noticed you are using

ISP_PORT = com5
ISP_SPEED = 115200
ISP_PROTOCOL = stk500v2
ISP_MCU = m328p 

Well, my 'Arduino as ISP' only work as 'stk500v1' and 19200 bps --- Any other combination causes the "Yikes! invalid signature found" in avrdude, or no response at all (time-out). Could be that a different avr itself would introduce "strange bytes" during bootloader burning?

[tekka]

@rvendrame let me try some things here - can you make sure, that the MYSBootloader your are trying to flash is the one from the library and/or MYSController folder (maybe you can upload it here)?
Importantly, there is no need to re-compile MYSBootloader as it has been successfully tested down to 3.3V and 125kHz pro-minis (!). Can you please update your Arduino IDE to 1.6.5 so that we both run the same version?

[tekka]

@rvendrame the speed is not really an issue here - the bytes are verified after flashing...

[rvendrame]

@tekka, thank you so much. I have downloaded the .hex again from github, just for the sake. Anyway it is here MYSBootloader.hex I'm using.

[tekka]

@rvendrame said:

Hello guys, I'm trying to burn the MYSBootloader.hex into some Pro minis (clones) here, however after burning it, they get somehow 'bricked' :

• I'm using my Uno "as ISP" on IDE 1.6.4
• I've followed the step-by-step tutorial posted above by @tekka
• My pro-minis are 5V, 16Mhz, external clock , 328p, supposedly a perfect match with 'boards.txt' info...
• "Burn bootloader" ends successful, with "Done burning boot loader" message.
• After that, the pro-mini pin 13 led flashes in a kind of random pattern, and it is not possible to upload any sketch, nor any kind of serial monitor on any speed.
• I can revert it, by selecting the standard 'Arduino Pro or Pro Mini' board , and burn boot loader again. It makes the pro-mini gets back to live, I can upload my sketches and serial monitor it.

So my questions:

• I don't have extra eprom connected --- Is it mandatory? I've read somewhere that it can be disabled, but can't find the instructions anymore...
• Fuse adjustments?
• What else can I do in order to troubleshooting it?

Thanks!

How do you know that the bootloader is not functioning properly? you connected the RF module as mentioned earlier? The led is blinking irregularly due to SPI...Do you get a startup message (from MYSBootloader) in MYSController?

The 327xx bytes mentioned in verbose mode are correct - the entire flash is overwritten...

[rvendrame]

Yes, I connect the radio and start the node, but nothing happens --- No serial monitor, nothing in MYSController. Just the pin 13 led flashing randomly.

[tekka]

@rvendrame said:

Yes, I connect the radio and start the node, but nothing happens --- No serial monitor, nothing in MYSController. Just the pin 13 led flashing randomly.

Just flashed MYSController.hex on my Arduino pro mini 3V3 and the fuses as mentioned in the boards.txt (L: 0xF7 E: 0x06 H: 0xDA), using USBasp and everything works smoothly...

Please keep in mind: There is no serial monitor for MYSBootloader and the 13 led flashing is normal

Can you try this (in the indicated order):
0) Update Arduino IDE to 1.6.5

1. burn the original bootloader and upload the clear eeprom sketch
2. burn MYSController, disconnect flasher and connect nRF24L01+ module
3. download the most recent MySensors 1.5 library and upload the GW sketch
4. launch MYSController 0.1.2.282, activate AutoID, Logging and connect to the serial GW
5. let it run for a few mins and upload the log-file here

[rvendrame]

@tekka, just to clarify, in step 4 above - the 'upload GW sketch' should be OTA? Or via regular FT232 adapter?

[scalz]

@rvendrame: I think it is ota. With MYSBootloader you can't use ftdi for uploading sketch.

[rvendrame]

@scalz, thx. I will give it a try tonight.

[tekka]

@rvendrame said:

@tekka, just to clarify, in step 4 above - the 'upload GW sketch' should be OTA? Or via regular FT232 adapter?

I meant to update the Gateway node with the most recent Serialgateway sketch...

[rvendrame]

@tekka said:

I meant to update the Gateway node with the most recent Serialgateway sketch...

Yep, I'm already on latest version on GW. My GW runs on a pro-mini, with standard bootloader --- I guess this is not a issue?

[tekka]

@rvendrame said:

@tekka said:

I meant to update the Gateway node with the most recent Serialgateway sketch...

Yep, I'm already on latest version on GW. My GW runs on a pro-mini, with standard bootloader --- I guess this is not a issue?

and MYSController is connected via USB/FTDI to the GW...?

[rvendrame]

@tekka said:

and MYSController is connected via USB/FTDI to the GW...?

It is connected via USB/FTDI into a mac-mini running a TCP-to-serial SW. (so both Vera and MYSController can reach it using IP address). Works like a charm, I can see all nodes and messages, no connection issues so far.

Is it required the GW running on MYSBootloader? I hope not...

[tekka]

@rvendrame Sensor nodes with MYSBootloader (unless they are Sensebender boards) and GW with original bootloader. Curious to see your logs.

[rvendrame]

EDIT: @tekka, @scalz , after so many tries, I don't know why I decided to replace the nRF radio , and guess what?

Funny thing is that the previous radio is working with regular bootloader. Dam fake chips! But I will sort it out later, now I want to play with my OTA ;-)

Thanks a lot!

[scalz]

@rvendrame: so cool. I am happy for you!
See you soon

[Francois]

@tekka do MYSBootloader also work with the RFM69 radios?

[tekka]

@rvendrame excellent :)

[tekka]

@Francois No, in it's current stage only nRF24L01+, but porting to RFM69 should not be too difficult...