More typos -> LSM6DSO
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Open lsm6dso_STdC/examples/lsm6dso_self_test.c and inspect the references at lines 307 and 348. Verify the self-test example uses the LSM6DSO gyroscope constants and setter shown in the issue, then confirm the file no longer contains these two mismatches.
Written by the indexing model from the issue text.
Description
I was initially not aware that each directory is for one sensor.
I thought it is a software variant (or X as place holder for some hardware variants)
and even wanted to question here what is different between each directory, e.g.
like LSM6DSO, LSM6DSOX, LSM6DSO32, LSM6DSO32X.
Question beside: Are they in some kind (backward) compatible?
So e.g. code for LSM6DSO can run on all other mentioned device (when not using the additional features)?
But back to LSM6DSO source code:
LIS2DH12_GY_ST_NEGATIVE
->
LSM6DSO_GY_ST_NEGATIVE
lsm6dso_xl_data_rate_set(&dev_ctx, LSM6DSO_GY_ODR_OFF);
->
lsm6dso_gy_data_rate_set(&dev_ctx, LSM6DSO_GY_ODR_OFF);
(same as https://github.com/STMicroelectronics/STMems_Standard_C_drivers/issues/142 )
I am at the moment using only self test code, so not checked the other example files.
- Dominant language
- C
- Stars
- 885
- Forks
- 538
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from STMicroelectronics/STMems_Standard_C_drivers
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
STMicroelectronics/STMems_Standard_C_drivers#184 · 2 reactions ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
bug
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
question
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in STMicroelectronics/STMems_Standard_C_drivers
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
colbymchenry/codegraph#2770 ·
Maintainers usually reply within 1 day
-
area/ysql kind/enhancement priority/medium status/awaiting-triage
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
yugabyte/yugabyte-db#35578 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Bug Status: Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
interpreter-core type-feature
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day