> I also noticed that 536915151 is 0x2000ACCF, which seems like a memory
> pointer, which raises my suspicion there is some misconfiguration issue.
This error message shows wrong information, fixed here
https://github.com/apache/nuttx/pull/11843
But still if this message is printed, something is
Hi Mauro,
I think there is some issue in your SPI (I don't know if it is in your
configuration, or on your wiring, or in our device, or something else).
The issue you are seeing (only 1 bit transmitted) could be confirmed by
this error message:
nrf52_spi_exchange: Incomplete transfer wrote 53691
Hi,
I made the recommended change and it compiled normally, but I saw that the
code was missing the implementation of the CS signal, so I made the changes
below and it still didn't work. Does the code really work for the
nRF52832-DK? I used my logic analyzer and there is no information on the
data
My mistake, I looked at the reported errors wrong. BMI160 code is broken
after recent changes. Fix is here https://github.com/apache/nuttx/pull/11789
wt., 27 lut 2024 o 02:33 Mauro Sollar napisał(a):
> This option was already checked, but I hadn't described it completely in
> the previous email.
This option was already checked, but I hadn't described it completely in
the previous email.
System type
nRF52 Peripheral Selection
(*) SPI 0 <--- actually (*) SPI 0 Master
Could it be this part of the code in Bringup that is wrong?
struct spi_dev_s *dev = nrf52_spibus_initiali
You need to specify that SPI is used as master: CONFIG_NRF52_SPI0_MASTER=y
niedz., 25 lut 2024 o 21:22 Mauro Sollar napisał(a):
> Hi,
>
> I'm trying to use the BMI160 sensor with the Nordic nRF52832-dk Kit, help
> me please!
>
> Kconfig Configuration:
>
> System type
> nRF52 Peripheral Selecti
Hi,
I'm trying to use the BMI160 sensor with the Nordic nRF52832-dk Kit, help
me please!
Kconfig Configuration:
System type
nRF52 Peripheral Selection
(*) SPI 0
Device Drivers
(*) SPI Driver Support
(*) SPI character driver
(*) Sensor Device Support
(*) Bosch BMI160 Inertial Me
