Hard fault when calling nrf_drv_twi_tx(). nRF52832.

RE: Hard fault when calling nrf_drv_twi_tx(). nRF52832.

Håkon Alseth — Tue, 17 Mar 2020 10:27:20 GMT

Hi,

[quote user="ConnorOsborn"]They stay high. I have tried P0.09, P0.10 and P019, P0.20[/quote]

P0.09 and P0.10 is the NFC pins. P0.19 and P0.20 are normally connected to LEDs on the DK, which can be problematic when you're trying to sink current (ie: then driving the pin to GND), so I would recommend that you try a GPIO that is unused, like P0.23 and P0.24. Flip over the DK, and you can see which pins are currently in use.

Could you try this and see if it starts working?

Kind regards,

Håkon

RE: Hard fault when calling nrf_drv_twi_tx(). nRF52832.

ConnorOsborn — Mon, 16 Mar 2020 21:31:35 GMT

After I switch the handle to NULL I still get the same issue. I would assume I should see something on the bus and clk happening but it always stays high on the scope. I have check that I am using the correct pins as well.

Edit: When I load up the twi_sensor example, I still see no change on SDA or SCL. They stay high. I have tried P0.09, P0.10 and P019, P0.20

RE: Hard fault when calling nrf_drv_twi_tx(). nRF52832.

Håkon Alseth — Mon, 16 Mar 2020 06:58:58 GMT

Hi,

[quote user="ConnorOsborn"]<error> app: ERROR 17 [NRF_ERROR_BUSY] at :0[/quote]

The nrf_drv_twi has been configured in non-blocking mode (ie: by providing a handler to the nrf_drv_twi_init() function), and the result is that the previous TWI bus transaction isn't finished yet when you're calling the next one. Since the library functions you're using assumes blocking, I would recommend that you init the driver in blocking mode:

err_code = nrf_drv_twi_init(&m_twi, &twi_MMA8652FC_config, NULL, NULL);

Kind regards,

Håkon

RE: Hard fault when calling nrf_drv_twi_tx(). nRF52832.

ConnorOsborn — Fri, 13 Mar 2020 21:16:02 GMT

Hello,

It never returns to the function, so I do not know the error code.
And yes, I verified the address in the data sheet. It couldn't have been changed because it states it is factory set and to have a different address it must be requested.

I have debug output now. I get this:
<info> app: Debug logging for UART over RTT started.
<info> app: Connected
<info> app: Data len is set to 0xF4(244)
<error> app: ERROR 17 [NRF_ERROR_BUSY] at :0
PC at: 0x00000000
<error> app: End of error report

RE: Hard fault when calling nrf_drv_twi_tx(). nRF52832.

Håkon Alseth — Fri, 13 Mar 2020 07:53:31 GMT

Hi,

[quote user=""] err_code = nrf_drv_twi_tx(&m_twi, MMA8652FC_ADDR, caddr, sizeof *caddr, true); // <-- Crash in this function
APP_ERROR_CHECK(err_code);[/quote]

What is the returned error code? Have you ensured that you have the correct address?

Kind regards,

Håkon