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

Improve support to raspberry pi 5 #90

Merged
merged 4 commits into from
Dec 9, 2024

Conversation

patrickelectric
Copy link
Member

@patrickelectric patrickelectric commented Nov 27, 2024

There are a couple of problems:

  • icm20689 can't use cs while in operation by OS in pi 5.
  • bmp390 is not compatible with bmp280 and the only implementation is async
    - Check bmp390: Add first version #93

Note: The tests to work it needs to restart the board since the pins will be "used" by the gpiosysfs system. This can be detected by running gpioinfo.

TODO: gpiochip0 should be used in pi 4 and gpiochip4 for pi5

@RaulTrombin
Copy link
Member

There is a workaround for icm2p689 that's change overlay spi-3cs to just spi-1cs, it's related to new kernel. I think the library need an update to use newer embedded-hal with cs pin.

There are a couple of problems:
- icm20689 can't use cs while in operation by OS in pi 5.
- bmp390 is not compatible with bmp280 e the only implementation is async

TODO: gpiochip0 should be used in pi 4

@patrickelectric
Copy link
Member Author

I believe that first we need an answer from: rust-embedded/linux-embedded-hal#116

@patrickelectric patrickelectric marked this pull request as ready for review December 8, 2024 09:10
@patrickelectric
Copy link
Member Author

this just add the new pin system for now

@patrickelectric patrickelectric marked this pull request as ready for review December 9, 2024 11:18
@patrickelectric patrickelectric changed the title Add support to raspberry pi 5 Improve support to raspberry pi 5 Dec 9, 2024
@RaulTrombin
Copy link
Member

There are a couple of problems:

  • icm20689 can't use cs while in operation by OS in pi 5.
  • bmp390 is not compatible with bmp280 and the only implementation is async

Note: The tests to work it needs to restart the board since the pins will be "used" by the gpiosysfs system. This can be detected by running gpioinfo.

TODO: gpiochip0 should be used in pi 4 and gpiochip4 for pi5

Do the rpi changed the hardware pin maps?

@patrickelectric
Copy link
Member Author

There are a couple of problems:

  • icm20689 can't use cs while in operation by OS in pi 5.

  • bmp390 is not compatible with bmp280 and the only implementation is async

Note: The tests to work it needs to restart the board since the pins will be "used" by the gpiosysfs system. This can be detected by running gpioinfo.

TODO: gpiochip0 should be used in pi 4 and gpiochip4 for pi5

Do the rpi changed the hardware pin maps?

The pi5 use a completely different hardware for gpio access

@patrickelectric patrickelectric merged commit 0ad8dc3 into bluerobotics:master Dec 9, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants