#How do I install the default Arduino bootloader, onto a Uno with MF firmware?
1 messages · Page 1 of 1 (latest)
mobiflight firmware does not replace the bootloader
it is just a regular arduino sketch
Hmmm the Arduino IDE says the programmer does not respond (the Uno)
ok, so
if you mean the "user arduino as upload tool" for another arduino
there is a specific arduino sketch for that
yep
but can't you just flash the nano directly from the IDE?
I guess you have reasons for that
Dodgy comms chip I think
if it has the CH340G with no markings
it is a fake CH340 and you need the driver fix
It sounds like your Arduino uses a counterfeit CH340 chip. You can find more information about this problem and how to fix it by visiting this blog post: Arduino Nano and Mega with CH340 chips connection issues
I've installed the driver fix. Will try the ISP sketch
ok
My bad for not uploading the ISP sketch (just done it)
The programmer ISP fails. Will check bad casserole
Win 10 here
yeah, I mean I havent really done this to a nano
I used the arduino flasher on an AtTiny85 chip (because it doesnt have any usb circuitry) when I made the first MobiFlight meetup badges
what kind of nano is it?
I wonder if the usb VID and PID match uniquely a mega
there is the board json files under Boards\ that determine the supported boards, mobiflight uses the usb PID and VID to determine what board it is
and if there are multiple choices it should give you a menu to choose from
but if it doesnt it likely is a distinctive match but seemingly wrong then
Nano 3 whats the best way to check VID and PID?
The Arduino IDE says
BN: Unknown board
VID: 0x0403
PID: 0x6001
SN: A5069RR4A
Hello, I recently bought Arduino Nano v3.0 from ebay. My problem is that i cannot install usb drivers for him either on Windows 7 64 bit or Windows XP 32 bit. FTDI drivers that i downloaded (from http://www.ftdichip.com) has vendor id (vid) set to 0x0403 and product id (pid) set to 0x6001 (0x6010, 0x6011, 0x6014 and 0x6010). With program USBVi...
For all developers I highly recommend Microsoft's USBView debugger. If you don't have it already, you need it!
It's an FTDI serial USB chip.
The Mega, Uno, Nano all have these two lines:
"^VID_0403&PID_6001"
"^VID_0403\+PID_6001\+.+",
So its impossible for MF to decide the board type , if an FDTI serial chip is used?
"HardwareIds": [
"^VID_2341&PID_0043",
"^VID_2A03&PID_0043",
"^VID_2341&PID_0243",
"^VID_2341&PID_0001",
"^VID_1A86&PID_7523",
"^VID_0403&PID_6001",
"^VID_067B&PID_2303",
"^VID_0403\+PID_6001\+.+"
],
The Ebay vendor said his Nano 3's had the old style boot loader. Perhaps that is why MF cannot upload the firmware?
Looking in MobiFlight\MobiFlight Connector\firmware there is no HEX file to reset the Nano.
Only Mega, Pro, Uno, RP_pico have reset hex files.
Perhaps if there has a Nano reset hex, uploading that might help.
I've given up on this Nano 3 and will return it to Ebay.
I've ordered another which clearly shows "CH340G " on the comms chip.
On a positive note, I have learned a lot and thank @manic venture for his help.
The old bootloader IIRC works at half the serial speed of the normal bootloader. I had a batch of Nanos with the old bootloader. I ended up updating the bootloader to the new version.
all worked after that
How did you update the bootloader? And does the old bootloader lead to sync problems with Mobiflight/avrdude?
I used another Uno board as programmer connected on the ICSP port to the Nano.
The issue with the old bootloader is that it loads sketches at half the speed of the normal (115kbps), which Mobiflight uses.
There are many resources explaining how to do this.
https://forum.arduino.cc/t/what-bootloader-is-there-in-a-nano/989343?_gl=1*1k02fec*_up*MQ.._gaNTIxNjAxMzk3LjE3Mzg3Njc1OTg._ga_NEXN8H46L5MTczODc2NzU5OC4xLjAuMTczODc2NzU5OC4wLjAuMTk0MTk2Nzc0Ng..
Hello , how can somebody find if a nano has old (atmegaboot) or new (optiboot) bootloader?