AVRDUDE linuxgpio/linuxspi and PDI #1561

jaybstone · 2023-11-09T01:27:31Z

jaybstone
Nov 9, 2023

Hello,

I'm having trouble using AVRDUDE 7.2 to program the ATXMEGA128A4U from a Raspberry Pi 4 board. Normally, I program the 128A4U through the PDI port from Microchip Studio without problems. Also, I normally run an app on the Pi which talks to the 128A4U through the SPI 0 without problems. So, the Pi has both the PDI connections and SPI connections to the 128A4U board. The PDI reset is pulled up on the 128A4U board. I do not have USB on the 128A4U board.

When I try using linuxspi or linuxgpio, I receive errors (see below). I adjusted the .conf file to use GPIO1 for the RESET line, and GPIO1, 9, 10, and 11 for the bit bang lines. I have tried using slower baud rates for the SPI. I have tried using AVRDUDE 6.3.

LINUXSPI ERROR:

pi@my-pi:~ $ sudo avrdude -p x128a4u -C ~/avrdude_mine.conf -c linuxspi -P /dev/spidev0.0:/dev/gpiochip0 -v -F

avrdude: Version 7.2-20231103 (08b82ea6)
         Copyright the AVRDUDE authors;
         see https://github.com/avrdudes/avrdude/blob/main/AUTHORS

         System wide configuration file is /home/pi/avrdude_MIB.conf
         User configuration file is /root/.avrduderc
         User configuration file does not exist or is not a regular file, skipping

         Using Port                    : /dev/spidev0.0:/dev/gpiochip0
         Using Programmer              : linuxspi
avrdude: defaulting bit clock to 200 kHz
         AVR Part                      : ATxmega128A4U
         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
           ----------- -------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           fuse1                   0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse2                   0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse4                   0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse5                   0     0     0    0 no          1    1      0     0     0 0x00 0x00
           lock                    0     0     0    0 no          1    1      0     0     0 0x00 0x00
           prodsig     sigrow      0     0     0    0 no         64   64      0     0     0 0x00 0x00
           signature               0     0     0    0 no          3    1      0     0     0 0x00 0x00
           data                    0     0     0    0 no          0    1      0     0     0 0x00 0x00
           io                      0     0     0    0 no       4096    1      0     0     0 0x00 0x00
           fuse0                   0     0     0    0 no          1    1      0     0     0 0x00 0x00
           eeprom                  0     0     0    0 no       2048   32      0     0     0 0x00 0x00
           flash                   0     0     0    0 no     139264  256      0     0     0 0x00 0x00
           application             0     0     0    0 no     131072  256      0     0     0 0x00 0x00
           apptable                0     0     0    0 no       4096  256      0     0     0 0x00 0x00
           boot                    0     0     0    0 no       8192  256      0     0     0 0x00 0x00
           usersig                 0     0     0    0 no        256  256      0     0     0 0x00 0x00

         Programmer Type : linuxspi
         Description     : Use Linux SPI device in /dev/spidev*
avrdude linuxspi_program_enable() error: program enable instruction not defined for part ATxmega128A4U
avrdude linuxspi_initialize() error: AVR device not responding
avrdude main() error: initialization failed, rc=-1
        - double check the connections and try again
        - use -B to set lower the bit clock frequency, e.g. -B 125kHz
avrdude: AVR device initialized and ready to accept instructions
avrdude: device signature = 0x000000 (retrying)
avrdude: device signature = 0x000000 (retrying)
avrdude: device signature = 0x000000
avrdude main() error: Yikes!  Invalid device signature.
avrdude main() warning: expected signature for ATxmega128A4U is 1E 97 46

avrdude done.  Thank you.

LINUXGPIO ERROR:

pi@MY-pi:~ $ sudo avrdude -p x128a4u -C ~/avrdude_mine.conf -c raspberry_pi_gpio -v -F              
avrdude: Version 7.2-20231103 (08b82ea6)
         Copyright the AVRDUDE authors;
         see https://github.com/avrdudes/avrdude/blob/main/AUTHORS

         System wide configuration file is /home/pi/avrdude_MIB.conf
         User configuration file is /root/.avrduderc
         User configuration file does not exist or is not a regular file, skipping

         Using Port                    : gpiochip0
         Using Programmer              : raspberry_pi_gpio
         AVR Part                      : ATxmega128A4U
         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
           ----------- -------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           fuse1                   0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse2                   0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse4                   0     0     0    0 no          1    1      0     0     0 0x00 0x00
           fuse5                   0     0     0    0 no          1    1      0     0     0 0x00 0x00
           lock                    0     0     0    0 no          1    1      0     0     0 0x00 0x00
           prodsig     sigrow      0     0     0    0 no         64   64      0     0     0 0x00 0x00
           signature               0     0     0    0 no          3    1      0     0     0 0x00 0x00
           data                    0     0     0    0 no          0    1      0     0     0 0x00 0x00
           io                      0     0     0    0 no       4096    1      0     0     0 0x00 0x00
           fuse0                   0     0     0    0 no          1    1      0     0     0 0x00 0x00
           eeprom                  0     0     0    0 no       2048   32      0     0     0 0x00 0x00
           flash                   0     0     0    0 no     139264  256      0     0     0 0x00 0x00
           application             0     0     0    0 no     131072  256      0     0     0 0x00 0x00
           apptable                0     0     0    0 no       4096  256      0     0     0 0x00 0x00
           boot                    0     0     0    0 no       8192  256      0     0     0 0x00 0x00
           usersig                 0     0     0    0 no        256  256      0     0     0 0x00 0x00

         Programmer Type : linuxgpio
         Description     : Bitbang Raspberry Pi GPIO via linuxgpio (sysfs or libgpiod)
         Pin assignment  : /sys/class/gpio/gpio{n}
           RESET   =  1
           SCK     =  11
           SDO     =  10
           SDI     =  9
