Flashing firmware

[IgnisWraithPrime]

How do you flash the firmware to the malenki nano?

[MarkR42]

Hi,

There is a programming connector J2 which expoes the UPDI signal from the microcontroller. This connector is designed to mate with a SOIC clip (Aka "soicbite" connector). The GND, VBAT and TXDEBUG are also available.

So pinout is 1- VBAT 3,4 - GND 6 - UPDI 8 - TXDEBUG ( a serial signal which writes debug messages)

You can connect the UPDI line to either

• A UPDI programmer, e.g. the one on the Microchip Attiny416 Xplained nano or other Microchip dev boards, an offiical programmer ( i haven't tried that)
• A jtag2updi board (which is usually an Arduino board)
• A USB-serial thing with a 4.7k resistor as described in https://github.com/microchip-pic-avr-tools/pymcuprog

On the host side you can use the "pymcuprog" program to flash the firmware and do some other things.

The firmware can be compiled from source using the command-line toolchain described here: https://github.com/MarkR42/avr_toolchain

Or you can use Microchip Studio for the whole thing probably with appropriate programmers. I expect the firmware source is compatible, as it uses the same header files etc as the "official" toolchain.

[justinas244]

Hi. Maybe you have your firmware who is possible to flash from arduino ide using jtag2updi programer and MegaTinyCore board library?

[MarkR42]

Hi, I didn't use the Arduino library for the firmware. Instead I've mostly written directly to the registers to program peripherals. I used the AVR C library for some of its functions (for example, delay loops)

I think what I'm doing is too time-sensitive to write using the Arduino library; I've got some assembler routines to bit-bang the SPI too.

[justinas244]

ah, ok. Then maybe is possible somehow to flash your firmware using jtag2updi programer? How i understand then i need flasher for your specific firmware, yes?

[justinas244]

because when i try use your added flasher in your project folder flasher.py and progtest.py nothing happen when i start these programs :D

[MarkR42]

because when i try use your added flasher in your project folder flasher.py and progtest.py nothing happen when i start these programs :D

Those are incomplete prototypes, I don't expect anything to work. I use pymcuprog to program the firmware, see flashcmd/flash1616.sh for an example.

[justinas244]

Sounds to complicated. Maybe in future you plan make tutorial step by step how flash firmwares in these modules :) ?

[justinas244]

i see that your code is writen in c language but in a7105_spi.c file is missing all spi functions

[MarkR42]

The SPI functions declared in a7105_spi.h are implemented in assembler in spi_asm.S

I know this is a bit confusing, but I did it to make the SPI bitbang a bit faster.

[justinas244]

At the beginning everything looked easy, now it's just getting harder to load your code :DD

[justinas244]

ok can you write step by step what i need do to flash your firmware to malenki?

[justinas244]

because now iam totally confused what i need do :D

[MarkR42]

I think you can use pymcuprog, see the script flashcmd/flash1616.sh for an example.

[IgnisWraithPrime]

The problem for us is that we do not have the appropriate flasher for attiny1616. We are trying to flash over arduino nano with jtag2updi. Is there a way to make jtag2updi work with pymcuprog? When we try to ping the nano with jtag2updi through pymcuprog it does not show up. Our next plan is to use avrdude and take the firmware from one malenki nano that we bought from a site and use that firmware for our maleknis that we ordered from pcbway

[MarkR42]

Hi,

I think you can use avrdude with jtag2updi to flash the 1616. At least this diagram suggests it's ok, https://github.com/ElTangas/jtag2updi

[IgnisWraithPrime]

We tried that we get an error that the file or directory does not exist. Cant really figure out where should the file be or how to input the path for avrdude. We are thinking that if we would get the firmware from a malenki then it would appear at the right location for avrdude.

[IgnisWraithPrime]

So we just tried again and realized that we were in system32 folder so we were unable to read or write anything. We navigated to the correct folder using cd commands and it worked

[IgnisWraithPrime]

Hi again. Would it be possible to addjust the unbind timer somehow? 90 seconds is quite a long time when i would need to control multiple bots with the same remote.

[MarkR42]

Hi,

If you need to run several robots with the same transmitter, use different transmitter profiles. This should enable the same tx to run several robots.

You don't need to rebind it unless you need to change to a different transmitter, e.g. if your main transmitter fails at an event and you need to use a spare.

Mark

On Sat, 11 Nov 2023 at 17:04, IgnisWraithPrime @.***> wrote:

Hi again. Would it be possible to addjust the unbind timer somehow? 90 seconds is quite a long time when i would need to control multiple bots with the same remote.

— Reply to this email directly, view it on GitHub https://github.com/MarkR42/malenki-nano/issues/10#issuecomment-1806866448, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAM2YUVZ2ZACP67HY5Y2UKLYD6VYVAVCNFSM6AAAAAA6P5HWSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBWHA3DMNBUHA . You are receiving this because you commented.Message ID: @.***>