[Tutorial] How to burn 1Mhz & 8Mhz bootloader using Arduino IDE 1.6.5-r5

[GertSanders]

@jacikaas

From the symptoms you describe, it seems the BOD is still set at the original 4.3V.

There is an Arduino sketch which allows an Arduino do check which fuses are set on another processor:

http://www.gammon.com.au/forum/?id=11633

This will allow you to be certain that the fuse settings on the slim node are correct.

The boards.txt file is just a settings file, so better to check the fuse settings on the processor itself.

[jacikaas]

@GertSanders

Thank You for reply! I got the results:

Atmega chip detector.
Written by Nick Gammon.
Version 1.18
Compiled on May  9 2016 at 11:25:03 with Arduino IDE 10605.
Attempting to enter ICSP programming mode ...
Entered programming mode OK.
Signature = 0x1E 0x95 0x0F 
Processor = ATmega328P
Flash memory size = 32768 bytes.
LFuse = 0x62 
HFuse = 0xDE 
EFuse = 0xFF 
Lock byte = 0xEF 
Clock calibration = 0xA0 
Bootloader in use: Yes
EEPROM preserved through erase: No
Watchdog timer always on: No
Bootloader is 512 bytes starting at 7E00

Bootloader:

7E00: 0x11 0x24 0x84 0xB7 0x14 0xBE 0x81 0xFF 0xE6 0xD0 0x85 0xE0 0x80 0x93 0x81 0x00 
7E10: 0x82 0xE0 0x80 0x93 0xC0 0x00 0x88 0xE1 0x80 0x93 0xC1 0x00 0x86 0xE0 0x80 0x93 
7E20: 0xC2 0x00 0x8C 0xE0 0x80 0x93 0xC4 0x00 0x8E 0xE0 0xBF 0xD0 0x25 0x9A 0x86 0xE0 
7E30: 0x23 0xEC 0x3F 0xEF 0x91 0xE0 0x30 0x93 0x85 0x00 0x20 0x93 0x84 0x00 0x96 0xBB 
7E40: 0xB0 0x9B 0xFE 0xCF 0x1D 0x9A 0xA8 0x95 0x81 0x50 0xA9 0xF7 0xEE 0x24 0xFF 0x24 
7E50: 0xAA 0x24 0xA3 0x94 0xB5 0xE0 0xCB 0x2E 0xA1 0xE1 0xBA 0x2E 0xF3 0xE0 0xDF 0x2E 
7E60: 0x98 0xD0 0x81 0x34 0x61 0xF4 0x95 0xD0 0x08 0x2F 0xA5 0xD0 0x02 0x38 0x29 0xF1 
7E70: 0x01 0x38 0x11 0xF4 0x85 0xE0 0x01 0xC0 0x83 0xE0 0x83 0xD0 0x7F 0xC0 0x82 0x34 
7E80: 0x11 0xF4 0x84 0xE1 0x03 0xC0 0x85 0x34 0x19 0xF4 0x85 0xE0 0x9C 0xD0 0x76 0xC0 
7E90: 0x85 0x35 0x79 0xF4 0x7E 0xD0 0xE8 0x2E 0xFF 0x24 0x7B 0xD0 0x08 0x2F 0x10 0xE0 
7EA0: 0x10 0x2F 0x00 0x27 0x0E 0x29 0x1F 0x29 0x00 0x0F 0x11 0x1F 0x84 0xD0 0x78 0x01 
7EB0: 0x65 0xC0 0x86 0x35 0x21 0xF4 0x84 0xE0 0x86 0xD0 0x80 0xE0 0xDE 0xCF 0x84 0x36 
7EC0: 0x09 0xF0 0x40 0xC0 0x66 0xD0 0x65 0xD0 0x08 0x2F 0x63 0xD0 0x80 0xE0 0xE8 0x16 
7ED0: 0x80 0xE7 0xF8 0x06 0x18 0xF4 0xF7 0x01 0xD7 0xBE 0xE8 0x95 0xC0 0xE0 0xD1 0xE0 
7EE0: 0x58 0xD0 0x89 0x93 0x0C 0x17 0xE1 0xF7 0xF0 0xE0 0xEF 0x16 0xF0 0xE7 0xFF 0x06 
7EF0: 0x18 0xF0 0xF7 0x01 0xD7 0xBE 0xE8 0x95 0x5E 0xD0 0x07 0xB6 0x00 0xFC 0xFD 0xCF 
7F00: 0xA7 0x01 0xA0 0xE0 0xB1 0xE0 0x2C 0x91 0x30 0xE0 0x11 0x96 0x8C 0x91 0x11 0x97 
7F10: 0x90 0xE0 0x98 0x2F 0x88 0x27 0x82 0x2B 0x93 0x2B 0x12 0x96 0xFA 0x01 0x0C 0x01 
7F20: 0xA7 0xBE 0xE8 0x95 0x11 0x24 0x4E 0x5F 0x5F 0x4F 0xF1 0xE0 0xA0 0x38 0xBF 0x07 
7F30: 0x51 0xF7 0xF7 0x01 0xC7 0xBE 0xE8 0x95 0x07 0xB6 0x00 0xFC 0xFD 0xCF 0xB7 0xBE 
7F40: 0xE8 0x95 0x1C 0xC0 0x84 0x37 0x61 0xF4 0x24 0xD0 0x23 0xD0 0x08 0x2F 0x21 0xD0 
7F50: 0x32 0xD0 0xF7 0x01 0x85 0x91 0x7F 0x01 0x14 0xD0 0x01 0x50 0xD1 0xF7 0x0E 0xC0 
7F60: 0x85 0x37 0x39 0xF4 0x28 0xD0 0x8E 0xE1 0x0C 0xD0 0x85 0xE9 0x0A 0xD0 0x8F 0xE0 
7F70: 0x84 0xCF 0x81 0x35 0x11 0xF4 0x88 0xE0 0x18 0xD0 0x1D 0xD0 0x80 0xE1 0x01 0xD0 
7F80: 0x6F 0xCF 0x98 0x2F 0x80 0x91 0xC0 0x00 0x85 0xFF 0xFC 0xCF 0x90 0x93 0xC6 0x00 
7F90: 0x08 0x95 0x80 0x91 0xC0 0x00 0x87 0xFF 0xFC 0xCF 0x80 0x91 0xC0 0x00 0x84 0xFD 
7FA0: 0x01 0xC0 0xA8 0x95 0x80 0x91 0xC6 0x00 0x08 0x95 0xE0 0xE6 0xF0 0xE0 0x98 0xE1 
7FB0: 0x90 0x83 0x80 0x83 0x08 0x95 0xED 0xDF 0x80 0x32 0x19 0xF0 0x88 0xE0 0xF5 0xDF 
7FC0: 0xFF 0xCF 0x84 0xE1 0xDE 0xCF 0x1F 0x93 0x18 0x2F 0xE3 0xDF 0x11 0x50 0xE9 0xF7 
7FD0: 0xF2 0xDF 0x1F 0x91 0x08 0x95 0x28 0x2E 0x80 0xE0 0xE7 0xDF 0xEE 0x27 0xFF 0x27 
7FE0: 0x09 0x94 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 
7FF0: 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x00 0x05 

MD5 sum of bootloader = 0xFD 0x26 0x6D 0xCC 0x38 0xDB 0xDF 0xB3 0x19 0xC2 0x21 0x79 0xBD 0x24 0x58 0x72 
Bootloader MD5 sum not known.

First 256 bytes of program memory:

0: 0x0C 0x94 0x5C 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 
10: 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 
20: 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 
30: 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 
40: 0x0C 0x94 0x88 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 
50: 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 
60: 0x0C 0x94 0x6E 0x00 0x0C 0x94 0x6E 0x00 0x00 0x00 0x00 0x08 0x00 0x02 0x01 0x00 
70: 0x00 0x03 0x04 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x02 0x04 0x08 
80: 0x10 0x20 0x40 0x80 0x01 0x02 0x04 0x08 0x10 0x20 0x01 0x02 0x04 0x08 0x10 0x20 
90: 0x04 0x04 0x04 0x04 0x04 0x04 0x04 0x04 0x02 0x02 0x02 0x02 0x02 0x02 0x03 0x03 
A0: 0x03 0x03 0x03 0x03 0x00 0x00 0x00 0x00 0x25 0x00 0x28 0x00 0x2B 0x00 0x00 0x00 
B0: 0x00 0x00 0x24 0x00 0x27 0x00 0x2A 0x00 0x11 0x24 0x1F 0xBE 0xCF 0xEF 0xD8 0xE0 
C0: 0xDE 0xBF 0xCD 0xBF 0x21 0xE0 0xA0 0xE0 0xB1 0xE0 0x01 0xC0 0x1D 0x92 0xA9 0x30 
D0: 0xB2 0x07 0xE1 0xF7 0x0E 0x94 0xEE 0x01 0x0C 0x94 0xFE 0x01 0x0C 0x94 0x00 0x00 
E0: 0x61 0xE0 0x8D 0xE0 0x0C 0x94 0x7E 0x01 0x61 0xE0 0x8D 0xE0 0x0E 0x94 0xB7 0x01 
F0: 0x68 0xEE 0x73 0xE0 0x80 0xE0 0x90 0xE0 0x0E 0x94 0xF5 0x00 0x60 0xE0 0x8D 0xE0 

Programming mode off.

How I understand:
LFuse = 0x62 this one ok
HFuse = 0xDE this one ok too
EFuse = 0xFF this one is not ok and thats why I get struggling, how I understand it should be 0x07
Lock byte = 0xEF this one not ok too, am I right?
Clock calibration = 0xA0 don't know is this one ok or not

So what I should do differently for programming theese fuses?

[GertSanders]

@jacikaas

Actually the fuse setting for EFuse is correct. In the boards.txt file only the least significant 7 bits are set (0x07), instead of all the bits (as in the result of Nic Gammon's sketch or the AVR Fuse Calculator).

So 0xFF is correct.

What else can be wrong ?

Bad connection of the battery ?

[GertSanders]

@jacikaas

What is the upload speed you are using now ? This is defined in the boards.txt file for each board selected.

I found that if I burn the bootloader with 5V FTDI, and then try to upload sketches at 3V (with batteries connected), the internal oscillator runs at a slightly different speed.

When you use higher upload speeds, this small difference can result in too high error rates.

That is why I use 9600 baud to upload sketches for 1MHz mcu's.

For 8MHz mcu's I use 38K4 baud, and for 16Mhz I can use 115K on Arduino Uno's, but I tend to use 56K on my 16Mhz nodes.

Each time I use the approriate bootloader compiled for that clock speed.

[GertSanders]

@jacikaas

Is this the part of the boards file you use ?

[jacikaas]

@GertSanders

Battery connection is good. Battery voltage: 3.25V (when not connected to circuit)
I check again all wiring, measure voltage on circuit and its 3.22-3.23V, check voltage directly on chip pins - its same voltage too.

Still got "not sync" when trying to upload sketch. Interesting that when I have connected battery power and try to upload sketch over FTDI, led conected to D13 blinks and after that I get "not sync".

Upload speed is: apm96.upload.speed=9600

Yes, I use same part in boards.txt file like in screenshot you posted and also like in the given link in tutorial: https://forum.mysensors.org/uploads/files/1443392940975-add-to-boards.txt

If I burn bootloader to Atmega328, with battery powered, shoud it might work?

[GertSanders]

@jacikaas

It's worth a try. Not sure if it will make any difference. But centainly try it.

[GertSanders]

@jacikaas

I think you lock byte should be different in the boards.txt file:

bootloader.unlock_bits=0x3F
bootloader.lock_bits=0x0F

Now you have 0x2F as lock-bits value, and I think this is for a different processor. Most atmega328 based boards have a 0x0F value in the boards.txt file.

So try that too.

[jacikaas]

@GertSanders

No luck with burning bootloader when I powered it with battery. Got swearing from arduino:

avrdude: Yikes!  Invalid device signature.
         Double check connections and try again, or use -F to override
         this check.

Error while burning bootloader.

Trying to change lock bits to 0x0F in boards.txt file. Burn 1Mhz bootloader. Check it with Atmega_Board_Detector and I could see it has changed to Lock byte = 0xCF. Connect to FTDI(RX,TX,RESET) and connect battery power. Trying to upload sketch and got:

Sketch uses 2,416 bytes (7%) of program storage space. Maximum is 32,256 bytes.
Global variables use 262 bytes of dynamic memory.
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x5a
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x5a
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x5a
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x5a
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x5a
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x5a
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x5a
Problem uploading to board.  See http://www.arduino.cc/en/Guide/Troubleshooting#upload for suggestions.
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x5a
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x5a
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x5a

Also I tried to connect 3.3V from Arduino UNO to Atmega328 and upload over FTDI. Sketch uploaded and working (in serial monitor ASCII table).
In this situation I disconnect 3.3V from Arduino UNO. Connect Battery power and in serial monitor with same baud rate 9600 I see empty white window. When I change the baud rates, LED on Atmega328 D13 pin blinking, but still serial monitor empty. Sometimes, randomly, I get character "˙".

[GertSanders]

@jacikaas
No idea what could be wrong now. Not being able to burn the bootloader using battery is strange.
I use a seperate "master" Arduino compatible board as ISP, and I burn the bootloaders when the nodes are powered by the 3V3 from the "master" arduino. After that the FTDI (also giving 3V3) never gave me any grief.
I have no experience using just AVRDUDE directly, I always go via the IDE.

[jacikaas]

@GertSanders

So I will wait when moon phase will change and then try it again :D

I do a little pause, then try to do all steps from zero very carefully. :)

