burining Arduino bootloader with FTDI

每次要燒錄bootloader時都要上網找一下才會想起當時是怎麼燒的....

試了很多方式, 用得最順手的是這個 Kimio Kosaka寫的
FTDI BITBANG mode...

基礎都是Avrdude, 這個程式要跟 avrdude.conf 還有這個 avrdude-GUI 都放在同一個資料夾下, 這樣比較不會找不到file

1.首先解開 serjtag-0.3
2. 把這個目錄下的\serjtag-0.3\ 的binary刪掉....
3. 把上面copy下來的 avrdude.conf copy 到 \serjtag-0.3\avrdude-serjtag\binary 把原來的蓋掉...
這個down load下來的有修改 ftdi 232的燒錄參數,也有支援 328P
4. 把那個avrdude-GUI野放到這裡 \serjtag-0.3\avrdude-serjtag\binary
5.直接執行 avrdude-GUI

硬體上是利用FTDI的IO來做燒錄的控制,對應如下...168P
miso PB4; # CTS X3(1)
sck PB5; # DSR X3(2)
mosi PB3; # DCD X3(3)
reset PC6; # RI X3(4)

CTS/DSR/DCD/RI是FTDI 232R的腳位...
最後那個1234就是Duemilanove上X3 connector上的腳位:

Arduino上面的ICSP pin define是這樣...

如果是要燒DIP得那就這樣接就行了...

打開avrdude gui,照這樣設...

Port那一格留白...

第一次燒錄的新chip說只能用 4800的baud rate. 但是燒過一次的就可以把 -B 4800拿掉...
avrdude的command大小寫有不一樣的定義....一定要照著打...

接下來先讀fuse bits...

Fuse的設定跟chip的momory/clock等都有關,168跟328就不一樣, 不同的設定也會不一樣....arduino:
chip/ Hfuse/ L fuse/ e fuse/ lock bits
168P/ DD/ FF/ 00/ 0F(Lock) 3F(unlock)
328P/ DA/ FF/ 05/ 0F(Lock) 3F(unlock)

有讀到就是通了, 有錯的話通常是接線或是avrdude的問題,例如config檔裏對手上的晶片的描述不正確或是沒有...

還有一個要注意的, 168跟168P,也不一樣....device signatrue 就不一樣,要選的bootloader也不一樣喔.. 用 -F就可以燒, 不過不能run....

接下來, 先earse chip, earse 完後再讀lock bits應該是3F(unlock)的狀況...


按照所選的chip寫好 H fuse/L fuse/ e fuse...


選好要燒的bootloader, 就按下去...

剛剛在讀fuse的時候, 可以試試fast mode, 如果可以, fast mode會快很多....

最後燒lock bit,不燒好像也可以用...


也可以用command的方法: http://www.geocities.jp/arduino_diecimila/bootloader/index_old_en.html
\serjtag-0.3\avrdude-serjtag\binary>avrdude -c diecimila -P ft0 -p m168 -t -B 4800
fast mode
avrdude -c diecimila -P ft0 -p m168 -t

Nice header for TQFP32:







留言

張貼留言

這個網誌中的熱門文章

Heltec ESP32+OLED+Lora, hardware testing

圖片
you can easily find some good boards from china, but most of them lack of accurate document... Hrere is an example; https://hackaday.io/project/26991-esp32-board-wifi-lora-32 the board looks good with lora and a 128x64 OLED, but the IIC and reset connection is important, since pin can be muxing easily, so every board could be different. pinMode(16,OUTPUT);  digitalWrite(16, LOW); // set GPIO16 low to reset OLED  delay(50);  digitalWrite(16, HIGH); // while OLED is running, must set GPIO16 to high  and, if needed, edit your Wire.begin() to Wire.begin(4,15); (4 = SDA 15 SCL)  i tested it with the Adafruit SSD1306 and the Acrobotics SSD1306 Librarys  both work.  Display size is 128x64 There are discussions on these boards on TＴＮ as a LORA node..or maybee single ch gateway? Heltec has a git :  https://github.com/Heltec-Aaron-Lee And there is another copy call TTGO https://de.aliexpress.com/item/TTGO-LORA32-868-915-Mhz-SX1276-ESP32-Oled-display-Bluetooth-WIFI
閱讀完整內容

micro SD card for ESP32, on lolin32 with OLED and heltec 32 lora oled

圖片
I have purchased 2 micro SD card holder for my esp project. First I would like to test with heltec esp32 lora oled module. this module uses: sck=05 MISO=19 MOSI=27 SS(lora)=18, then I assigned 21 for sd SS and there is a lib in esp32-arduino, which use SS default at 5 I took the example and use SD.begin(21), but I alway get the error: entry 0x40078a9c Card Mount Failed But I do saw once that it read out the sd card type and volume. Not sure it's the issue of lora sd card swithing, or it just can't work. The other esp32 card I have is an wemos esp32 oled, it did not leave me too much pins, I need to find out how to connect sd to it. But I have wemos D1 mini esp8266 on hand, and connect it as:  * The WeMos Micro SD Shield uses:  * D5, D6, D7, D8, 3V3 and G  *  * The shield uses SPI bus pins:  * D5 = CLK  * D6 = MISO  * D7 = MOSI  * D8 = CS It's not working with the example in the arduino IDE 1.8.5, which marked SD(esp8266), but it w
閱讀完整內容

AIS0. understanding AIS NMEA 0183: How it's coded

For my boat tracking system, I found out that using AIS format seems to be a good idea, at least I don't have to worry about how to present boat data, since there are already plenty things for do this on mobile phone or PC. Here is what I read: http://catb.org/gpsd/AIVDM.html Looking into AIS NMEA0183, it has much more application then I think. Such as MOB device, epir, aid to navigation device...etc, all are included. it use the first few char to indicate the function: Table 1. AIS talker IDs !AB NMEA 4.0 Base AIS station !AD MMEA 4.0 Dependent AIS Base Station !AI Mobile AIS station !AN NMEA 4.0 Aid to Navigation AIS station !AR NMEA 4.0 AIS Receiving Station !AS NMEA 4.0 Limited Base Station !AT NMEA 4.0 AIS Transmitting Station !AX NMEA 4.0 Repeater AIS station !BS Base AIS station (deprecated in NMEA 4.0) !SA NMEA 4.0 Physical Shore AIS Station It can also be used between device on boat for message communication, AIVDO The
閱讀完整內容