Building

The official PYBD running MicroPython, and its accessories.
Target audience: Users with a PYBD
User avatar
devnull
Posts: 452
Joined: Sat Jan 07, 2017 1:52 am
Location: Singapore / Cornwall
Contact:

Building

Post by devnull » Mon Apr 01, 2019 12:42 pm

Hi all;

I am still using the firmware that it was shipped with, but want to add my frozen files etc.

1. Do I use the same build binary for the pyboard1.1 now for the pyboard-d ?
2. How do you put it into DFU mode ? - I have tried pulling BOOT0 > 3V3

tine3700
Posts: 14
Joined: Tue Sep 13, 2016 7:08 am

Re: Building

Post by tine3700 » Mon Apr 01, 2019 2:06 pm

Hi,

you can put a PYBD in DFU mode with these steps:

1. Hold down USR button and press the RST button
2. The RGB LED flashes red, green, blue, white
3. Release the USR button as soon as the RGB LED flashes white to enter DFU mode
4. Now the RGB LED blinks red, to show PYBD is in DFU mode

User avatar
devnull
Posts: 452
Joined: Sat Jan 07, 2017 1:52 am
Location: Singapore / Cornwall
Contact:

Re: Building

Post by devnull » Mon Apr 01, 2019 2:08 pm

Managed to get it into DFU mode and used PYBOARD1.1 Binary to flash to it, or course that broke it.

So now I have a broken PYBOARD-D - is this the first ??

But I don't see a PYBboard definition in the ports/stm32/boards folder ??

Code: Select all

B_L475E_IOT01A		NUCLEO_F746ZG		STM32F411DISC		common_ifs.ld		stm32f091_af.csv	stm32f439.ld		stm32h743_af.csv
CERB40			NUCLEO_F767ZI		STM32F429DISC		make-pins.py		stm32f091xc.ld		stm32f439_af.csv	stm32l432.ld
ESPRUINO_PICO		NUCLEO_H743ZI		STM32F439		openocd_stm32f4.cfg	stm32f401_af.csv	stm32f4xx_prefix.c	stm32l432_af.csv
HYDRABUS		NUCLEO_L432KC		STM32F4DISC		openocd_stm32f7.cfg	stm32f401xd.ld		stm32f722.ld		stm32l476_af.csv
LIMIFROG		NUCLEO_L476RG		STM32F769DISC		openocd_stm32l4.cfg	stm32f401xe.ld		stm32f722_af.csv	stm32l476xe.ld
NETDUINO_PLUS_2		OLIMEX_E407		STM32F7DISC		pllvalues.py		stm32f405.ld		stm32f746.ld		stm32l476xg.ld
NUCLEO_F091RC		PYBLITEV10		STM32L476DISC		startup_stm32f0.s	stm32f405_af.csv	stm32f746_af.csv	stm32l496_af.csv
NUCLEO_F401RE		PYBV10			STM32L496GDISC		startup_stm32f4.s	stm32f411.ld		stm32f767.ld		stm32l496xg.ld
NUCLEO_F411RE		PYBV11			common_basic.ld		startup_stm32f7.s	stm32f411_af.csv	stm32f767_af.csv
NUCLEO_F429ZI		PYBV3			common_bl.ld		startup_stm32h7.s	stm32f429.ld		stm32f769.ld
NUCLEO_F446RE		PYBV4			common_blifs.ld		startup_stm32l4.s	stm32f429_af.csv	stm32h743.ld

ThomasChr
Posts: 120
Joined: Sat Nov 25, 2017 7:50 am

Re: Building

Post by ThomasChr » Mon Apr 01, 2019 2:24 pm

@devnull:
As far as I know there is no Sourcecode nor Firmware for the Pyboard D.
Damien did not tell if and when there will be any of that available.

User avatar
Roberthh
Posts: 1958
Joined: Sat May 09, 2015 4:13 pm
Location: Rhineland, Europe

Re: Building

Post by Roberthh » Mon Apr 01, 2019 3:09 pm

At least the binary images should be published on the Download page.

ThomasChr
Posts: 120
Joined: Sat Nov 25, 2017 7:50 am

Re: Building

Post by ThomasChr » Mon Apr 01, 2019 4:07 pm

I‘m sure they will be published soon.
And I hope the source will also be published!

User avatar
Roberthh
Posts: 1958
Joined: Sat May 09, 2015 4:13 pm
Location: Rhineland, Europe

Re: Building

Post by Roberthh » Mon Apr 01, 2019 5:08 pm

It's not that urgent. The board works well so far. Only @devnull needs a new firmware.

ThomasChr
Posts: 120
Joined: Sat Nov 25, 2017 7:50 am

Re: Building

Post by ThomasChr » Mon Apr 01, 2019 5:17 pm

Should we raise donations for devnull so that he can afford a new Pyboard D? ;-)

ThomasChr
Posts: 120
Joined: Sat Nov 25, 2017 7:50 am

Re: Building

Post by ThomasChr » Tue Apr 02, 2019 9:27 am

The binary firmware is here: https://micropython.org/download#pybd
Still no answer from Damien if and when the source will be available... :-(

Damien
Site Admin
Posts: 634
Joined: Mon Dec 09, 2013 5:02 pm

Re: Building

Post by Damien » Wed Apr 03, 2019 8:03 am

I have now made available the code, so you can build PYBD firmware yourself using the code posted here: https://github.com/micropython/micropython/pull/4669

For the low-level WiFi driver there is a binary blob, which is unavoidable given the nature of WiFi regulations. I tried to make it so that this binary code is confined and minimised.

Thanks for your patience waiting for this! If you have any issues building it, please leave a comment on the github PR.

Post Reply