Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
flow3r firmware
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
flow3r
flow3r firmware
Commits
17c67375
Commit
17c67375
authored
1 year ago
by
TheNewCivilian
Committed by
q3k
1 year ago
Browse files
Options
Downloads
Patches
Plain Diff
docs: Fix copy + bring back title
parent
3b3da2dc
No related branches found
No related tags found
1 merge request
!139
docs: Add USB access instructions
Pipeline
#6707
passed
1 year ago
Stage: check
Stage: build
Stage: deploy
Changes
1
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/badge/firmware.rst
+13
-15
13 additions, 15 deletions
docs/badge/firmware.rst
with
13 additions
and
15 deletions
docs/badge/firmware.rst
+
13
−
15
View file @
17c67375
...
@@ -77,23 +77,9 @@ This is the SPI flash partition layout we use:
...
@@ -77,23 +77,9 @@ This is the SPI flash partition layout we use:
Setup USB access rules
Accessing files from a PC
-------------------------
-------------------------
.. warning::
**Did you set up USB access rules already?**
To let ``mpremote`` to work properly your user needs to have access rights to ttyACM.
Quick fix: ``sudo chmod a+rw /dev/ttyACM[Your Device Id here]```
More sustainable fix: Setup an systemd rule to automatically allow the logged in user to access ttyUSB
1. To use this, add the following to /etc/udev/rules.d/60-extra-acl.rules: ``KERNEL=="ttyACM[0-9]*", TAG+="udev-acl", TAG+="uaccess"``
2. Reload ``udevadm control --reload-rules && udevadm trigger``
If the badge is running correctly, you can access the filesystem over the micropython REPL, using tools like mpremote.
If the badge is running correctly, you can access the filesystem over the micropython REPL, using tools like mpremote.
::
::
...
@@ -114,6 +100,18 @@ If the badge is running correctly, you can access the filesystem over the microp
...
@@ -114,6 +100,18 @@ If the badge is running correctly, you can access the filesystem over the microp
0 st3m
0 st3m
0 .sys-installed
0 .sys-installed
.. warning::
**Your flow3r is not showing up using Linux?**
To let ``mpremote`` to work properly your user needs to have access rights to ttyACM.
Quick fix: ``sudo chmod a+rw /dev/ttyACM[Your Device Id here]```
More sustainable fix: Setup an udev rule to automatically allow the logged in user to access ttyUSB
1. To use this, add the following to /etc/udev/rules.d/60-extra-acl.rules: ``KERNEL=="ttyACM[0-9]*", TAG+="udev-acl", TAG+="uaccess"``
2. Reload ``udevadm control --reload-rules && udevadm trigger``
You can also put the badge into :ref:`Disk Mode` to make it appear as a USB pendrive
You can also put the badge into :ref:`Disk Mode` to make it appear as a USB pendrive
on your PC. However, only one of the two FAT32 block devices (internal flash
on your PC. However, only one of the two FAT32 block devices (internal flash
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment