I'm getting a verification error when trying to flash the firmware from git via the bootloader:

avrdude -c stk500v2 -b 115200 -P /dev/ttyUSB0 -u -p m8 -D -U flash:w:bs_nfet.hex:i

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.04s

avrdude: Device signature = 0x1e9307
avrdude: reading input file "bs_nfet.hex"
avrdude: writing flash (8192 bytes):

Writing | ################################################## | 100% 1.97s

avrdude: 8192 bytes of flash written
avrdude: verifying flash memory against bs_nfet.hex:
avrdude: load data flash data from input file bs_nfet.hex:
avrdude: input file bs_nfet.hex contains 8192 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 3.38s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0840
         0xff != 0x82
avrdude: verification error; content mismatch

avrdude done.  Thank you.

Edit:
It appears the bootloader is not erasing (setting to 0xFF) the empty space as the pages are flashed, therefore leaving data from the old firmware in some circumstances like this where the new firmware is smaller than the old. Verify then fails because it expects 0xFF in the empty space.

Normally this is not an issue because of chip erase but with the bootloader we need something else. Does the Arduino bootloader automatically erase these gaps between data?

Edit:
I think the WinAVR srec tool "srec_cat" can fix the hex file by filling the gaps with 0xFF. I tried this:

srec_cat bs_nfet.hex -intel -fill 0xFF 0x0 0x2000 -o bs_nfet_fixed.hex -intel --line-length=44 --address-length=3

And it seems to produce the same output as the original bs_nfet.hex except with the gaps filled. Now to try it.

Originally Posted by jaccies

As you can see on hobbywing.com website the spec is stated now for all their ESC's e.g for Flyfun-18A ESC:
1 Specification
1.1 Output: Continuous 18A, Burst 22A up to 10 seconds.
1.2 Input Voltage: 2-4 cells lithium battery or 5-12 cells NiCd/NiMh battery.
1.3 BEC: 2A / 5V Linear mode BEC.
1.4 Refresh rate of the throttle signal: 50Hz to 432Hz.
1.5 Max Speed: 210000rpm for 2 Poles BLM, 70000rpm for 6 poles BLM, 35000rpm for 12 poles BLM.
(BLM = BrushLess Motor)
1.6 Size: 55mm*25mm*6mm.
1.7 Weight: 21g.

Dont the Hobbywing ESCs use the Silabs chip so can't be flashed with SK's firmware?

I successfully flashed Hobbyking F-20A ESC’s but after I increased the trottle it stared to smoke. I tried this with 2 different ESC, one with a motor connected which only pulsed and one without. I used the firmware from https://github.com/sim-/tgy. Have anyone else experienced this and know of a solution?

Using:
http://www.hobbyking.com/hobbyking/s...5202&aff=61689
http://www.hobbyking.com/hobbyking/s...6247&aff=61689
http://www.hobbyking.com/hobbyking/s...dProduct=24723

Thanks
Tom

Originally Posted by fusionfrog

I successfully flashed Hobbyking F-20A ESC’s but after I increased the trottle it stared to smoke. I tried this with 2 different ESC, one with a motor connected which only pulsed and one without. I used the firmware from https://github.com/sim-/tgy. Have anyone else experienced this and know of a solution?

There's no .hex files there.... I assume you built one? If you did, which .INC file did you use?

i got turntigy ae 30 it's in the list but are they upgradable?

Originally Posted by fusionfrog

I successfully flashed Hobbyking F-20A ESC’s but after I increased the trottle it stared to smoke. I tried this with 2 different ESC, one with a motor connected which only pulsed and one without. I used the firmware from https://github.com/sim-/tgy. Have anyone else experienced this and know of a solution?

Using:
http://www.hobbyking.com/hobbyking/s...5202&aff=61689
http://www.hobbyking.com/hobbyking/s...6247&aff=61689
http://www.hobbyking.com/hobbyking/s...dProduct=24723

Thanks
Tom

Which hex file did you use? You needed to use bs_nfet.hex for those HobbyKing F-20A. If you used another hex file you damaged the ESCs. Also what smoked? All of the ESCs?

Originally Posted by SecretM@n

i got turntigy ae 30 it's in the list but are they upgradable?

you just had to read one page back to get your answer.

Originally Posted by simonk

The AE are SiLabs now (see the spreadsheet). You can go for the Mystery / BlueSeries or try here.

SiLabs ESCs are not upgradable with SimonK firmware.

...

Thanx TheFernMan,
I used
avrdude -c usbasp -p m8 -U flash:w:tgy.hex
Is this the right syntax?
avrdude -c usbasp -p m8 -U flash:w:bs_nfet.hex

The bottom right chip (facing motors) on the opposite side of http://static.rcgroups.net/forums/at...yking_F20A.jpg
started to overheat.

Originally Posted by fusionfrog

Thanx TheFernMan,
I used
avrdude -c usbasp -p m8 -U flash:w:tgy.hex
Is this the right syntax?
avrdude -c usbasp -p m8 -U flash:w:bs_nfet.hex

The bottom right chip (facing motors) on the opposite side of http://static.rcgroups.net/forums/at...yking_F20A.jpg
started to overheat.

Yea tgy.hex is wrong hex file for that ESC. Why don't you use LazyZero flash tool. It's super easy and no need to play with fuses.

Originally Posted by TheFernMan

you just had to read one page back to get your answer.



SiLabs ESCs are not upgradable with SimonK firmware.

tank's sry i was reading many web page and i didint read all here

I have hopefully done my due diligence and examined every Front and Back Image for the Atmel based ESC's that Simon's firmware currently supports. Google Spreadsheet

When I initially bought these a long time ago, they were from eBay and advertised as

35A Brushless Motor ESC Speed Controller RC Trex 450 V2

they appear different from most commonly referenced ESC's as they are 2 PCB's on top of each other. I have tried Googling the details on the Atmel MCU (ATMEGA8L -8AI 0304) but that didn't yield any further information on the Brand or further details of this ESC.

The images I have of them are as follows:


Has any kind soul seen these before and could possibly guide me to the correct firmware to apply to these ESC's?

Thanks

Hi
I just flashed my HK Blueseries 30A ESC with SimonK bs_nfet.hex (2012-9-30) without realizing about the bootloader feature available using lazyzero flashtool. Is it possible for me to reflash the same bs_nfet.hex (2012-9-30) again on the same ESC with the bootloader this time round?

Can someone enlighten me? Thanks.

Originally Posted by Acit

Hi
I just flashed my HK Blueseries 30A ESC with SimonK bs_nfet.hex (2012-9-30) without realizing about the bootloader feature available using lazyzero flashtool. Is it possible for me to reflash the same bs_nfet.hex (2012-9-30) again on the same ESC with the bootloader this time round?

Yes, is not a problem.

Technically the only difference is the fuses it sets, the bootloader is most likely already on your ESC, just not enabled. But if you're not handy with avrdude then probably better to do the whole flash again.

Originally Posted by LittleMo

Yes, is not a problem.



Technically the only difference is the fuses it sets, the bootloader is most likely already on your ESC, just not enabled. But if you're not handy with avrdude then probably better to do the whole flash again.

Thanks LittleMo, now I get it clearly.