[Question] How to flash a specific (CI) firmware onto a primehub

[BertLindeman]

Question
Where can I find the current doc about how to flash CI-firmware onto a primehub

Context
(Sorry, my memory..)
I know it is not yet really supported, but I am very curious about the filesystem on the hubs.
I want to try this snippet
Looking at the update, I think this experiment is only available on the primehub.
Using install does not install the most current CI-firmware.

Screenshots

[dlech]

pybricksdev flash firmware.zip

[BertLindeman]

What I forgot was to keep pressing the bluetooth button before connecting with the USB cable...
Thank you David. The hint triggered enough to get going.

[laurensvalk]

I want to try this snippet

Since you ask --- If you want to try something even more experimental, try this build.

Try running a new program. Then try pressing the center button to see what happens. 😉

[BertLindeman]

Took me quite some time to get the firmware installed (win10 - got timeouts)
Now happy 😄

('primehub', '3.1.0b1', 'v3.1.0b1-14-g7ca4742d on 2021-09-29')

And another line I will not disclose

[laurensvalk]

Are you sure that is the version I linked to above? It should be from October 6.

[BertLindeman]

Sharp eye, Laurens Thank you!
re-did: (To help my memory)
primehub press bluetooth button until connected via USB

dir:

2021-10-06  19:45           359.202 primehub-firmware.zip

On windows command prompt:

C:\Users\bert.grijshuid\Downloads\Lego\Pybricks\CI firmware>pybricksdev flash primehub-firmware.zip
Creating firmware
Failed to retrieve string descriptor 5
Failed to retrieve string descriptor 6
Failed to retrieve string descriptor 7
dfu-util 0.10-dev

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Multiple alternate interfaces for DfuSe file
Opening DFU capable USB device...
Device ID 0694:0008
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "LEGO LES HUB "
File contains 1 DFU images
Parsing DFU image 1
Target name: ST...
Image for alternate setting 0, (1 elements, total size = 245568)
Setting Alternate Interface #0 ...
Parsing element 1, address = 0x08008000, size = 245560
Erase           [=========================] 100%       245560 bytes
Erase    done.
Download        [=========================] 100%       245560 bytes
Download done.
Done parsing DfuSe file

Version reported now is:
('primehub', '3.1.0b1', 'v3.1.0b1-22-g178f280b on 2021-10-06')
As you predicted 😉

Running a new (empty) program does "nothing" as I would expect.
Then pressing the center button seems to re-run the empty program.
After the flash I ran a small program to verify the version.
Should I have NOT done that?

[laurensvalk]

Running a new (empty) program does "nothing" as I would expect.
Then pressing the center button seems to re-run the empty program.

Right, so maybe try something non-empty, such as something with lights/motors 😄

[laurensvalk]

So the expected result is that when you run a program, it's saved on the hub. You can start it again with the button - no flashing required.

[BertLindeman]

Ah, right.

So run a program.

And on the center press after the run . . .
That same program runs again.
Sooo, the program (probably main.py) is stored onto the hub.

Side step:
Am I right that the experimental file classes are not included here (or renamed?)

from pybricks.experimental import flash_init_spi, flash_init_littlefs, flash_read_raw, flash_read_file

results in

Traceback (most recent call last):
  File "main.py", line 5, in <module>
ImportError: can't import name flash_init_spi

[laurensvalk]

Sooo, the program (probably main.py) is stored onto the hub.

Yes! Thanks for taking the time to test.

Am I right that the experimental file classes are not included here

To see what's included, just enter the REPL, begin typing flash and hit tab to auto-complete.

[BertLindeman]

To see what's included, just enter the REPL, begin typing flash and hit tab to auto-complete.

Of course.

So file access is becoming simpler, no init needed now.

My snippet:

# from pybricks.experimental import flash_init_spi
# from pybricks.experimental import  flash_init_littlefs
from pybricks.experimental import  flash_read_raw
from pybricks.experimental import  flash_read_file

# Init SPI and file system
# flash_init_spi()
# flash_init_littlefs()

# Read information about the file system
info = flash_read_raw(address=0, len=58)
print(info)

# Read an existing file. Use the original firmware to create this file.
filename = "main.py"
data = flash_read_file(filename)
print("\nPrinting file", filename)
print(data)

Sorry I take so much of your time.
And thank you for the support!
[EDIT] typo "tape' -> 'take'

[laurensvalk]

There's a write function as well now, so

Use the original firmware to create this file.

is technically no longer required. But it's still possible.

Our goal is that both Pybricks and the official firmware can see and access the same files.

So it would be interesting if you want to try creating a few files with both firmwares, and see if you can read them with the other firmware without trouble.

Sorry I take so much of your time.

On the contrary, thanks for testing this undocumented experimental stuff 😉