regarding the board with and without the flash chipset for nrf52840 board

[liuluan1984]

Hi Nordic, 

I am using your official board nrf52840 to develop my application based on the ble_app_uart_peripheral example. BLE communication and the spi interfaced sensor parts works fine with the official development board PCA10056 downloading with segger studio. but when I move the application to another board without the external flash chipset, it fail for running with the interruption from the sensor side. Any ideas for it? 

reference code 

[Jared]

Hi,

I can't see that you're actually using the external flash anywhere in your code. Could you point me towards where? 

How exactly is the application failing? 

Have you mapped the pins correctly? Could you share the custom board file that you're using for your custom board?

regards

Jared 

[liuluan1984]

Here is board I am using, the pin connection should be the same, it is the MDBT50Q-1MV2 module board.

Here is the reference   https://www.raytac.com/download/index.php?index_id=43 

[Jared]

Hi,

Have you remembered to flash the Softdevice?

Just to exclude any possible HW issues. Could you instead of using your application try to flash board with the unmodified SPI example from the SDK. If this example works, then we can safely assume that your issue is not HW dependent. Next, only after confirming that it works unmodified, you can try to switch the pins in the example with the pins that you use in your application. 

Regarding your code:

liuluan1984 said:

When I am using the official board all works fine, when i am using the raytac board, it never go into the interruption for reading the fifo. 

 I assume that you're referring to the in_pin_handler() that is supposed to be called on a LOW to HIGH event? Could you set a breakpoint in the handler and check that the program doesn't stop when you set the PIN_INTERRUPT to high. 

Also, where is lsm9ds1_fifo_data_level_get() and similar functions defined? What serial communication are they using, SPI?

regards

Jared

[liuluan1984]

I have not flashed the softdevice, maybe I need to find a guide for that

in_pin_handler() that is supposed to be called on a LOW to HIGH event? YES

I am using the sgger as development environment, 

"lsm9ds1_fifo_data_level_get" is defined in the file "lsm9ds1_reg.c"

lsm9ds1_reg.c

int32_t lsm9ds1_fifo_data_level_get(stmdev_ctx_t *ctx, uint8_t *val)
{
lsm9ds1_fifo_src_t fifo_src;
int32_t ret;
ret = lsm9ds1_read_reg(ctx, LSM9DS1_FIFO_SRC, (uint8_t *)&fifo_src,
1);
*val = fifo_src.fss;
return ret;
}

[Jared]

Hi,

Yes the softdevice has to be flashed if your application uses BLE. Also:

 

Jared said:

Just to exclude any possible HW issues. Could you instead of using your application try to flash board with the unmodified SPI example from the SDK. If this example works, then we can safely assume that your issue is not HW dependent. Next, only after confirming that it works unmodified, you can try to switch the pins in the example with the pins that you use in your application. 

 

Jared said:

Could you set a breakpoint in the handler and check that the program doesn't stop when you set the PIN_INTERRUPT to high. 

[liuluan1984]

thank you, I will try to test the soft deivce first. then i will test the PIN_INTERRUPT to high. 

[liuluan1984]

I find it is not the interruption issue or not the spi issue, i have sloved it. thank you. please close the case