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

Implement entry point for functional blocks #73

Open
CloudyPadmal opened this issue Apr 18, 2021 · 1 comment
Open

Implement entry point for functional blocks #73

CloudyPadmal opened this issue Apr 18, 2021 · 1 comment

Comments

@CloudyPadmal
Copy link
Collaborator

When user turns on PSLab device, we should have two paths for them to move forward

  • Normal mode
  • Standalone mode

Implement a logical pathway to manage these two path entries depending on requirements.

  • Normal mode: UART communication
  • Standalone mode: read from SD card and set instruments
@CloudyPadmal
Copy link
Collaborator Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant