SPI Master initialization with BLE

RE: SPI Master initialization with BLE

RK — Tue, 23 Jun 2015 00:25:59 GMT

This question is confusing because you're talking about two different issues and you've given the impression they are the same but I think they aren't. Firstly, as far as I can tell, the one you've discussed most is the crash on the sd_nvic_EnableIRQ() function inside the init. And that crash only occurs if you put the spi_master_open() before the ble_stack_init(). It's obviously going to crash if you do that because you can't call sd_* functions before you initialise the softdevice.

If, by the way, you'd answered this question which Aryan asked

can you check what is the error returned by sd_nvic_ClearPending?

and told him the answer was '2' he could have told you that. 2 is NRF_ERROR_SOFTDEVICE_NOT_ENABLED. You just told him you'd checked the IRQ, which wasn't what he asked. The documentation gives the API-specific error codes, any SD function can also return a generic SD error code.

Then it seems you have another error later when calling the send_recv() function. But you don't say what it is. The implication is that it's the same error but I rather doubt that. So what's that error, is it an error returned from a function, an APP_ERROR_CHECK() error, a hardfault, what is the actual error there?

Ignoring for now that the spi code doesn't do anything useful, just receives a byte into a location in stack memory and then throws it away again and the wisdom of waiting synchronously for the SPI master to write in the middle of a timer timeout.

RE: SPI Master initialization with BLE

gaminn — Mon, 22 Jun 2015 15:37:15 GMT

Please find the project in my reply to this question from Jun 17.

RE: SPI Master initialization with BLE

Susheel Nuguru — Mon, 22 Jun 2015 06:58:08 GMT

edit your question and in that you get an option to attach files, you can attach your project there as a zip file. I made you wait for three days, i could wait for few hours ;)

RE: SPI Master initialization with BLE

gaminn — Mon, 22 Jun 2015 06:42:15 GMT

What is the most convenient way to upload files to this forum? Sorry, but I will be able to upload the files again later this afternoon when I get back to my office.

RE: SPI Master initialization with BLE

Susheel Nuguru — Mon, 22 Jun 2015 06:26:51 GMT

Hi gaminn, I cannot download the file (says webpage is not available). Can you upload it again so that I can try it here.

RE: SPI Master initialization with BLE

gaminn — Fri, 19 Jun 2015 21:09:00 GMT

Thanks anyway for letting me know.

RE: SPI Master initialization with BLE

Susheel Nuguru — Fri, 19 Jun 2015 15:58:08 GMT

Im sorry gaminn, saw this too late, i will have to try this on Monday when I get back to my desk

RE: SPI Master initialization with BLE

gaminn — Thu, 18 Jun 2015 18:55:12 GMT

bleapphrs This is my project (HRS example with added SPI). SPI code is in main.c file. First problem is when spi_master_open() is called before ble_stack_init() in main() function, then an error occurs. You can try it. Another problem is when spi_master_send_recv() is called (it is in battery_level_meas_timeout_handler() function), then also an error occurs. Can you please test it and say what modifications should I make in order to be able to read a byte from battery_level_meas_timeout_handler() function? Thanks

RE: SPI Master initialization with BLE

Susheel Nuguru — Thu, 18 Jun 2015 07:24:53 GMT

did the same for APP_ERROR_CHECK(sd_nvic_ClearPendingIRQ(p_spi_instance->irq_type));

RE: SPI Master initialization with BLE

Susheel Nuguru — Thu, 18 Jun 2015 07:16:57 GMT

It just works fine for me, I have attached an image from my debugger showing that it passes that APP_ERROR_CHECK just fine.

RE: SPI Master initialization with BLE

gaminn — Thu, 18 Jun 2015 07:00:10 GMT

I use SDK 8.1, S110 softdevice, hardware nrf51 DK. Thanks for your help.

RE: SPI Master initialization with BLE

Susheel Nuguru — Thu, 18 Jun 2015 06:49:35 GMT

which SD and SDK are using? SPI is not a restricted peripheral, this error should not have happened. Many customers have been using SPI with softdevice and this error must have been flagged by all of them. Anyhow, give me details of your hardware, SD and SDK. I will try it out here

RE: SPI Master initialization with BLE

gaminn — Thu, 18 Jun 2015 06:40:43 GMT

According to API documentation developer.nordicsemi.com/.../a01316.html the only possible error code for this function is NRF_ERROR_SOC_NVIC_INTERRUPT_NOT_AVAILABLE . I checked that p_spi_instance->irq_type value is 3 or 4 (which are SPI0 or SPI1 IRQs numbers).

RE: SPI Master initialization with BLE

Susheel Nuguru — Thu, 18 Jun 2015 06:26:52 GMT

can you check what is the error returned by sd_nvic_ClearPending?

RE: SPI Master initialization with BLE

gaminn — Wed, 17 Jun 2015 18:00:19 GMT

ble_app_hrs.zip Is there any update on this? I have softdevice 8 application which needs to initialize SPI master, but I get hardfault or application reset on line:

APP_ERROR_CHECK(sd_nvic_ClearPendingIRQ(p_spi_instance->irq_type));

RE: SPI Master initialization with BLE

Susheel Nuguru — Mon, 27 Apr 2015 09:47:04 GMT

Are you still having this problem Cheney or were you able to fix it? Can you update us more here.

RE: SPI Master initialization with BLE

tmeizeli — Wed, 15 Apr 2015 13:46:44 GMT

You wouldn't happen to be calling spi_master_send_recv in an ISR would you? I had a similar problem and it is starting to look like that was the problem.

RE: SPI Master initialization with BLE

Susheel Nuguru — Mon, 13 Apr 2015 06:43:57 GMT

if it is OK for you can you PM me (if you do not want it to be public) your working environment, will save me lot of time.

RE: SPI Master initialization with BLE

Cheney — Fri, 10 Apr 2015 11:44:32 GMT

Thank you so much !

I may have complicated the thing. The main goal is just to have a working SPI master peripheral with a BLE collector...

Anyway thank you and have a nice weekend.

RE: SPI Master initialization with BLE

Susheel Nuguru — Fri, 10 Apr 2015 11:26:57 GMT

Seems strange, however I cannot know the reason for the hardfault unless I will be able to reproduce it myself and I do not have working setup to test this yet. I will try to reproduce this on monday.

RE: SPI Master initialization with BLE

Cheney — Fri, 10 Apr 2015 09:10:39 GMT

main.c

The SPI interrupt priority is set to low (same as the UART perif.).

Here is the function (located in spi_master.c) that causes the hardfault, exactly at the line

	 APP_ERROR_CHECK(sd_nvic_EnableIRQ(p_spi_instance->irq_type));

at the end of the function. Apparently it's when the softdevice is called to enable the SPI IRQ.

uint32_t spi_master_send_recv(const spi_master_hw_instance_t spi_master_hw_instance,
                              uint8_t * const p_tx_buf, const uint16_t tx_buf_len,
                              uint8_t * const p_rx_buf, const uint16_t rx_buf_len)
{
    #if defined(SPI_MASTER_0_ENABLE) || defined(SPI_MASTER_1_ENABLE)

    volatile spi_master_instance_t * p_spi_instance = spi_master_get_instance(
        spi_master_hw_instance);
    APP_ERROR_CHECK_BOOL(p_spi_instance != NULL);

    uint32_t err_code   = NRF_SUCCESS;
    uint16_t max_length = 0;
    
    uint8_t nested_critical_region = 0;
    
    //Check if disable all IRQs flag is set
    if (p_spi_instance->disable_all_irq)
    {
        //Disable interrupts.
        APP_ERROR_CHECK(sd_nvic_critical_region_enter(&nested_critical_region));
    }
    else
    {
        //Disable interrupt SPI.
        APP_ERROR_CHECK(sd_nvic_DisableIRQ(p_spi_instance->irq_type));
    }

    //Initialize and perform data transfer
    if (p_spi_instance->state == SPI_MASTER_STATE_IDLE)
    {
        max_length = (rx_buf_len > tx_buf_len) ? rx_buf_len : tx_buf_len;

        if (max_length > 0)
        {
            p_spi_instance->state        = SPI_MASTER_STATE_BUSY;
            p_spi_instance->bytes_count  = 0;
            p_spi_instance->started_flag = false;
            p_spi_instance->max_length   = max_length;

            /* Initialize buffers */
            spi_master_buffer_init(p_tx_buf,
                                   tx_buf_len,
                                   &(p_spi_instance->p_tx_buffer),
                                   &(p_spi_instance->tx_length),
                                   &(p_spi_instance->tx_index));
            spi_master_buffer_init(p_rx_buf,
                                   rx_buf_len,
                                   &(p_spi_instance->p_rx_buffer),
                                   &(p_spi_instance->rx_length),
                                   &(p_spi_instance->rx_index));

            nrf_gpio_pin_clear(p_spi_instance->pin_slave_select);
            spi_master_send_initial_bytes(p_spi_instance);
        }
        else
        {
            err_code = NRF_ERROR_INVALID_PARAM;
        }
    }
    else
    {
        err_code = NRF_ERROR_BUSY;
    }
		
    //Check if disable all IRQs flag is set.
    if (p_spi_instance->disable_all_irq)
    {   
        //Enable interrupts.
        APP_ERROR_CHECK(sd_nvic_critical_region_exit(nested_critical_region));
    }
    else
    {
        //Enable SPI interrupt.
			  APP_ERROR_CHECK(sd_nvic_EnableIRQ(p_spi_instance->irq_type));
        
    }

    return err_code;
    #else
    return NRF_ERROR_NOT_SUPPORTED;
    #endif
}

RE: SPI Master initialization with BLE

Susheel Nuguru — Fri, 10 Apr 2015 07:34:26 GMT

Check if you have not set the interrupt priority for the SPI to be too high, it cannot be higher priority than NRF_APP_PRIORITY_HIGH If it is possible to attach your file, then probably I take a look into it.

RE: SPI Master initialization with BLE

Cheney — Thu, 09 Apr 2015 13:15:28 GMT

Okay, I changed for SPI1 instead of SP0 and it's working (?!) until the line :

APP_ERROR_CHECK(sd_nvic_ClearPendingIRQ(p_spi_instance->irq_type));

which now causes the hard fault...

Thank you for your help.

RE: SPI Master initialization with BLE

Cheney — Thu, 09 Apr 2015 13:08:49 GMT

nRF51422-QFAC, the one with 32kB.

RE: SPI Master initialization with BLE

Susheel Nuguru — Thu, 09 Apr 2015 12:58:11 GMT

If you are using develoment kits with 32KB RAM then this should work, else 0x5800 is outside 16KB RAM. What hardware are you working on?