Page 1 of 1

[Q] Programming the pyBoard v1.1 in Arduino IDE?

Posted: Wed Oct 28, 2020 5:23 pm
by guidol
Maybe a odd question, but I try to use a pyBoard v1.1 for running another application.

So went wnt the following way to get support for STM32-Boards (like the STM32F405 on my pyboard)
in the Arduino IDE:

- Installing Arduino IDE
- getting STM32-Support via the Boardmanager and the Boards-URL
http://dan.drown.org/stm32duino/package ... index.json
- getting program/flash-Support for the STM32-Boards via the
STM32CubeProgrammer - which includes the CLI-Flash-command in the /bin directory

On my system the pyBoard is shown as COM4: (while running MicroPython) and connected via USB

I do set the Arduino IDE to a generic STM32F405RG board and the transfer-mode to DFU
Then I connect on the pyBoard 3.3V and BOOT0 for DFU-mode (COM4: goes away)

I can compile the sketch and it gets transfered to 0x8000000 (sometimes als referenced as 0x08000000) - but after the successful transfer and a reset to the pyBoard the LEDS keeping lit like in the DFU-mode and no COM-port is recognized :(

The only way to get the board to lige again is to flash MicroPython again via the DFU-Mode
(here I use dfu-utils under Linux) but can also try the STM32CubeProgrammer-GUI (which needs Java)
to flash the DFU-file

Has anyone successfully flashed/used a pyBoard (v1.1) with the Arduino IDE?
Is there another/special board-definition available for the Arduino IDE Boardmanager for the use with the pyBoard?

Re: [Q] Programming the pyBoard v1.1 in Arduino IDE?

Posted: Mon Dec 28, 2020 9:22 am
by appels
Hi,

I just wrote a tutorial on this, here is the link:
viewtopic.php?f=6&t=9496

Re: [Q] Programming the pyBoard v1.1 in Arduino IDE?

Posted: Wed Aug 17, 2022 5:09 pm
by guidol
Today with the STM32Duino v2.3.0 and STM32Programmer v2.11.0 I did get it to work :)

Now I could use the Arduino-IDE with my Pyboard v1.1 Clone (STM32F405RGT6)
and the compiled RunCPM (CP/M-Emulator) could use the MicroSD-Slot :)

@apples: from your Tutorial (Many Thanks for that) I had not to change variant.cpp anymore (FLASH_LATENCY_5)
(seems to be standard now for the STM32F4x group - wasnt anymore in the file)

Image