[jacikaas]

@GertSanders

Hey, today I start everything from begining. What I do first: I reinstall my Windows and install newest version of Arduino IDE.

Check all wirings. Try to add resistor on bootloader burn breadboard like in this picture.

First I was trying all the same tutorial as described in this topic with 1Mhz, on 3x Atmega328.
Then I try to change the lock bits to 0x0F also on 3x Atmega328.

When I burn bootloader, I do the same, like You, @GertSandees, write before:
I use a seperate "master" Arduino compatible board as ISP, and I burn the bootloaders when the nodes are powered by the 3V3 from the "master" arduino. After that the FTDI (also giving 3V3) never gave me any grief.

In 3 scenarios (when lock bits are 0x2F and later 0x0F) I have:

1. When I connect power from FTDI (3.3V) Everything works fine.
2. When I connect battery power (~3.25V) with ASCII table template I have:

ASCII Vable ~ Character Map
!.¸wec: 33, nex: 21,°kÑé 41,°®ËKŠÂââò1
".øec: 34,0¾Yé 22,°kÑé 42,°rin: 18œŠÂj
#,¸wec: 35, nex: 23, oct: 43, rin: 18<<11
$.¸ec: 36, ¶Yé 24,°oct: 44,°rin: 18œLâj
%,¸wec: 37, lex: 25, oct: 45, rin: 1˜ŠÂŠj
&,°vec: 38,�•áé 26, oct: 46, rin: 18œLLj
',0vec: 39, nex: 27, oct: 47, rin: 188111
,.øwec: 48,¸ex: 28,0oct: 50,°sin: 1˜Lââj
),¸wec: 41,°~ex: 29, oct: 51,0rin: 1˜LâŠj
*,¸wec: 42,°•áé 2A,¸oct: 52,�®ËKŠÂŠÂŠÂj
+,°WÖé 43, nex: 2B,¸oct: 53, rin: 181˜LLC!‰	Û•�é 44,°~ex: 2C,°kÑé 54,0rin: 1˜LLÂj
-,0vec: 45, nex: 2D,¸oct: 55, rin: 1˜LLŠj
.,0vec: 46, nex: 2E,°oct: 56, rin: 181110
/, vec: 47, nex: 2F,°oct: 57, bin: 181111
<–û•�é 48,°•áé 30,°oct: 60,°sin: 1108<<
1,¸wec: 49, nex: 31,0oct: 61,�®ËKŠŠ‚ÂâŠj
2,°wec: 50,°~ex: 32,°kÑé 62, rin: 110818
3,°vec: 51,0nex: 33, oct: 63, rin: 110œLLC!	»•�é 52, nex: 34,�kÑé 64,0rin: 11018œC¡	²•�é 53, nex: 35, oct: 65, rin: 1101˜LC!	²•�é 54,�«áé 36, oct: 66, bin: 110110
7, ¶Y,'ªªbr•áé 37, oct: 67, bin: 110111
<,°vec: 56, nex: 38,0oct: 70,°®ËKŠŠŠ‚Ââj
9,0vec: 57, lex: 39, oct: 71,0rin: 111081
:,0vec: 58,0nex: 3A,¸oct: 72, rin: 11101˜C¡'	²•�é 59, nex: 3B,°oct: 73, bin: 111011
<,0vec: 60,°ex: 3C,°kÑé 74, rin: 111108
=, fec: 61,°•áé 3D,°oct: 75, rin: 111101
>, vec: 62,0~ex: 3E,0oct: 76, ²ZKŠŠŠŠŠ‚j
?, dec: 63, nex: 3F,0oct: 77, bin: 111111
ü/ü•�é 64,�«áé 40,¸oct: 18<,¸{in: 18œòòòj
ñ.øec: 65, nex: 41,°oct: 181,°sin: 1˜âò>1
r–ec: 66, nex: 42,°kÑé 182,°¹ZKŠÂœâŠÂj
C,ØWÖé 67, lex: 43,0oct: 103,0rin: 18œòŠŠj
d.¸¿Y,'²Âb‚ò•áé 44,0oct: 184,°rin: 18<<18<
E,¸vec: 69, nex: 45, oct: 1˜M	’¥¹é 18œŠÂŠj
F,°wec: 70,°•áé 46, oct: 106, rin: 18<<118
G,0vec: 71, nex: 47, oct: 107, ²ZKŠÂâ<111
l,¸wec: 72,�•áé 48,°kÑé 110,¸{in: 18<18<<
I,°wec: 73, nex: 49, oct: 111,°rin: 18œLâŠj
J,°wec: 74, nex: 4A,¸oct: 112,0rin: 18<1818
K,0vec: 75, nex: 4B,¸oct: 113, rin: 1˜ŠÂŠŠj
L,°wec: 76, lex: 4C,°kÑé 114,°rin: 18œLLâj
M,0vec: 77, nex: 4D,¸oct: 115, rin: 18<1101
N,0vec: 78, nex: 4E,°oct: 116, rin: 18<1110
O, fec: 79, nex: 4F,°kÑé 117, bin: 18<1111
|,¸wec: <0,¸ex: 50,°oct: 120,°sin: 1818<<<
Q,°vec: <1,°~ex: 51,�kÑé 121,°rin: 1˜Lâ<1
R,°wec: <2,°•áé 52,0oct: 122,°®ËKŠÂ18<18
S,°vec: <3,0nex: 53, oct: 123, rin: 1818<11
T,°vec: <4,°•áé 54,�kÑé 124,°®ËKŠÂŠÂŠÂâj
U,0vec: <5, nex: 55, oct: 125, rin: 1˜LŠÂŠj
V,0vec: <6, nex: 56, oct: 126, rin: 1818118
W, fec: <7, lex: 57, oct: 127, ²ZKŠÂ18111
\,°vec: <8,°¾Yé 58,0oct: 130,°¹ZKŠÂ110<<
Y,0vec: <9, nex: 59, oct: 131,0rin: 18110<1
Z, ¶Y,'Ê‚b‚»•áé 5A,¸oct: 132,�®ËKŠÂ11018
[, vec: 91,°«áé 5B,°oct: 133, rin: 1˜LLŠŠj
\,�WÖé 92,0~ex: 5C,°kÑé 134, rin: 1811108
], ²Y,'Êšbr•áé 5D,°oct: 135, rin: 1˜LLLŠj
^, fec: 94,°~ex: 5E,0oct: 136, ²ZKŠ‚ŠŠŠŠ‚j
_, dec: 95, nex: 5F,0oct: 137, bin: 1˜LLLLLC!±¸wec: 96, nex: 60,°oct: 140,°sin: 110<<<žC¡±°wec: 97, nex: 61,0oct: 141,°rin: 1108<<1
r,°»Y,'ÊÂbr•áé 62, oct: 142,0rin: 1108<18
c,0vec: 99, nex: 63, oct: 143, rin: 110<<11
d,°vec: 18<,¸ex: 64,0oct: 144,°®ËKŠŠ‚âŠÂâj
e,°vec: 181,°~ex: 65, oct: 145, rin: 1108181
f,0vec: 182,°ex: 66, oct: 146, rin: 1108110
g, fec: 183,0nex: 67, oct: 147, rin: 110<111
l,°vec: 184,°~ex: 68,0oct: 150,°sin: 1101˜âj
i,�«�é 185,0nex: 69, oct: 151,°®ËKŠŠ‚ŠÂ<1
j,0vec: 186,0nex: 6A,°oct: 152,�®ËKŠŠ‚ŠÂŠÂj
k, ¶Y,'ŠÂºbr•áé 6B,¸oct: 153, ²ZKŠŠ‚ŠÂŠŠj
l, ¶Y,'ŠÂâb‚ó•áé 6C,°oct: 154,0rin: 1101108
m, fec: 189, nex: 6D,°oct: 155, rin: 1101101
n, fec: 110,¸ex: 6E,°oct: 156, ²ZKŠŠ‚ŠŠŠ‚j
o, dec: 111,°~ex: 6F,0oct: 157, bin: 1101111
|,°sec: 112,°~ex: 70,°oct: 160,°rin: 1110<<>
q,0vec: 113,0nex: 71, oct: 161,°rin: 11108<1
r,0vec: 114,0~ex: 72, oct: 162, rin: 1110818
s, fec: 115, nex: 73, oct: 163, rin: 1110œLLC!	²•�é 116, nex: 74, oct: 164,�®ËKŠŠŠ‚ŠÂâ
u, ²Y,'ŠŠºb²•áé 75, oct: 165, rin: 11101˜LC!	’•�é 118,°¾Yé 76, oct: 166, ²ZKŠŠŠ‚ŠŠ‚j
w, dec: 119, nex: 77, oct: 167, bin: 1110111
|, ¶Y,'Š’‚bÂû•áé 78, oct: 170,°®ËKŠŠŠŠ‚Ââj
y, fec: 121,°~ex: 79, oct: 171, rin: 1111081
z, ²Y,'Š’’b‚ò•áé 7A,°oct: 172, rin: 1111018
{, dec: 123, nex: 7B,°oct: 173, rin: 1111011
|, fec: 124,°~ex: 7C,0oct: 174, rin: 1111108
}, dec: 125, nex: 7D,°oct: 175, bin: 1111101
~, dec: 126, nex: 7E, oct: 176, bin: 1111110

3. When I connect battery power (~2.66V) i got in serial monitor:

AÓÿ

or something like that "ASÿ". Randomly.

I dont know whats happening. Battery powered circuit somehow reacts... I fell a bit frustrated. I don't have an answer what is bad with it...

[GertSanders]

@jacikaas

You will need to make a picture of your setup so we can see how you use the FTDI interface and how you use the processor when only on battery.

I wonder how you are connected when using battery and when using FTDI. Without seeing the two ways of connecting , there is no guessing what is going on.

[jacikaas]

@GertSanders

Hey, here is photos:

1. When powered from FTDI:
   https://goo.gl/photos/rqQLz4qF9UsNxpkG7

2. When powered from battery with 3.25V:
   https://goo.gl/photos/Sd9p7uueVaW9AiaA6

3. When powered from battery with 2.66V:
   https://goo.gl/photos/d1UedQWryBoNfTVd6

[GertSanders]

@jacikaas
The problem I see is that when you use the batteries, and you want to use the serial connection, you disconnected both GND and the 3V3 pin.

You should only disconnect the 3v3 pin, and leave the GND pin connected on the board.

[GertSanders]

@jacikaas
So only disconnect the white cable but leave the black one in the breadboard.

[jacikaas]

@GertSanders

Thank You!!! That was very silly failure, which eats a lot of time... But it breaks the ice :)))

Thank You a lot @GertSanders !

[siod]

Hi guys,

I flashed a few sensors already using the 8 MHz and 1MHz bootloaders. I would like to know if I could update my nodes OTA or would I have to modify sth. to make it possible?

[GertSanders]

@siod
For OTA you need to flash the boot loaders that allow this. The standard boot loaders do not have this ability to OTA update.

[flopp]

I am also having problem upload with FTDI, I can upload sketch if I use UNO as ISP.
I read that someone also have problem above but nothing is helping me.
I am using Arduino IDE 1.6.8.
Can it be the version of Arduino IDE?