Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Development
  3. MYSBootloader 1.3.0-beta.3

MYSBootloader 1.3.0-beta.3

Scheduled Pinned Locked Moved Development
182 Posts 44 Posters 59.4k Views 42 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • gohanG Offline
    gohanG Offline
    gohan
    Mod
    wrote on last edited by
    #117

    I think you have to issue a reboot node from the mycontroller or myscontroller to have the OTA start

    M 1 Reply Last reply
    0
    • gohanG gohan

      I think you have to issue a reboot node from the mycontroller or myscontroller to have the OTA start

      M Offline
      M Offline
      moskovskiy82
      wrote on last edited by
      #118

      @gohan So is it first reboot. Or start flashing - reboot?

      J 1 Reply Last reply
      0
      • gohanG Offline
        gohanG Offline
        gohan
        Mod
        wrote on last edited by
        #119

        You assign firmware to upload to node and then you send a reboot, if I remember correctly

        1 Reply Last reply
        1
        • M moskovskiy82

          @gohan So is it first reboot. Or start flashing - reboot?

          J Offline
          J Offline
          jkandasa
          Plugin Developer
          wrote on last edited by
          #120

          @moskovskiy82 If you use MyController, Yes, you should assign the firmware for the node and send reboot.

          M 1 Reply Last reply
          0
          • J jkandasa

            @moskovskiy82 If you use MyController, Yes, you should assign the firmware for the node and send reboot.

            M Offline
            M Offline
            moskovskiy82
            wrote on last edited by moskovskiy82
            #121

            @jkandasa Thank you!

            One more question. Now need to use a 3,3V arduino Pro (chinese version) (Nano and 5V version flashed via the uno without a hitch)

            This is what i put into boards.txt The MYSBootloader_8Mhz.hex is from the dev branch

            proMYSBL8.name=ATmega328 8Mhz MYSBootloader
            
            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=0xDA
            proMYSBL8.bootloader.extended_fuses=0x06
            proMYSBL8.bootloader.unlock_bits=0x3F
            proMYSBL8.bootloader.lock_bits=0xFF
            proMYSBL8.bootloader.file=MySensors/MYSBootloader_8Mhz.hex
            proMYSBL8.build.mcu=atmega328p
            proMYSBL8.build.f_cpu=8000000L
            proMYSBL8.build.board=AVR_UNO
            proMYSBL8.build.core=arduino
            proMYSBL8.build.variant=standard
            

            Tried to flash the mysbootloader but get the following error

            C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avrdude -CC:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM7 -b19200 -e -Ulock:w:0x3F:m -Uefuse:w:0x06:m -Uhfuse:w:0xDA:m -Ulfuse:w:0xE2:m 
            
            avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53
                     Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
                     Copyright (c) 2007-2014 Joerg Wunsch
            
                     System wide configuration file is "C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf"
            
                     Using Port                    : COM7
                     Using Programmer              : stk500v1
                     Overriding Baud Rate          : 19200
                     AVR Part                      : ATmega328P
                     Chip Erase delay              : 9000 us
                     PAGEL                         : PD7
                     BS2                           : PC2
                     RESET disposition             : dedicated
                     RETRY pulse                   : SCK
                     serial program mode           : yes
                     parallel program mode         : yes
                     Timeout                       : 200
                     StabDelay                     : 100
                     CmdexeDelay                   : 25
                     SyncLoops                     : 32
                     ByteDelay                     : 0
                     PollIndex                     : 3
                     PollValue                     : 0x53
                     Memory Detail                 :
            
                                              Block Poll               Page                       Polled
                       Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
                       ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
                       eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
                       flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
                       lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                       hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                       efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                       lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                       calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
                       signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00
            
                     Programmer Type : STK500
                     Description     : Atmel STK500 Version 1.x firmware
                     Hardware Version: 2
                     Firmware Version: 1.18
                     Topcard         : Unknown
                     Vtarget         : 0.0 V
                     Varef           : 0.0 V
                     Oscillator      : Off
                     SCK period      : 0.1 us
            
            avrdude: AVR device initialized and ready to accept instructions
            
            Reading | ################################################## | 100% 0.03s
            
            avrdude: Device signature = 0x1e950f (probably m328p)
            avrdude: erasing chip
            avrdude: reading input file "0x3F"
            avrdude: writing lock (1 bytes):
            
            Writing | ################################################## | 100% 0.01s
            
            avrdude: 1 bytes of lock written
            avrdude: verifying lock memory against 0x3F:
            avrdude: load data lock data from input file 0x3F:
            avrdude: input file 0x3F contains 1 bytes
            avrdude: reading on-chip lock data:
            
            Reading | ################################################## | 100% 0.01s
            
            avrdude: verifying ...
            avrdude: 1 bytes of lock verified
            avrdude: reading input file "0x06"
            avrdude: writing efuse (1 bytes):
            
            Writing |  ***failed;  
            ################################################## | 100% 0.07s
            
            avrdude: 1 bytes of efuse written
            avrdude: verifying efuse memory against 0x06:
            avrdude: load data efuse data from input file 0x06:
            avrdude: input file 0x06 contains 1 bytes
            avrdude: reading on-chip efuse data:
            
            Reading | ################################################## | 100% 0.01s
            
            avrdude: verifying ...
            avrdude: WARNING: invalid value for unused bits in fuse "efuse", should be set to 1 according to datasheet
            This behaviour is deprecated and will result in an error in future version
            You probably want to use 0xfe instead of 0x06 (double check with your datasheet first).
            avrdude: 1 bytes of efuse verified
            avrdude: reading input file "0xDA"
            avrdude: writing hfuse (1 bytes):
            
            Writing | ################################################## | 100% 0.01s
            
            avrdude: 1 bytes of hfuse written
            avrdude: verifying hfuse memory against 0xDA:
            avrdude: load data hfuse data from input file 0xDA:
            avrdude: input file 0xDA contains 1 bytes
            avrdude: reading on-chip hfuse data:
            
            C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avrdude -CC:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM7 -b19200 -Uflash:w:C:\Program Files (x86)\Arduino\hardware\arduino\avr/bootloaders/MySensors/MYSBootloader_8Mhz.hex:i -Ulock:w:0xFF:m 
            
            avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53
            Reading | ################################################## | 100% 0.01s
                     Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
            
                     Copyright (c) 2007-2014 Joerg Wunsch
            avrdude: verifying ...
            
            avrdude: 1 bytes of hfuse verified
                     System wide configuration file is "C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf"
            avrdude: reading input file "0xE2"
            avrdude: writing lfuse (1 bytes):
            
            Writing | ################################################## | 100% 0.01s
            
            avrdude: 1 bytes of lfuse written
            avrdude: verifying lfuse memory against 0xE2:
            avrdude: load data lfuse data from input file 0xE2:
            avrdude: input file 0xE2 contains 1 bytes
            avrdude: reading on-chip lfuse data:
            
            Reading | ################################################## | 100% 0.01s
            
            avrdude: verifying ...
            avrdude: 1 bytes of lfuse verified
            
            avrdude done.  Thank you.
            
            
                     Using Port                    : COM7
                     Using Programmer              : stk500v1
                     Overriding Baud Rate          : 19200
                     AVR Part                      : ATmega328P
                     Chip Erase delay              : 9000 us
                     PAGEL                         : PD7
                     BS2                           : PC2
                     RESET disposition             : dedicated
                     RETRY pulse                   : SCK
                     serial program mode           : yes
                     parallel program mode         : yes
                     Timeout                       : 200
                     StabDelay                     : 100
                     CmdexeDelay                   : 25
                     SyncLoops                     : 32
                     ByteDelay                     : 0
                     PollIndex                     : 3
                     PollValue                     : 0x53
                     Memory Detail                 :
            
                                              Block Poll               Page                       Polled
                       Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
                       ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
                       eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
                       flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
                       lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                       hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                       efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                       lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                       calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
                       signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00
            
                     Programmer Type : STK500
                     Description     : Atmel STK500 Version 1.x firmware
                     Hardware Version: 2
                     Firmware Version: 1.18
                     Topcard         : Unknown
                     Vtarget         : 0.0 V
                     Varef           : 0.0 V
                     Oscillator      : Off
                     SCK period      : 0.1 us
            
            avrdude: AVR device initialized and ready to accept instructions
            
            Reading | ################################################## | 100% 0.02s
            
            avrdude: Device signature = 0x1e950f (probably m328p)
            avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
                     To disable this feature, specify the -D option.
            avrdude: erasing chip
            avrdude: reading input file "C:\Program Files (x86)\Arduino\hardware\arduino\avr/bootloaders/MySensors/MYSBootloader_8Mhz.hex"
            avrdude: writing flash (32754 bytes):
            
            Writing | ################################################## | 100% 0.00s
            
            avrdude: 32754 bytes of flash written
            avrdude: verifying flash memory against C:\Program Files (x86)\Arduino\hardware\arduino\avr/bootloaders/MySensors/MYSBootloader_8Mhz.hex:
            avrdude: load data flash data from input file C:\Program Files (x86)\Arduino\hardware\arduino\avr/bootloaders/MySensors/MYSBootloader_8Mhz.hex:
            avrdude: input file C:\Program Files (x86)\Arduino\hardware\arduino\avr/bootloaders/MySensors/MYSBootloader_8Mhz.hex contains 32754 bytes
            avrdude: reading on-chip flash data:
            
            Reading | ################################################## | 100% 0.00s
            
            avrdude: verifying ...
            avrdude: verification error, first mismatch at byte 0x7800
                     0x00 != 0x11
            avrdude: verification error; content mismatch
            
            avrdude done.  Thank you.
            
            Error while burning bootloader.
            
            
            luizrrochaL 1 Reply Last reply
            0
            • M moskovskiy82

              @jkandasa Thank you!

              One more question. Now need to use a 3,3V arduino Pro (chinese version) (Nano and 5V version flashed via the uno without a hitch)

              This is what i put into boards.txt The MYSBootloader_8Mhz.hex is from the dev branch

              proMYSBL8.name=ATmega328 8Mhz MYSBootloader
              
              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=0xDA
              proMYSBL8.bootloader.extended_fuses=0x06
              proMYSBL8.bootloader.unlock_bits=0x3F
              proMYSBL8.bootloader.lock_bits=0xFF
              proMYSBL8.bootloader.file=MySensors/MYSBootloader_8Mhz.hex
              proMYSBL8.build.mcu=atmega328p
              proMYSBL8.build.f_cpu=8000000L
              proMYSBL8.build.board=AVR_UNO
              proMYSBL8.build.core=arduino
              proMYSBL8.build.variant=standard
              

              Tried to flash the mysbootloader but get the following error

              C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avrdude -CC:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM7 -b19200 -e -Ulock:w:0x3F:m -Uefuse:w:0x06:m -Uhfuse:w:0xDA:m -Ulfuse:w:0xE2:m 
              
              avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53
                       Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
                       Copyright (c) 2007-2014 Joerg Wunsch
              
                       System wide configuration file is "C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf"
              
                       Using Port                    : COM7
                       Using Programmer              : stk500v1
                       Overriding Baud Rate          : 19200
                       AVR Part                      : ATmega328P
                       Chip Erase delay              : 9000 us
                       PAGEL                         : PD7
                       BS2                           : PC2
                       RESET disposition             : dedicated
                       RETRY pulse                   : SCK
                       serial program mode           : yes
                       parallel program mode         : yes
                       Timeout                       : 200
                       StabDelay                     : 100
                       CmdexeDelay                   : 25
                       SyncLoops                     : 32
                       ByteDelay                     : 0
                       PollIndex                     : 3
                       PollValue                     : 0x53
                       Memory Detail                 :
              
                                                Block Poll               Page                       Polled
                         Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
                         ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
                         eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
                         flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
                         lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                         hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                         efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                         lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                         calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
                         signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00
              
                       Programmer Type : STK500
                       Description     : Atmel STK500 Version 1.x firmware
                       Hardware Version: 2
                       Firmware Version: 1.18
                       Topcard         : Unknown
                       Vtarget         : 0.0 V
                       Varef           : 0.0 V
                       Oscillator      : Off
                       SCK period      : 0.1 us
              
              avrdude: AVR device initialized and ready to accept instructions
              
              Reading | ################################################## | 100% 0.03s
              
              avrdude: Device signature = 0x1e950f (probably m328p)
              avrdude: erasing chip
              avrdude: reading input file "0x3F"
              avrdude: writing lock (1 bytes):
              
              Writing | ################################################## | 100% 0.01s
              
              avrdude: 1 bytes of lock written
              avrdude: verifying lock memory against 0x3F:
              avrdude: load data lock data from input file 0x3F:
              avrdude: input file 0x3F contains 1 bytes
              avrdude: reading on-chip lock data:
              
              Reading | ################################################## | 100% 0.01s
              
              avrdude: verifying ...
              avrdude: 1 bytes of lock verified
              avrdude: reading input file "0x06"
              avrdude: writing efuse (1 bytes):
              
              Writing |  ***failed;  
              ################################################## | 100% 0.07s
              
              avrdude: 1 bytes of efuse written
              avrdude: verifying efuse memory against 0x06:
              avrdude: load data efuse data from input file 0x06:
              avrdude: input file 0x06 contains 1 bytes
              avrdude: reading on-chip efuse data:
              
              Reading | ################################################## | 100% 0.01s
              
              avrdude: verifying ...
              avrdude: WARNING: invalid value for unused bits in fuse "efuse", should be set to 1 according to datasheet
              This behaviour is deprecated and will result in an error in future version
              You probably want to use 0xfe instead of 0x06 (double check with your datasheet first).
              avrdude: 1 bytes of efuse verified
              avrdude: reading input file "0xDA"
              avrdude: writing hfuse (1 bytes):
              
              Writing | ################################################## | 100% 0.01s
              
              avrdude: 1 bytes of hfuse written
              avrdude: verifying hfuse memory against 0xDA:
              avrdude: load data hfuse data from input file 0xDA:
              avrdude: input file 0xDA contains 1 bytes
              avrdude: reading on-chip hfuse data:
              
              C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avrdude -CC:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM7 -b19200 -Uflash:w:C:\Program Files (x86)\Arduino\hardware\arduino\avr/bootloaders/MySensors/MYSBootloader_8Mhz.hex:i -Ulock:w:0xFF:m 
              
              avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53
              Reading | ################################################## | 100% 0.01s
                       Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
              
                       Copyright (c) 2007-2014 Joerg Wunsch
              avrdude: verifying ...
              
              avrdude: 1 bytes of hfuse verified
                       System wide configuration file is "C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf"
              avrdude: reading input file "0xE2"
              avrdude: writing lfuse (1 bytes):
              
              Writing | ################################################## | 100% 0.01s
              
              avrdude: 1 bytes of lfuse written
              avrdude: verifying lfuse memory against 0xE2:
              avrdude: load data lfuse data from input file 0xE2:
              avrdude: input file 0xE2 contains 1 bytes
              avrdude: reading on-chip lfuse data:
              
              Reading | ################################################## | 100% 0.01s
              
              avrdude: verifying ...
              avrdude: 1 bytes of lfuse verified
              
              avrdude done.  Thank you.
              
              
                       Using Port                    : COM7
                       Using Programmer              : stk500v1
                       Overriding Baud Rate          : 19200
                       AVR Part                      : ATmega328P
                       Chip Erase delay              : 9000 us
                       PAGEL                         : PD7
                       BS2                           : PC2
                       RESET disposition             : dedicated
                       RETRY pulse                   : SCK
                       serial program mode           : yes
                       parallel program mode         : yes
                       Timeout                       : 200
                       StabDelay                     : 100
                       CmdexeDelay                   : 25
                       SyncLoops                     : 32
                       ByteDelay                     : 0
                       PollIndex                     : 3
                       PollValue                     : 0x53
                       Memory Detail                 :
              
                                                Block Poll               Page                       Polled
                         Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
                         ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
                         eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
                         flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
                         lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                         hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                         efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                         lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                         calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
                         signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00
              
                       Programmer Type : STK500
                       Description     : Atmel STK500 Version 1.x firmware
                       Hardware Version: 2
                       Firmware Version: 1.18
                       Topcard         : Unknown
                       Vtarget         : 0.0 V
                       Varef           : 0.0 V
                       Oscillator      : Off
                       SCK period      : 0.1 us
              
              avrdude: AVR device initialized and ready to accept instructions
              
              Reading | ################################################## | 100% 0.02s
              
              avrdude: Device signature = 0x1e950f (probably m328p)
              avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
                       To disable this feature, specify the -D option.
              avrdude: erasing chip
              avrdude: reading input file "C:\Program Files (x86)\Arduino\hardware\arduino\avr/bootloaders/MySensors/MYSBootloader_8Mhz.hex"
              avrdude: writing flash (32754 bytes):
              
              Writing | ################################################## | 100% 0.00s
              
              avrdude: 32754 bytes of flash written
              avrdude: verifying flash memory against C:\Program Files (x86)\Arduino\hardware\arduino\avr/bootloaders/MySensors/MYSBootloader_8Mhz.hex:
              avrdude: load data flash data from input file C:\Program Files (x86)\Arduino\hardware\arduino\avr/bootloaders/MySensors/MYSBootloader_8Mhz.hex:
              avrdude: input file C:\Program Files (x86)\Arduino\hardware\arduino\avr/bootloaders/MySensors/MYSBootloader_8Mhz.hex contains 32754 bytes
              avrdude: reading on-chip flash data:
              
              Reading | ################################################## | 100% 0.00s
              
              avrdude: verifying ...
              avrdude: verification error, first mismatch at byte 0x7800
                       0x00 != 0x11
              avrdude: verification error; content mismatch
              
              avrdude done.  Thank you.
              
              Error while burning bootloader.
              
              
              luizrrochaL Offline
              luizrrochaL Offline
              luizrrocha
              wrote on last edited by
              #122

              @moskovskiy82 My boards.txt specify bootloader.low_fuses=0xF7 as the Arduino being programmed has a crystal on board.

              One other thing: I built my own programming board, to support programming ATMega 328p chips and Pro boards in 3.3v@8MHz and 5v@16Mhz... I used a switch and a level converter board to connect the Uno ICSP port to the pins of the Pro.

              Uno pins are 5V output, they would burn the input pins of the 3.3v Pro chip, did you account for that ?

              1 Reply Last reply
              0
              • gohanG Offline
                gohanG Offline
                gohan
                Mod
                wrote on last edited by
                #123

                You can use 5v to program a 3.3v pro mini as the chip is the same, one is only clocked down to 8Mhz in order to be stable at 3.3v

                luizrrochaL 1 Reply Last reply
                0
                • gohanG gohan

                  You can use 5v to program a 3.3v pro mini as the chip is the same, one is only clocked down to 8Mhz in order to be stable at 3.3v

                  luizrrochaL Offline
                  luizrrochaL Offline
                  luizrrocha
                  wrote on last edited by
                  #124

                  @gohan I beg to differ. On Page 299 of Atmel's ATMega 328p datasheet you can verify that the Absolute Maximum Ratings table states : "Voltage on any Pin except RESET with respect to Ground . . . . . . . . . .-0.5V to VCC+0.5V" which adds to 3.8V for a 3.3V Pro.

                  And also: *NOTICE: Stresses beyond those listed under “Absolute Maximum Ratings” may cause permanent damage to the device.

                  Perhaps you have mistaken the Pro for the NRF24L01+ radio which is supplied by 3.3v but has 5Volt tolerant inputs ?

                  Otherwise there would be no need for those USB to FTDI boards with 3v3/5V selection jumpers ...

                  1 Reply Last reply
                  0
                  • gohanG Offline
                    gohanG Offline
                    gohan
                    Mod
                    wrote on last edited by gohan
                    #125

                    I programmed the pro mini with 5v and it worked. Maybe I was lucky. The 3v ftdi adapter is mandatory for esp8266 for example.

                    1 Reply Last reply
                    0
                    • tekkaT tekka

                      @Mark-Swift I haven't tested that with OSX - maybe somebody can help here?

                      ? Offline
                      ? Offline
                      A Former User
                      wrote on last edited by
                      #126

                      @tekka for OSX, the sequencing of flags matters. So, line 45 can be:

                      $(PROJECT).o: $(PROJECT).c
                      "$(BINPATH)avr-gcc" $(CFLAGS) -I$(INCLUDES) $< -o $@
                      

                      can be improved to

                      $(PROJECT).o: $(PROJECT).c
                      "$(BINPATH)avr-gcc" -I$(INCLUDES) $(CFLAGS) $< -o $@
                      

                      and it all works.

                      Also, if anyone is getting error for "avr-gcc" not found, then just add the path to avr-gcc in your path.

                      tekkaT 1 Reply Last reply
                      0
                      • ? A Former User

                        @tekka for OSX, the sequencing of flags matters. So, line 45 can be:

                        $(PROJECT).o: $(PROJECT).c
                        "$(BINPATH)avr-gcc" $(CFLAGS) -I$(INCLUDES) $< -o $@
                        

                        can be improved to

                        $(PROJECT).o: $(PROJECT).c
                        "$(BINPATH)avr-gcc" -I$(INCLUDES) $(CFLAGS) $< -o $@
                        

                        and it all works.

                        Also, if anyone is getting error for "avr-gcc" not found, then just add the path to avr-gcc in your path.

                        tekkaT Offline
                        tekkaT Offline
                        tekka
                        Admin
                        wrote on last edited by
                        #127

                        @Bhavin-Doshi Thanks for reporting - could you prepare a PR?
                        https://github.com/mysensors/MySensorsBootloaderRF24

                        ? 1 Reply Last reply
                        0
                        • tekkaT tekka

                          @Bhavin-Doshi Thanks for reporting - could you prepare a PR?
                          https://github.com/mysensors/MySensorsBootloaderRF24

                          ? Offline
                          ? Offline
                          A Former User
                          wrote on last edited by
                          #128

                          @tekka Submitted https://github.com/mysensors/MySensorsBootloaderRF24/pull/20.

                          tekkaT 1 Reply Last reply
                          0
                          • ? A Former User

                            @tekka Submitted https://github.com/mysensors/MySensorsBootloaderRF24/pull/20.

                            tekkaT Offline
                            tekkaT Offline
                            tekka
                            Admin
                            wrote on last edited by
                            #129

                            @Bhavin-Doshi PR merged. Thank you!

                            N 1 Reply Last reply
                            0
                            • tekkaT tekka

                              @Bhavin-Doshi PR merged. Thank you!

                              N Offline
                              N Offline
                              nagurao.basude
                              wrote on last edited by
                              #130

                              @tekka, I am planning to move from MySensors v2.0.0 to v2.1.1, do I need to use the updated MYSBootloader? Currently I am using MYSBootloader 1.3 pre-relase (https://forum.mysensors.org/topic/3453/mysbootloader-1-3-pre-release-myscontroller-1-0-0beta).

                              Can you please also help me understand the differences in the low_fuses and high_fuses values in the older version of bootloader and the latest version?

                              tekkaT 1 Reply Last reply
                              0
                              • N nagurao.basude

                                @tekka, I am planning to move from MySensors v2.0.0 to v2.1.1, do I need to use the updated MYSBootloader? Currently I am using MYSBootloader 1.3 pre-relase (https://forum.mysensors.org/topic/3453/mysbootloader-1-3-pre-release-myscontroller-1-0-0beta).

                                Can you please also help me understand the differences in the low_fuses and high_fuses values in the older version of bootloader and the latest version?

                                tekkaT Offline
                                tekkaT Offline
                                tekka
                                Admin
                                wrote on last edited by tekka
                                #131

                                @nagurao.basude no, you don't need to but the new version has some stability improvements. The fuse differences are to better match HW (osc type) & clearing eeprom.

                                AVR fuse calculator: http://www.engbedded.com/fusecalc/

                                N 1 Reply Last reply
                                0
                                • Nca78N Offline
                                  Nca78N Offline
                                  Nca78
                                  Hardware Contributor
                                  wrote on last edited by
                                  #132

                                  Hello, has someone used the 1MHz precompiled bootloader ? If yes what baud rate did you use to communicate via serial ?
                                  I flashed it on a node but I can't upload any script ("not in sync" error). If I believe HW.h it should be 9600 bauds but I have tried hat and nearly every baudrate with no luck.
                                  I had no problem using the 8MHz version.

                                  The only way I could use the 1MHz bootloader at the moment is to flash the hex file containing both bootloader and script.
                                  Sorry to ask this stupid question, I wanted to compile the bootloader but Internet connection is nearly down and I can't even download Atmel Studio :(

                                  1 Reply Last reply
                                  1
                                  • tekkaT tekka

                                    @nagurao.basude no, you don't need to but the new version has some stability improvements. The fuse differences are to better match HW (osc type) & clearing eeprom.

                                    AVR fuse calculator: http://www.engbedded.com/fusecalc/

                                    N Offline
                                    N Offline
                                    nagurao.basude
                                    wrote on last edited by
                                    #133

                                    @tekka Thank you very much for the response. I will just start migrating my existing nodes to MySensors v2.1.1library.

                                    1 Reply Last reply
                                    0
                                    • Mark SwiftM Offline
                                      Mark SwiftM Offline
                                      Mark Swift
                                      wrote on last edited by
                                      #134

                                      @tekka try as I might, I can't get the nodes to respond to the new 'signal report' option in MYS Controller, any ideas why?

                                      tekkaT 1 Reply Last reply
                                      0
                                      • Mark SwiftM Mark Swift

                                        @tekka try as I might, I can't get the nodes to respond to the new 'signal report' option in MYS Controller, any ideas why?

                                        tekkaT Offline
                                        tekkaT Offline
                                        tekka
                                        Admin
                                        wrote on last edited by
                                        #135

                                        @Mark-Swift This feature only works on MySensors >=2.2.0

                                        Mark SwiftM 1 Reply Last reply
                                        0
                                        • tekkaT tekka

                                          @Mark-Swift This feature only works on MySensors >=2.2.0

                                          Mark SwiftM Offline
                                          Mark SwiftM Offline
                                          Mark Swift
                                          wrote on last edited by
                                          #136

                                          @tekka said in MYSBootloader 1.3.0-beta.3:

                                          @Mark-Swift This feature only works on MySensors >=2.2.0

                                          @tekka I'm using the latest dev branch on all my nodes and gateway...

                                          tekkaT 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          17

                                          Online

                                          11.7k

                                          Users

                                          11.2k

                                          Topics

                                          113.0k

                                          Posts


                                          Copyright 2019 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • MySensors
                                          • OpenHardware.io
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular