Trying to get DXCore 1.5ß running in portable 1.8.13 #378

pcfreak1201 · 2022-12-21T12:13:30Z

pcfreak1201
Dec 21, 2022

Is it Christmas already? No, but thanks anyway ;-) Great job, Spence!

Because of the necessary manual install, I give my Windows VM a try and set up a portable Arduino 1.8.13.
But even when I try to put the DxCore (megaavr-folder) in the portable/hardware/ folder nor in the arduino-1.8.13/hardware/arduino/ folder - the DX-Core showed up at the boards. The Arduino IDE fires up with no error...
I don't see any other instructions in installation.md?!
(By the way I already downloaded avr-gcc-7.3.0-atmel3.6.1-azduino6-i686-w64-mingw32.tar.bz2 and extract+copy the avr folder in tools)

Any ideas?

SpenceKonde · 2022-12-22T02:14:56Z

SpenceKonde
Dec 22, 2022
Maintainer

portable/sketchbook/hardware

1 reply

pcfreak1201 Dec 22, 2022
Author

Arrg - arduino-1.8.13\portable\sketchbook\hardware\DxCore-1.5.1... - now it works! Thanks!

ITDiscovery · 2022-12-26T15:51:31Z

ITDiscovery
Dec 26, 2022

I am creating a new environment on an RPi4. Here's my walkthrough so far:

From Arm64 Desktop new install (Linux raspberry 5.15.76-v8+ aarch64 GNU/Linux).
Download Arduino ARM64 from https://www.arduino.cc/en/software
Copy the DL's ArduinoIDE to the /opt directory and "sudo tar -xf Arduino-1.8.19-linuxaarch65.tar.xz"
"cd /opt/arduino-1.8.19" then "mkdir portable", "cd portable", "mkdir sketchbook", "cd sketchbook", "mkdir hardware".
"cd /opt/arduino-1.8.19" then "sudo ./install.sh"
Reboot

All the options show up, now I need to work on updating the toolchain... :-( I'll post that when I get it sorted out.

1 reply

ITDiscovery Dec 26, 2022

Changed "version 1.5.1" to "version 2.6.0" in /opt/arduino-1.8.19/portable/sketchbook/hardware/DxCore/megaavr/platform.txt

I did a wget of http://drazzy.com/package_drazzy.com_index.json and in the section "DxCore" version "1.4.10" package "7.3.0-atmel3.6.1-azduino4b" is spec'ced. Since this is aarch64-linux-gnu I wound up with:

"host": "aarch64-linux-gnu",
"archiveFileName": "avr-gcc-7.3.0-atmel3.6.1-azduino4a-aarch64-pc-linux-gnu.tar.bz2",
"url": "https://spencekondetoolchains.s3.amazonaws.com/avr-gcc-7.3.0-atmel3.6.1-azduino4a-aarch64-pc-linux-gnu.tar.bz2"

Sooo...
"cd /opt/arduino-1.8.19/hardware/tools"
"wget https://spencekondetoolchains.s3.amazonaws.com/avr-gcc-7.3.0-atmel3.6.1-azduino4a-aarch64-pc-linux-gnu.tar.bz2"
"tar -xvf avr-gcc-7.3.0-atmel3.6.1-azduino4a-aarch64-pc-linux-gnu.tar.bz2"

Tested by opening the Blink sketch and doing a verify with the AVR-DD board selected (no boot loader).

And because my boards use SerialUPDI...
"cd /opt/arduino-1.8.19/portable/sketchbook/hardware/DxCore/megaavr/tools"
"wget https://github.com/earlephilhower/esp-quick-toolchain/releases/download/2.5.0-4/python3-via-env.tar.gz"
"tar -xvf python3-via-env.tar.gz"

I am able to burn a bootloader for my AVR128DB28 part, but it's not working for my AVR64DD28 part using the same board layout. I was also able to upload Blink successfully, and it worked fine (once I remembered that LED_BUILTIN is PIN_PA7).

Here's the schematic: https://github.com/ITDiscovery/AVR128PS2Keyboard/raw/main/BCardAVR128DB28.pdf

This is a slightly newer version(I snail-mailed one to Spence many moons ago), so ignore J0-5. X2, C8, C9, R4, R5 are not populated. R3 is a jumper (and not really relevant).

I get:

pymcuprog.serialupdi.physical - INFO - Opening port '/dev/ttyUSB0' at '57600' baud
pymcuprog.serialupdi.link - INFO - STCS 08 to 0x03
pymcuprog.serialupdi.link - INFO - STCS 06 to 0x02
pymcuprog.serialupdi.link - INFO - LDCS from 0x00
pymcuprog.serialupdi.link - WARNING - UPDI init failed: Can't read CS register.

Many thanks for future help!! If I can get this sorted, I'd like to make some new AVR128DD28 boards to hand out at Dallas Hackers.

SpenceKonde · 2022-12-30T03:44:02Z

SpenceKonde
Dec 30, 2022
Maintainer

AVR128DD28 huh? Im assuming you mean AVR64DD28.
That error just looks like a wiring error - though you aren't using the right version of the toolchain, you need Azduino6 for 1.5.x

But 1.5.1 is now available in board manager

1 reply

ITDiscovery Dec 30, 2022

Yes, AVR128DD28 was a typo, I did indeed mean AVR64DD28. I x2 checked what I was setup for. I updated the document above. When I get a few minutes, I'll try applying the Azduino6 toolchain and then update the post above depending on results.

pcfreak1201 · 2022-12-30T08:20:28Z

pcfreak1201
Dec 30, 2022
Author

Arduino: 1.8.19 (Linux), Board: "AVR DD-series (no bootloader), AVR32DD14, 10 MHz internal, 1.9V, Disabled/Disabled, EEPROM retained, PF6: Reset & PF7: UPDI, Default (recommended), Default, 1.5k flash, no floats, On all pins, with new implementation., Enabled, 8ms, Master or Slave, Disabled (Always use this if not writing flash from app), Disabled (recommended), No delay before window "opens""

[...]
Using board 'avrdd' from platform in folder: /home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1
Using core 'dxcore' from platform in folder: /home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1
Detecting libraries used...
/home/stefan/.arduino15/packages/DxCore/tools/avr-gcc/7.3.0-atmel3.6.1-azduino6/bin/avr-g++ -c -g -Os -Wall -std=gnu++17 -fpermissive -Wno-sized-deallocation -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -Wno-error=narrowing -flto -mrelax -w -x c++ -E -CC -mmcu=avr32dd14 -DF_CPU=10000000L -DCLOCK_SOURCE=0 -DTWI_MORS_SINGLE -DMILLIS_USE_TIMERB1 -DCORE_ATTACH_ALL -DARDUINO=10819 -DARDUINO_avrdd -DARDUINO_ARCH_MEGAAVR "-DDXCORE=\"1.5.1\"" -DDXCORE_MAJOR=1UL -DDXCORE_MINOR=5UL -DDXCORE_PATCH=1UL -DDXCORE_RELEASED=1 -DMVIO_ENABLED -I/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/cores/dxcore/api/deprecated -I/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/cores/dxcore -I/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/variants/14pin-ddseries /tmp/arduino_build_870768/sketch/Blink.ino.cpp -o /dev/null
Generating function prototypes...
/home/stefan/.arduino15/packages/DxCore/tools/avr-gcc/7.3.0-atmel3.6.1-azduino6/bin/avr-g++ -c -g -Os -Wall -std=gnu++17 -fpermissive -Wno-sized-deallocation -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -Wno-error=narrowing -flto -mrelax -w -x c++ -E -CC -mmcu=avr32dd14 -DF_CPU=10000000L -DCLOCK_SOURCE=0 -DTWI_MORS_SINGLE -DMILLIS_USE_TIMERB1 -DCORE_ATTACH_ALL -DARDUINO=10819 -DARDUINO_avrdd -DARDUINO_ARCH_MEGAAVR "-DDXCORE=\"1.5.1\"" -DDXCORE_MAJOR=1UL -DDXCORE_MINOR=5UL -DDXCORE_PATCH=1UL -DDXCORE_RELEASED=1 -DMVIO_ENABLED -I/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/cores/dxcore/api/deprecated -I/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/cores/dxcore -I/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/variants/14pin-ddseries /tmp/arduino_build_870768/sketch/Blink.ino.cpp -o /tmp/arduino_build_870768/preproc/ctags_target_for_gcc_minus_e.cpp
/home/stefan/arduino-1.8.19/tools-builder/ctags/5.8-arduino11/ctags -u --language-force=c++ -f - --c++-kinds=svpf --fields=KSTtzns --line-directives /tmp/arduino_build_870768/preproc/ctags_target_for_gcc_minus_e.cpp
Sketch wird kompiliert...
/home/stefan/.arduino15/packages/DxCore/tools/avr-gcc/7.3.0-atmel3.6.1-azduino6/bin/avr-g++ -c -g -Os -Wall -Wextra -std=gnu++17 -fpermissive -Wno-sized-deallocation -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -Wno-error=narrowing -MMD -flto -mrelax -mmcu=avr32dd14 -DF_CPU=10000000L -DCLOCK_SOURCE=0 -DTWI_MORS_SINGLE -DMILLIS_USE_TIMERB1 -DCORE_ATTACH_ALL -DARDUINO=10819 -DARDUINO_avrdd -DARDUINO_ARCH_MEGAAVR "-DDXCORE=\"1.5.1\"" -DDXCORE_MAJOR=1UL -DDXCORE_MINOR=5UL -DDXCORE_PATCH=1UL -DDXCORE_RELEASED=1 -DMVIO_ENABLED -I/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/cores/dxcore/api/deprecated -I/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/cores/dxcore -I/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/variants/14pin-ddseries /tmp/arduino_build_870768/sketch/Blink.ino.cpp -o /tmp/arduino_build_870768/sketch/Blink.ino.cpp.o
Compiling libraries...
Compiling core...
Using precompiled core: /tmp/arduino_cache_967615/core/core_ee5cf0735d1f0f51d3834756ee0cf7e2.a
Linking everything together...
/home/stefan/.arduino15/packages/DxCore/tools/avr-gcc/7.3.0-atmel3.6.1-azduino6/bin/avr-gcc -Wall -Wextra -Os -g -flto -fuse-linker-plugin -mrelax -Wl,--gc-sections,--section-start=.text=0x0,--section-start=.FLMAP_SECTION1=0x8000,--section-start=.FLMAP_SECTION2=0x10000,--section-start=.FLMAP_SECTION3=0x18000 -mmcu=avr32dd14 -o /tmp/arduino_build_870768/Blink.ino.elf /tmp/arduino_build_870768/sketch/Blink.ino.cpp.o /tmp/arduino_build_870768/../arduino_cache_967615/core/core_ee5cf0735d1f0f51d3834756ee0cf7e2.a -L/tmp/arduino_build_870768 -lm
/home/stefan/.arduino15/packages/DxCore/tools/avr-gcc/7.3.0-atmel3.6.1-azduino6/bin/avr-objcopy -O binary -R .eeprom /tmp/arduino_build_870768/Blink.ino.elf /tmp/arduino_build_870768/Blink.ino.bin
/home/stefan/.arduino15/packages/DxCore/tools/avr-gcc/7.3.0-atmel3.6.1-azduino6/bin/avr-objcopy -O ihex -j .eeprom --set-section-flags=.eeprom=alloc,load --no-change-warnings --change-section-lma .eeprom=0 /tmp/arduino_build_870768/Blink.ino.elf /tmp/arduino_build_870768/Blink.ino.eep
/home/stefan/.arduino15/packages/DxCore/tools/avr-gcc/7.3.0-atmel3.6.1-azduino6/bin/avr-objcopy -O ihex -R .eeprom /tmp/arduino_build_870768/Blink.ino.elf /tmp/arduino_build_870768/Blink.ino.hex
bash -c "/home/stefan/.arduino15/packages/DxCore/tools/avr-gcc/7.3.0-atmel3.6.1-azduino6/bin/avr-objdump --disassemble --source --line-numbers --demangle --section=.text /tmp/arduino_build_870768/Blink.ino.elf > /tmp/arduino_build_870768/Blink.ino.lst"
bash -c "/home/stefan/.arduino15/packages/DxCore/tools/avr-gcc/7.3.0-atmel3.6.1-azduino6/bin/avr-nm --numeric-sort --line-numbers --demangle --print-size --format=s  /tmp/arduino_build_870768/Blink.ino.elf > /tmp/arduino_build_870768/Blink.ino.map"
/home/stefan/.arduino15/packages/DxCore/tools/avr-gcc/7.3.0-atmel3.6.1-azduino6/bin/avr-size -A /tmp/arduino_build_870768/Blink.ino.elf
Der Sketch verwendet 816 Bytes (2%) des Programmspeicherplatzes. Das Maximum sind 32768 Bytes.
Globale Variablen verwenden 4 Bytes (0%) des dynamischen Speichers, 4092 Bytes für lokale Variablen verbleiben. Das Maximum sind 4096 Bytes.
/home/stefan/.arduino15/packages/DxCore/tools/avrdude/6.3.0-arduino17or18/bin/avrdude -C/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/avrdude.conf -v -pavr32dd14 -cjtag2updi -P/dev/ttyUSB0 -Ufuse5:w:0b11001101:m -Ufuse6:w:0b00001100:m -Ufuse7:w:0x00:m -Ufuse8:w:0x00:m""-Uflash:w:/tmp/arduino_build_870768/Blink.ino.hex:i 

avrdude: Version 6.3-20201216
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2014 Joerg Wunsch

         System wide configuration file is "/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/avrdude.conf"
         User configuration file is "/home/stefan/.avrduderc"
         User configuration file does not exist or is not a regular file, skipping

         Using Port                    : /dev/ttyUSB0
         Using Programmer              : jtag2updi
JTAG ICE mkII sign-on message:
Communications protocol version: 1
M_MCU:
  boot-loader FW version:        1
  firmware version:              6.00
  hardware version:              1
S_MCU:
  boot-loader FW version:        1
  firmware version:              6.00
  hardware version:              1
Serial number:                   00:00:00:00:00:00
Device ID:                       JTAGICE mkII
         AVR Part                      : AVR32DD14
         Chip Erase delay              : 0 us
         PAGEL                         : P00
         BS2                           : P00
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 0
         StabDelay                     : 0
         CmdexeDelay                   : 0
         SyncLoops                     : 0
         ByteDelay                     : 0
         PollIndex                     : 0
         PollValue                     : 0x00
         Memory Detail                 :

                                  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
           prodsig        0     0     0    0 no        125  125      0     0     0 0x00 0x00
           fuses          0     0     0    0 no          9   16      0     0     0 0x00 0x00
           fuse0          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse1          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse2          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse4          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse5          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse6          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse7          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse8          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           lock           0     0     0    0 no          4    1      0     0     0 0x00 0x00
           data           0     0     0    0 no          0    0      0     0     0 0x00 0x00
           flash          0     0     0    0 no      32768  512      0     0     0 0x00 0x00
           eeprom         0     0     0    0 no        256   32      0     0     0 0x00 0x00

         Programmer Type : JTAGMKII_PDI
         Description     : JTAGv2 to UPDI bridge
         M_MCU hardware version: 1
         M_MCU firmware version: 6.00
         S_MCU hardware version: 1
         S_MCU firmware version: 6.00
         Serial number:          00:00:00:00:00:00
         Vtarget         : 5.0 V

avrdude: jtagmkII_initialize(): Cannot locate "flash" and "boot" memories in description
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.03s

avrdude: Device signature = 0x1e953b (probably avr32dd14)
avrdude: reading input file "0b11001101"
avrdude: writing fuse5 (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of fuse5 written
avrdude: verifying fuse5 memory against 0b11001101:
avrdude: load data fuse5 data from input file 0b11001101:
avrdude: input file 0b11001101 contains 1 bytes
avrdude: reading on-chip fuse5 data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of fuse5 verified
avrdude: reading input file "0b00001100"
avrdude: writing fuse6 (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of fuse6 written
avrdude: verifying fuse6 memory against 0b00001100:
avrdude: load data fuse6 data from input file 0b00001100:
avrdude: input file 0b00001100 contains 1 bytes
avrdude: reading on-chip fuse6 data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of fuse6 verified
avrdude: reading input file "0x00"
avrdude: writing fuse7 (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of fuse7 written
avrdude: verifying fuse7 memory against 0x00:
avrdude: load data fuse7 data from input file 0x00:
avrdude: input file 0x00 contains 1 bytes
avrdude: reading on-chip fuse7 data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of fuse7 verified
avrdude: reading input file "0x00:m""-Uflash:w:/tmp/arduino_build_870768/Blink.ino.hex"
avrdude: can't open input file 0x00:m""-Uflash:w:/tmp/arduino_build_870768/Blink.ino.hex: No such file or directory
avrdude: read from file '0x00:m""-Uflash:w:/tmp/arduino_build_870768/Blink.ino.hex' failed

avrdude: jtagmkII_program_disable(): bad response to leave progmode command: RSP_NO_TARGET_POWER

avrdude done. Thank you.

Beim Hochladen des Sketches ist ein Fehler aufgetreten (Error during upload)

Strange: this DUT was already flashed with blink on avrdude-7.0 and still blinks -- but now it doesn't respond any more to nothing. Always only RSP_NO_TARGET_POWER (with jtag2updi). But now I can use my "normal" system for rurther checking ...

0 replies

pcfreak1201 · 2022-12-30T08:48:13Z

pcfreak1201
Dec 30, 2022
Author

And no luck with SerialUPDI:

SerialUPDI
UPDI programming for Arduino using a serial adapter
Based on pymcuprog, with significant modifications
By Quentin Bolsee and Spence Konde
Version 1.2.3 - Jan 2022
Using serial port /dev/ttyUSB0 at 230400 baud.
Target: avr32dd14
Set fuses: ['6:0b00001100', '7:0x00', '8:0x00']
Action: write
File: /tmp/arduino_build_870768/Blink.ino.hex
pymcuprog.programmer - INFO - Setting up programming session for 'avr32dd14'
pymcuprog.deviceinfo.deviceinfo - INFO - Looking for device avr32dd14
pymcuprog.serialupdi.physical - INFO - Opening port '/dev/ttyUSB0' at '115200' baud
pymcuprog.serialupdi.link - INFO - STCS 08 to 0x03
pymcuprog.serialupdi.link - INFO - STCS 06 to 0x02
pymcuprog.serialupdi.link - INFO - LDCS from 0x00
pymcuprog.serialupdi.link - WARNING - UPDI init failed: Can't read CS register.
pymcuprog.serialupdi.physical - INFO - Sending double break
pymcuprog.serialupdi.physical - INFO - Double-break sent. Retrying.
pymcuprog.serialupdi.physical - INFO - Opening port '/dev/ttyUSB0' at '115200' baud
pymcuprog.serialupdi.link - INFO - STCS 08 to 0x03
pymcuprog.serialupdi.link - INFO - STCS 06 to 0x02
pymcuprog.serialupdi.link - INFO - LDCS from 0x00
pymcuprog.serialupdi.link - WARNING - UPDI init failed: Can't read CS register.
Traceback (most recent call last):
  File "/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/tools/prog.py", line 286, in <module>
    main()
  File "/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/tools/prog.py", line 128, in main
    return_code = pymcuprog_basic(args, fuses_dict)
  File "/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/tools/prog.py", line 199, in pymcuprog_basic
    status = pymcu._start_session(backend,
  File "/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/tools/libs/pymcuprog/pymcuprog_main.py", line 545, in _start_session
    backend.start_session(sessionconfig)
  File "/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/tools/libs/pymcuprog/backend.py", line 359, in start_session
    self.programmer.setup_device(
  File "/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/tools/libs/pymcuprog/programmer.py", line 78, in setup_device
pymcuprog.serialupdi.physical - INFO - Closing port '/dev/ttyUSB0'
Beim Hochladen des Sketches ist ein Fehler aufgetreten
    self.device_model = get_nvm_access_provider(self.transport,
  File "/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/tools/libs/pymcuprog/nvm.py", line 42, in get_nvm_access_provider
    accessprovider = NvmAccessProviderSerial(transport, device_info, baud=frequency, options=options)
  File "/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/tools/libs/pymcuprog/nvmserialupdi.py", line 54, in __init__
    self.avr = UpdiApplication(port, baud, self.dut)
  File "/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/tools/libs/pymcuprog/serialupdi/application.py", line 79, in __init__
    datalink.init_datalink()
  File "/home/stefan/.arduino15/packages/DxCore/hardware/megaavr/1.5.1/tools/libs/pymcuprog/serialupdi/link.py", line 44, in init_datalink
    raise PymcuprogError("UPDI initialisation failed")
pymcuprog.pymcuprog_errors.PymcuprogError: UPDI initialisation failed

5 replies

pcfreak1201 Dec 30, 2022
Author

Yep, it's kinda "bricked". Microchip Studio with ATMELICE3 can't read the chip either. Because it still blinks with 0.5Hz, it has nothing to do with the oscillator settings, so next I'll try to build a HV-UPDI programmer and test "de-brick" with HV-pulse...

ITDiscovery Dec 30, 2022

So I updated my main dev platform (MacBook) with 1.5.1 (many thanks for the hard work Spence!!). I Burned Bootloader for my AVR128DB28 and it did the 3 quick blinks on PA7 every second. I uploaded Blink, and it works fine.

I get the same error as pcfreak1201 when I Burn Bootloader on the AVR64DD28. I'm x2 checking the part values, but the AVR128DB28 and AVR64DD28 are using the same PCB layout (I guess JCLPCB could have made a bad board, or I have in incorrect part).

Here are my settings:
AVRDD Series (Optiboot) - doesn't seem to matter
AVR64DD28
Clock Speed 24MHz Internal
Millis() - TCB2 on 28/32 (recommended)
BOD Level 1.9v
BOD Active/Sleeping Disabled
WDT Timeout Disabled
WDT Window -No delay
Reset and UDPI Functions: PF6 Reset, PF7 UPDI - 1 sec timeout
Startup Time: 8ms
Bootloader Serial Port: USART0, PA0-TX, PA-1-RX
Bootloader Entry Condition: Default
MVIO: Enabled
attachInterupt(): all pins
printf(): default
1x Wire, Master or Slave

pymcuprog.programmer - INFO - Setting up programming session for 'avr64dd28' pymcuprog.deviceinfo.deviceinfo - INFO - Looking for device avr64dd28 pymcuprog.serialupdi.physical - INFO - Opening port '/dev/cu.usbserial-AB0LX43L' at '57600' baud pymcuprog.serialupdi.link - INFO - STCS 08 to 0x03 pymcuprog.serialupdi.link - INFO - STCS 06 to 0x02 pymcuprog.serialupdi.link - INFO - LDCS from 0x00 pymcuprog.serialupdi.link - WARNING - UPDI init failed: Can't read CS register. pymcuprog.serialupdi.physical - INFO - Sending double break pymcuprog.serialupdi.physical - INFO - Double-break sent. Retrying. pymcuprog.serialupdi.physical - INFO - Opening port '/dev/cu.usbserial-AB0LX43L' at '57600' baud pymcuprog.serialupdi.link - INFO - STCS 08 to 0x03 pymcuprog.serialupdi.link - INFO - STCS 06 to 0x02 pymcuprog.serialupdi.link - INFO - LDCS from 0x00 pymcuprog.serialupdi.link - WARNING - UPDI init failed: Can't read CS register.

So I'm x2 checking the part values and continuity on the board.

Update: I did a terrible job soldering up the DD board. PD7 and PF0 were not connected. Both D1 and D2 were backwards. I thought for sure "ah D1 is on UPDI...that has to be it!!" ... nope, same result. I'm looking at R6 & C7. R6 on the DD is 330, and on the DB is 1K. C7 is at 103 on the DB and 104 on the DD.

More update: I ensured that C7 and R6 have the same values (1K and .01uF), still no luck.

pcfreak1201 Dec 30, 2022
Author

Well, Burn Bootloader doesn't use the serial port, so is only VCC, UPDI and GND necessary. So do the SerialUPDI work on other devices?
I don't use Optiboot and only set the frequency to 10MHz. And first try with the exported Hex-file (was generated in a VM with 1.5.1) on linux worked: ZakKemble/AVRDUDESS#72 (comment)

SpenceKonde Dec 31, 2022
Maintainer

Yeah, serial UPDI is working for me. One thing though - that diode, D1, it says it's a 1N4148, which is a standard silicon diode. You should really have a "small signal" schottky diode, not a small signal, non-schottky diode. (also not some big chunky schottky rectifier with god knows how much parasitic effects). Does your serial adapter have a resistor in series with TX? If so what value? That

I think R6 is wrong (it shouldn't be there at all, what is it there for?!) but it shouldn't be able to cause the observed problem unless C7 has a short underneath it (I don't know if those are smd caps, and if so how large and what footprint you use for them - smaller caps, particularly with the pads needlessly close together, when soldered by hand, can sometimes form a solder bridge under the cap). Or if PF7/UPDI and PF6/reset are shorted, that would also cause problems programming

ITDiscovery Dec 31, 2022

R6 is there because there is no resistor on the FTDI board. No short on C7 which I changed from .1uF to .01uF. Can you think of any reason why an DD would not work in the same circuit as a DB. I gotta emphasize, that the DB works fine. The circuit is identical. Just to make sure:

UPDI - Pin 19 goes straight to RX. A 4.7K resistor goes from Pin 19 to TX. The anode of the 1N4148 goes to UPDI and cathode goes to TX. I'm seeing a good signal all the way to Pin 19 on the scope.
Reset - Pin 18 (is this even relevant?, I never get the bootloader to work, and the line is high and stays that way during the attempt to burn the bootloader) gets a C7 (by spec a 100nF Cap) to ground. R6 goes from Pin 18 to the switch to ground, it was 330 per spec. Sorry for the confusion on the schematic, which shows it wrong. I'll fix that tomorrow, which also show DTR implementation incorrectly....that's a schematic from an earlier (yeah and broken) version.

SpenceKonde · 2022-12-31T03:15:00Z

SpenceKonde
Dec 31, 2022
Maintainer

Still, a 1n4148 is going to be flaky. I had problems using those for that purpose. They didn't do their job very well, which was to help make **sure** the serial adapter can get the pin below V<sub>ILmax</sub> quickly without interfering with the manipulations coming from the target end. It may well be that the threshold voltages on pf6 and pf7 (the latter being unspecified for the da/db, and the former specified in different terms) are different on the two part families.

…

____________ Spence Konde Azzy’S Electronics New products! Check them out at tindie.com/stores/DrAzzy GitHub: github.com/SpenceKonde ATTinyCore: Arduino support for almost every ATTiny microcontroller Contact: ***@***.***

On Fri, Dec 30, 2022, 21:34 Peter Nichols ***@***.***> wrote: R6 is there because there is no resistor on the FTDI board. No short on C7 which I changed from .1uF to .01uF. Can you think of any reason why an DD would not work in the same circuit as a DB. I gotta emphasize, that the DB works fine. The circuit is identical. Just to make sure: UPDI - Pin 19 goes straight to RX. A 4.7K resistor goes from Pin 19 to TX. The anode of the 1N4148 goes to UPDI and cathode goes to TX. I'm seeing a good signal all the way to Pin 19 on the scope. Reset - Pin 18 (is this even relevant?, I never get the bootloader to work, and the line is high and stays that way during the attempt to burn the bootloader) gets a C7 (by spec a 100nF Cap) to ground. R6 goes from Pin 18 to the switch to ground, it was 330 per spec. Sorry for the confusion on the schematic, which shows it wrong. I'll fix that tomorrow, which also show DTR implementation incorrectly....that's a schematic from an earlier (yeah and broken) version. — Reply to this email directly, view it on GitHub <#378 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTXEW5IOMJFO66PC3YSX53WP6LURANCNFSM6AAAAAATFRZ6MY> . You are receiving this because you commented.Message ID: ***@***.***>

3 replies

ITDiscovery Dec 31, 2022

So I've got Bat43s on order. But we can consider this closed, the part was either defective or I cooked it mounting it to the board. I tested another board with the same design, and it works fine. Tested as follows:

Burn Bootloader via Serial UPDI at 57.6K. PA7 Blinks twice once a second. I then upload Blink sketch on the serial port, works perfectly. I put the "defective" board aside. Maybe it's bricked...

This afternoon I'll play with cleaning up the schematic, update and verify that, and post that and a board layout.

ITDiscovery Jan 1, 2023

Cleanup on schematic previously linked is done, including the change to a SSS Diode. I'll be waiting with interest on the WDT, perhaps my first board is "bricked".

I'd be happy to create the RPi dev environment as a walkthrough in MD to extend the "manual installation" docs.
I'll wait for Spence's thumbs up on posting board layouts, as I don't want to be perceived as "competition" for his great Tindie breakout boards.

Thanks again Spence for your hard work on this environment.

pcfreak1201, did you get your issue resolved?

pcfreak1201 Jan 7, 2023
Author

Well, I've already the order out for some PCBs following @Dlloydev 's HV-jtag2updi (ATTINY16x04)-programmer example, but with jumper for combining HV and UPDI on the same pin or - necessary for the DD's - for applying to the Reset pin, and no charge-pump but a cheap small boost-converter from China for the 9/12V. Because I don't like breadboards, I have not quite a lot parts not in SMD. May be I'll try something...

pcfreak1201 · 2023-01-13T16:08:38Z

pcfreak1201
Jan 13, 2023
Author

Here we are! I unbricked my AVR32DD14 breakout-board and can confirm the patch (1.5.2->1.5.3) worked, but ...
First things first: WARNING! This is not the propper way nor save to do for beginners!
To unbrick my DD14 I applied a constant voltage of 9V -> 2k2 Resistor -> ~RESET manual before I hit "Burn Bootloader" (only with patch or V1.5.3!) and I saw some kind of reset (blinking stops after applying the 9v "pulse"). Burn bootloader works (over jtag2updi, actual version of @ElTangas)
.. but after uploading the new sketch, my ProMini with CH340 (=Nano-Clone) stops working - at the verify, I think:

avrdude: 790 bytes of flash written
avrdude: verifying flash memory against /tmp/arduino_build_67594/Blink.ino.hex:
avrdude: load data flash data from input file /tmp/arduino_build_67594/Blink.ino.hex:
avrdude: input file /tmp/arduino_build_67594/Blink.ino.hex contains 790 bytes
avrdude: reading on-chip flash data:

Reading | avrdude: jtagmkII_paged_load(): timeout/error communicating with programmer (status -1)
avrdude: jtagmkII_paged_load(): bad response to read memory command: RSP_NO_TARGET_POWER
#########################avrdude: jtagmkII_recv(): msglen 167772161 exceeds max message size 100000, ignoring message
avrdude: jtagmkII_recv(): msglen 167772161 exceeds max message size 100000, ignoring message
avrdude: jtagmkII_recv(): msglen 167772161 exceeds max message size 100000, ignoring message
avrdude: jtagmkII_recv(): msglen 167772161 exceeds max message size 100000, ignoring message
avrdude: jtagmkII_read_byte(): timeout/error communicating with programmer (status -1)
avrdude: jtagmkII_read_byte(): timeout/error communicating with programmer (status -1)
avrdude: jtagmkII_read_byte(): timeout/error communicating with programmer (status -1)
avrdude: jtagmkII_read_byte(): timeout/error communicating with programmer (status -1)
avrdude: jtagmkII_read_byte(): fatal timeout/error communicating with programmer (status -1)
avr_read(): error reading address 0x0000
    read operation not supported for memory "flash"
avrdude: failed to read all of flash memory, rc=-2
avrdude: jtagmkII_program_disable(): timeout/error communicating with programmer (status -1)
avrdude: jtagmkII_close(): timeout/error communicating with programmer (status -1)
avrdude: jtagmkII_close(): timeout/error communicating with programmer (status -1)

avrdude done.  Thank you.

And after power-cycling all works fine again. So I've verfied with avrdude 7.1(+AVRDUDESS) the same hex:

avrdude: Version 7.1
         Copyright the AVRDUDE authors;
         see https://github.com/avrdudes/avrdude/blob/main/AUTHORS

         System wide configuration file is /home/stefan/avrdude-7.1/build_linux/src/avrdude.conf
         User configuration file is /home/stefan/.avrduderc
         User configuration file does not exist or is not a regular file, skipping

         Using Port                    : /dev/ttyUSB1
         Using Programmer              : jtag2updi
avrdude: jtagmkII_open_pdi()
avrdude: jtagmkII_getsync() attempt 1 of 10: sending sign-on command: 0x86 (29 bytes msg)
JTAG ICE mkII sign-on message:
Communications protocol version: 1
M_MCU:
  boot-loader FW version:        1
  firmware version:              6.00
  hardware version:              1
S_MCU:
  boot-loader FW version:        1
  firmware version:              6.00
  hardware version:              1
Serial number:                   00:00:00:00:00:00
Device ID:                       JTAGICE mkII
avrdude: jtagmkII_getsync(): using a 298-byte device descriptor
avrdude: jtagmkII_setparm()
avrdude: jtagmkII_setparm(): Sending set parameter command (parm 0x03, 1 bytes): 0x80 (1 bytes msg)
avrdude: jtagmkII_getsync(): sending get sync command: 0x80 (1 bytes msg)
avrdude: input file /tmp/arduino_build_408825/Blink.ino.hex auto detected as Intel Hex
         AVR Part                      : AVR32DD14
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         Serial program mode           : yes
         Parallel program mode         : yes
         Memory Detail                 :

                                           Block Poll               Page                       Polled
           Memory Type Alias    Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- -------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           fuse0       wdtcfg      0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse1       bodcfg      0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse2       osccfg      0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse4       tcd0cfg     0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse5       syscfg0     0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse6       syscfg1     0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse7       codesize    0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse8       bootsize    0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuses                   0     0     0    0 no          9   16      0     0     0 0x00 0x00
           lock                    0     0     0    0 no          4    1      0     0     0 0x00 0x00
           tempsense               0     0     0    0 no          2    1      0     0     0 0x00 0x00
           signature               0     0     0    0 no          3    1      0     0     0 0x00 0x00
           prodsig                 0     0     0    0 no        125  125      0     0     0 0x00 0x00
           sernum                  0     0     0    0 no         16    1      0     0     0 0x00 0x00
           userrow     usersig     0     0     0    0 no         32   32      0     0     0 0x00 0x00
           data                    0     0     0    0 no          0    1      0     0     0 0x00 0x00
           eeprom                  0     0     0    0 no        256    1      0     0     0 0x00 0x00
           flash                   0     0     0    0 no      32768  512      0     0     0 0x00 0x00

         Programmer Type : JTAGMKII_UPDI
         Description     : JTAGv2 to UPDI bridge
avrdude: jtagmkII_getparm()
avrdude: jtagmkII_getparm(): Sending get parameter command (parm 0x01): 0x81 (3 bytes msg)
avrdude: jtagmkII_getparm()
avrdude: jtagmkII_getparm(): Sending get parameter command (parm 0x02): 0x81 (5 bytes msg)
         M_MCU HW version: 1
         M_MCU FW version: 6.00
         S_MCU HW version: 1
         S_MCU FW version: 6.00
         Serial number   : 00:00:00:00:00:00
avrdude: jtagmkII_getparm()
avrdude: jtagmkII_getparm(): Sending get parameter command (parm 0x06): 0x81 (3 bytes msg)
         Vtarget         : 5.0 V

avrdude: jtagmkII_initialize(): trying to set baudrate to 115200
avrdude: jtagmkII_setparm()
avrdude: jtagmkII_setparm(): Sending set parameter command (parm 0x05, 1 bytes): 0x80 (1 bytes msg)
avrdude: jtagmkII_set_devdescr(): Sending set device descriptor command: 0x80 (1 bytes msg)
avrdude: jtagmkII_reset(): sending reset command: 0x80 (1 bytes msg)
avrdude: AVR device initialized and ready to accept instructions

Reading | avrdude: jtagmkII_read_byte(.., signature, 0x0, ...)
avrdude: jtagmkII_program_enable(): Sending enter progmode command: 0x80 (1 bytes msg)
avrdude: jtagmkII_program_enable(): Sending enter progmode command: 0x80 (1 bytes msg)
avrdude: jtagmkII_read_byte(): sending read memory command: 0x82 (2 bytes msg)
avrdude: jtagmkII_read_byte(.., signature, 0x1, ...)
avrdude: jtagmkII_read_byte(): sending read memory command: 0x82 (2 bytes msg)
################avrdude: jtagmkII_read_byte(.., signature, 0x2, ...)
avrdude: jtagmkII_read_byte(): sending read memory command: 0x82 (2 bytes msg)
################################## | 100% 0.03s

avrdude: device signature = 0x1e953b (probably avr32dd14)
avrdude: verifying flash memory against /tmp/arduino_build_408825/Blink.ino.hex
avrdude: load flash data from input file /tmp/arduino_build_408825/Blink.ino.hex
avrdude: input file /tmp/arduino_build_408825/Blink.ino.hex contains 790 bytes
avrdude: reading on-chip flash data ...

Reading | avrdude: jtagmkII_paged_load(.., flash, 512, 512)
avrdude: jtagmkII_paged_load(): sending read memory command: 0x82 (257 bytes msg)
avrdude: jtagmkII_paged_load(): sending read memory command: 0x82 (257 bytes msg)
#########################avrdude: jtagmkII_paged_load(.., flash, 512, 512)
avrdude: jtagmkII_paged_load(): sending read memory command: 0x82 (257 bytes msg)
avrdude: jtagmkII_paged_load(): sending read memory command: 0x82 (257 bytes msg)
######################### | 100% 0.16s

avrdude: verifying ...
avrdude: 790 bytes of flash verified
avrdude: jtagmkII_program_disable(): Sending leave progmode command: 0x80 (1 bytes msg)
avrdude: jtagmkII_reset(): sending reset command: 0x80 (1 bytes msg)
avrdude: jtagmkII_close()
avrdude: jtagmkII_close(): sending GO command: 0x80 (1 bytes msg)
avrdude: jtagmkII_close(): sending sign-off command: 0x80 (1 bytes msg)

avrdude done.  Thank you.

So that's kind a strange - but the programming works already. Now I go forward with the SerialUPDI hoping that's not a bug in the upload-routine.

1 reply

pcfreak1201 Jan 15, 2023
Author

Only to finalize here: With SerialUPDI BurnBootloader and Program/Verify works fine.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Trying to get DXCore 1.5ß running in portable 1.8.13 #378

{{title}}

Replies: 7 comments 12 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Trying to get DXCore 1.5ß running in portable 1.8.13 #378

Replies: 7 comments · 12 replies

SpenceKonde Dec 22, 2022 Maintainer

pcfreak1201 Dec 22, 2022 Author

SpenceKonde Dec 30, 2022 Maintainer

pcfreak1201 Dec 30, 2022 Author

pcfreak1201 Dec 30, 2022 Author

pcfreak1201 Dec 30, 2022 Author

pcfreak1201 Dec 30, 2022 Author

SpenceKonde Dec 31, 2022 Maintainer

SpenceKonde Dec 31, 2022 Maintainer

pcfreak1201 Jan 7, 2023 Author

pcfreak1201 Jan 13, 2023 Author

pcfreak1201 Jan 15, 2023 Author

Replies: 7 comments 12 replies

SpenceKonde
Dec 22, 2022
Maintainer

pcfreak1201 Dec 22, 2022
Author

SpenceKonde
Dec 30, 2022
Maintainer

pcfreak1201
Dec 30, 2022
Author

pcfreak1201
Dec 30, 2022
Author

pcfreak1201 Dec 30, 2022
Author

pcfreak1201 Dec 30, 2022
Author

SpenceKonde Dec 31, 2022
Maintainer

SpenceKonde
Dec 31, 2022
Maintainer

pcfreak1201 Jan 7, 2023
Author

pcfreak1201
Jan 13, 2023
Author

pcfreak1201 Jan 15, 2023
Author