[SOLVED] No example working [Arduino 1.6.7]


#1

Hi. I received my two Duos and

  1. updated Arduino 1.6.7 with the board resources via BoardManager
  2. loaded, compiled and uploaded the BLINK and later the ScanNetwork examples

Both were uploaded correctly, but neither worked! (both Duos tested)
I see “uploading” flashing on the rgb led
After uploading the RGB-LED flashed BLUE about 5 times a second.

Any suggestions

------------- dumped compiling/upload messages (partially truncated) -------------------------------------------------
Sketch uses 2,904 bytes (1%) of program storage space. Maximum is 196,608 bytes.
Forcing reset using 1200bps open/close on port COM3
PORTS {COM3, } / {COM3, } => {}

…truncated

PORTS {COM3, } / {COM3, } => {}
Uploading using selected port: COM3
C:\Users\urs\Documents_Development\arduino-1.6.7\hardware\tools\avr/bin/avrdude -CC:\Users\urs\AppData\Local\Arduino15\packages\RedBear\hardware\STM32F2\0.2.3/avrdude_conf/avrdude.conf -v -v -v -v -pcortex-m3 -cavr109 -PCOM3 -b19200 -D -Uflash:w:C:\Users\urs\AppData\Local\Temp\build104952adca32e6d60a5f7ab21de4aee2.tmp/Duo_Blink.ino.hex:i

avrdude: Version 6.0.1, compiled on Apr 15 2015 at 19:59:58
Copyright © 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright © 2007-2009 Joerg Wunsch

     System wide configuration file is "C:\Users\urs\AppData\Local\Arduino15\packages\RedBear\hardware\STM32F2\0.2.3/avrdude_conf/avrdude.conf"

     Using Port                    : COM3
     Using Programmer              : avr109
     Overriding Baud Rate          : 19200
     AVR Part                      : cortex-m3
     Chip Erase delay              : 9000 us
     PAGEL                         : PD7
     BS2                           : PA0
     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
       ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
       flash         65    10    64    0 yes    262144 4096     64  4500  4500 0x00 0x00
                              Block Poll               Page                       Polled
       Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
       ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
       signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

     Programmer Type : butterfly
     Description     : Atmel AppNote AVR109 Boot Loader

Connecting to programmer: .avrdude: Send: . [1b]
avrdude: Send: S [53]
avrdude: Recv: R [52]

avrdude: Recv: B [42] L [4c] - [2d] D [44] U [55] O [4f]
avrdude: Send: V [56]
avrdude: Recv: 1 [31] 0 [30]
avrdude: Send: v [76]
avrdude: Recv: 1 [31]
avrdude: Recv: 0 [30]
avrdude: Send: p [70]
avrdude: Recv: S [53]
Found programmer: Id = “RBL-DUO”; type = S
Software Version = 1.0; Hardware Version = 1.0
avrdude: Send: a [61]
avrdude: Recv: Y [59]
Programmer supports auto addr increment.
avrdude: Send: b [62]
avrdude: Recv: Y [59]
avrdude: Recv: . [00]
avrdude: Recv: @ [40]
Programmer supports buffered memory access with buffersize=64 bytes.
avrdude: Send: t [74]

Programmer supports the following devices:
avrdude: Recv: D [44]
Device code: 0x44
avrdude: Recv: . [00]

avrdude: Send: T [54] D [44]
avrdude: Recv: . [0d]
avrdude: devcode selected: 0x44
avrdude: Send: P [50]
avrdude: Recv: . [0d]
avrdude: AVR device initialized and ready to accept instructions

Reading | avrdude: Send: s [73]
avrdude: Recv: . [0b] . [90] . [1e]
################################################## | 100% 0.00s

avrdude: Device signature = 0x1e900b
avrdude: reading input file “C:\Users\urs\AppData\Local\Temp\build104952adca32e6d60a5f7ab21de4aee2.tmp/Duo_Blink.ino.hex”
avrdude: writing flash (2984 bytes):

Writing | avrdude: Send: A [41] . [00] . [00]
avrdude: Recv: . [0d]
avrdude: Send: B [42] . [00] @ [40] F [46] . [00] . [00] . [0c] . [08] . [a4] . [0b] . [0c] . [08] . [00] . [00] . [04] . [00] X [58] . [00] . [05] . [01] . [04] . [02] . [04] . [00] . [00] . [00] . [00] . [00] P [50] . [0a] . [0c] . [08] . [02] K [4b] . [01] ! [21] . [18] . [88] . [00] . [f0] . [9f] . [bb] . [00] . [bf] . [00] . [03] . [00] [20] . [10] . [b5] . [09] L [4c] . [01] ! [21] [20] . [88] . [00] . [f0] . [a7] . [fb] O [4f] . [f4] z [7a] p [70] . [00] . [f0] . [d2] . [f9]
avrdude: Recv: . [0d]

…truncated

