Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Keep the hub name as a default when installing/re-installing PyBricks Firmware #1415

Open
afarago opened this issue Feb 4, 2024 · 2 comments
Labels
enhancement New feature or request software: pybricks-code Issues with https://code.pybricks.com application topic: flashing firmware Issues related to fhe firmware flashing process

Comments

@afarago
Copy link

afarago commented Feb 4, 2024

Is your feature request related to a problem? Please describe.
When flashing the hub with the pybricks firmware it would be awesome to keep the hub name intact.

Describe the solution you'd like
We have multiple hubs for robotics (FLL, WRO, Edutus Robotics Cup) and while flashing / updating the firmware it is cumbersome to re-enter the hub name again and again.

Possible solutions:

  1. if connected to a hub and starting the "Install Pybricks Firmware" - take the name of the hub Instead of the default to the step3 - Hub name.
  2. while flashing the firmware add an option (checkbox) to step3 - Hub name (optional) to keep the current name and read it when selecting the DFU in step 4.

I am not sure if hub name is available in DFU mode of a PyBricks firmware Hub.
I am not sure if hub name is available in DFU mode of a stock LEGO SPIKE or Mindstorms Hub.

Describe alternatives you've considered
Currently I check which hub I am flashing and re-entering the name.

Additional context
N/A

@afarago afarago added enhancement New feature or request triage Issues that have not been triaged yet labels Feb 4, 2024
@afarago afarago changed the title [Feature] Keep the hub name as a default when installing/re-sinatlling PyBricks Firmware [Feature] Keep the hub name as a default when installing/re-installing PyBricks Firmware Feb 4, 2024
@dlech dlech added software: pybricks-code Issues with https://code.pybricks.com application topic: flashing firmware Issues related to fhe firmware flashing process and removed triage Issues that have not been triaged yet labels Feb 4, 2024
@dlech
Copy link
Member

dlech commented Feb 4, 2024

I am not sure if hub name is available in DFU mode of a PyBricks firmware Hub.

Sort of, but it isn't in a fixed location, so we currently don't have a way to find it. But the firmware could be modified to add some mechanism to find it.

I am not sure if hub name is available in DFU mode of a stock LEGO SPIKE or Mindstorms Hub.

IIRC, there is a pointer table at a fixed position in the flash memory (at least for 2.x firmware, not sure about newer LE SPIKE 3 firmware) that has a pointer to the hub name, so maybe possible.

When flashing the hub with the pybricks firmware it would be awesome to keep the hub name intact.

This is something I've thought about a time or two as well. The best possible solution I have though of so far would be to update the "default" hub name with the name of the last connected hub. For people with one hub, this would always be the right name. For people updating multiple hubs, they would have to connect regularly first to have the name read (no other interaction would be required, just connect) and then put the hub in update mode and go through the update process.

@afarago
Copy link
Author

afarago commented Feb 4, 2024

The best possible solution I have though of so far would be to update the "default" hub name with the name of the last connected hub

Would love this solution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request software: pybricks-code Issues with https://code.pybricks.com application topic: flashing firmware Issues related to fhe firmware flashing process
Projects
None yet
Development

No branches or pull requests

2 participants