avrdude bitbang_program_enable() error: program enable instruction not defined for part ATxmega128A4U
avrdude bitbang_initialize() error: AVR device not responding
avrdude main() error: initialization failed, rc=-1
        - double check the connections and try again
        - use -B to set lower the bit clock frequency, e.g. -B 125kHz
avrdude: AVR device initialized and ready to accept instructions
avrdude: device signature = 0x000000 (retrying)
avrdude: device signature = 0x000000 (retrying)
avrdude: device signature = 0x000000
avrdude main() error: Yikes!  Invalid device signature.
avrdude main() warning: expected signature for ATxmega128A4U is 1E 97 46

avrdude done.  Thank you.

Any help would be appreciated.
Thanks,
Jay

Answered by mcuee

Nov 9, 2023

As of now, linuxspi and linuxgpio do not support PDI/UPDI/JTAG/DebugWire, only ISP.

View full answer

mcuee · 2023-11-09T01:54:58Z

mcuee
Nov 9, 2023
Maintainer

As of now, linuxspi and linuxgpio do not support PDI/UPDI/JTAG/DebugWire, only ISP.

1 reply

mcuee Nov 9, 2023
Maintainer

Existing discussions:

MCUdude · 2023-11-09T07:15:17Z

MCUdude
Nov 9, 2023
Maintainer

@stefanrueger shouldn't Avrdude print a sensible error message when the programmer and the part don't share a common programming interface?

EDIT:
Ah, it does print an error, but only if you don't manually override the signature check using -F. We should probably print the error regardless, but only exit the application if the signature check hasn't been overridden using -F.

avrdude/src/main.c

Lines 1113 to 1117 in 08b82ea

    
           if(!ovsigck && partdesc && (p = locate_part(part_list, partdesc)) && !(p->prog_modes & pgm->prog_modes)) { 
        
             pmsg_error("programmer %s cannot program part %s as they\n", pgmid, p->desc); 
        
             imsg_error("lack a common programming mode; use -F to override this check\n"); 
        
             exit(1); 
        
           }

8 replies

MCUdude Nov 9, 2023
Maintainer

Is there a way using AVRDUDE that I can program the 128A4U board from the Pi board with the GPIO lines that are connected?

In Theory, yes. If you can find or build an stk500v2 based programmer that has a serial port, you can use the built-in UART that the Pi offers to communicate to the programmer. But there's no way around using a dedicated programmer.

jaybstone Nov 9, 2023
Author

The x128A4U board is in production and already in the field. Using an stk500v2 based programmer is not feasible. A firmware update needs to be automated from the Pi board (which can receive its own software download update).

With the GPIO pins connected above, is programming possible if I implement the ISP (AVR910 Microchip document) or the PDI (AVR1612 Microchip document) from the Pi to the x128A4U? I'd like your opinion before I get started.

Also, if I had a USB connection between the Pi and the x128A4U, then AVRDUDE would work, correct?

Thanks again,
Jay

MCUdude Nov 9, 2023
Maintainer

Using a bootloader on the Xmega would work. I've tried the AVR109 based xboot bootloader which works like a charm on Xmegas. You could also install the FLIP2 bootloader if you want to communicate with the Xmega over USB. Avrdude supports both of these options.

jaybstone Nov 9, 2023
Author

I will try xboot.

Just curious, if the AVRDUDE linuxspi supports ISP, why can't I use that to program the x128A4U without using a bootloader? I have all the SPI and RESET connections.

Thanks,
Jay

jaybstone Nov 10, 2023
Author

MCUdude,

XBoot worked.

sudo avrdude -p x128a4u -P /dev/serial0 -c avr109 -b 115200 -U flash:w:test.hex

Thanks,
Jay

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

AVRDUDE linuxgpio/linuxspi and PDI #1561

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 9 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

AVRDUDE linuxgpio/linuxspi and PDI #1561

jaybstone Nov 9, 2023

Replies: 2 comments · 9 replies

mcuee Nov 9, 2023 Maintainer

mcuee Nov 9, 2023 Maintainer

MCUdude Nov 9, 2023 Maintainer

MCUdude Nov 9, 2023 Maintainer

jaybstone Nov 9, 2023 Author

MCUdude Nov 9, 2023 Maintainer

jaybstone Nov 9, 2023 Author

jaybstone Nov 10, 2023 Author

jaybstone
Nov 9, 2023

Replies: 2 comments 9 replies

mcuee
Nov 9, 2023
Maintainer

mcuee Nov 9, 2023
Maintainer

MCUdude
Nov 9, 2023
Maintainer

MCUdude Nov 9, 2023
Maintainer

jaybstone Nov 9, 2023
Author

MCUdude Nov 9, 2023
Maintainer

jaybstone Nov 9, 2023
Author

jaybstone Nov 10, 2023
Author