avrdude: Send: B [42] . [00] @ [40] F [46] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: Recv: . [0d]
################################################## | 100% 0.47s

avrdude: 2984 bytes of flash written
avrdude: verifying flash memory against C:\Users\urs\AppData\Local\Temp\build104952adca32e6d60a5f7ab21de4aee2.tmp/Duo_Blink.ino.hex:
avrdude: load data flash data from input file C:\Users\urs\AppData\Local\Temp\build104952adca32e6d60a5f7ab21de4aee2.tmp/Duo_Blink.ino.hex:
avrdude: input file C:\Users\urs\AppData\Local\Temp\build104952adca32e6d60a5f7ab21de4aee2.tmp/Duo_Blink.ino.hex contains 2984 bytes
avrdude: reading on-chip flash data:

Reading | avrdude: Send: A [41] . [00] . [00]
avrdude: Recv: . [0d]
avrdude: Send: g [67] . [00] @ [40] F [46]
avrdude: Recv: . [00] . [00] . [0c] . [08] . [a4] . [0b] . [0c] . [08] . [00] . [00] . [04] . [00] X [58] . [00] . [05] . [01] . [04] . [02] . [04] . [00] . [00] . [00] . [00] . [00] P [50] . [0a] . [0c] . [08] . [02] K [4b] . [01] ! [21] . [18] . [88] . [00] . [f0] . [9f] . [bb] . [00] . [bf] . [00] . [03] . [00] [20] . [10] . [b5] . [09] L [4c] . [01] ! [21] [20] . [88] . [00] . [f0] . [a7] . [fb] O [4f] . [f4] z [7a] p [70] . [00] . [f0] . [d2] . [f9]
avrdude: Send: g [67] . [00] @ [40] F [46]

…truncated

avrdude: Send: g [67] . [00] @ [40] F [46]
avrdude: Recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
################################################## | 100% 0.82s

avrdude: avr_read(): skipping page 1: no interesting data

…truncated

avrdude: avr_read(): skipping page 63: no interesting data
avrdude: verifying …
avrdude: 2984 bytes of flash verified
avrdude: Send: L [4c]
avrdude: Recv: . [0d]
avrdude: Send: E [45]
avrdude: Recv: . [0d]

avrdude done. Thank you.


#2

Hi,

The RGB status led blinking blue means that your Duo is in listening mode, which is for you to provision WiFi profile. To quick test the sketch you uploaded, set the system mode to MANUAL in sketch:

SYSTEM_MODE(MANUAL);//do not connect to cloud.

BTW, the board package version v0.2.3 in Boards Manager should work with firmware version v0.2.2. Please follow the Getting Started Guide to update your Duo’s firmware first. Besides, ensure that you are using the examples under “File>Examples>RedBear_Duo”.

Cheers!


#3
  1. as I wrote both sketches were from the (redbear_duo) example.
  2. BOTH have the setting SYSTEM_MODE(MANUAL); included
  3. for a newly received board it should NOT be necessarily to make a firmware update first.
    that’s NOT consumer friendly. checked my version is 0.2.1 ; VERY unfriendly
    I will come back after an update …

#4

Hi @ursm,

Sorry for suffering from a bad out-of-box experience.

Since the firmware is still under development, we strongly suggest you visit the RedBear Duo GitHub page often to check out new updates and new functions as they will be rolled out frequently.

The firmware version and board package version should work corporately:

Firmware Version --> Arduino Board Package Version
v0.1.1 --> v0.1.1
v0.2.0 --> v0.2.1
v0.2.1 --> v0.2.2
v0.2.2 --> v0.2.3

The reason why firmware version can not be the same with Arduino board package version is that the board package has more bug to be fixed because of Arduino IDE. Thus, in the future, there may be several board package versions work with one firmware version.

We are working hard to improve the user experience, please give us time to make it be a better platform.

Cheers!


#5

so, after updating the firmware, both example sketches worked fine.
–> [SOLVED]


#6

For anyone who has problems with using examples on Arduino IDE, or wants to check the compatibility between the board package version and firmware version, please refer to https://github.com/redbear/STM32-Arduino/blob/master/VERSION.md

Thanks!


#7

Hi,

I have the same problem. My out of box experience also very bad:
Archiving built core (caching) in: /var/folders/sq/s5pxjz8505b48fcjfmvvb25h0000gn/T/arduino_cache_107978/core/core_RedBear_STM32F2_RedBear_Duo_native_922cca7ea847577b7918781b411e542f.a
32+0 records in
32+0 records out
32 bytes transferred in 0.021414 secs (1494 bytes/sec)
4+0 records in
4+0 records out
4 bytes transferred in 0.062880 secs (64 bytes/sec)
Sketch uses 3976 bytes (1%) of program storage space. Maximum is 262144 bytes.
Found programmer: Id = “RBL-DUO”; type = S
Software Version = 1.0; Hardware Version = 1.0
Programmer supports buffered memory access with buffersize=64 bytes.

and not uploading…