You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now we have a bootloader in PSLab firmware. If users have production ready .HEX files, using Unified Bootloader app, they can upgrade/change the current firmware instantly.
What if: if we have two hex files,
one for normal mode
one for standalone mode where it handles SDcard operations and data logging.
Because these two modes are not usually switched between very frequently, I can assume a user might be able to upload the correct firmware hex file using bootloader (which will take 5 seconds).
This will also simplify the firmware architecture.
When user turns on PSLab device, we should have two paths for them to move forward
Implement a logical pathway to manage these two path entries depending on requirements.
The text was updated successfully, but these errors were encountered: