Best place to get started

RE: Best place to get started

RK — Mon, 22 May 2017 12:46:37 GMT

replying to a 4 year old thread isn't going to get you anywhere. Start a new one, reference this thread if you want. A lot has changed in 4 years.

RE: Best place to get started

Hust — Mon, 22 May 2017 10:45:32 GMT

Hi all, Currently, I'm doing project with MPU in notify mode 1 second period, before using this sd_twi_hw_master, I used twi_sw_master and it work well. However, I tried to use twi_hw_master and it got kind of confict so my cell phone can not see nRF51822, now I use this one, the cell phone recognize it but the data is not changing over time, it fixed, how can i solve this problem?

RE: Best place to get started

Chocol8 — Wed, 10 May 2017 09:09:55 GMT

Hello, I have faced the same problem. And code forces a system reset which starts the whole initialization from the begin. What changes you have made to prevent this?

RE: Best place to get started

Vijayalakshmi — Thu, 21 Apr 2016 13:45:19 GMT

can we use the same sd_twi_hw_master file along with s132 also? and the link is broken. couldnt download

RE: Best place to get started

scytulip — Sun, 14 Dec 2014 23:06:25 GMT

Hi, Alseth. This issue still exists in the newest SDK 7.1. But your code works fine. May you submit your code as a revision for furture PDKs? Thanks.

RE: Best place to get started

Håkon Alseth — Thu, 12 Jun 2014 09:22:44 GMT

I've re-posted the link. It should work now.

RE: Best place to get started

Håkon Alseth — Thu, 12 Jun 2014 09:22:41 GMT

I've re-posted the link. It should work now.

RE: Best place to get started

Marius R. — Tue, 03 Jun 2014 12:51:36 GMT

The above link is broken (like every other link in this forum). Can anyone tell me how to get this file anyway.

RE: Best place to get started

sky — Tue, 03 Jun 2014 03:07:19 GMT

Hi,

I also met the problem , but the file "sd_twi_hw_master (2).c" has been passed ,can you send it again ?

RE: Best place to get started

Jeff Craighead — Tue, 15 Oct 2013 18:49:22 GMT

I'm starting to work on something similar with the S110 and the TWI and some other on chip hardware (SPI, temp sensor, GPIOs) that will interfere with the S110. As I'm reading the docs I don't see anything obvious that says "Include XXX if using a SoftDevice, or use YYY if not." So is there a simple list of SoftDevice safe APIs/includes for various hardware access? I see the SoC library functions documentation, but nothing there is related to TWI, SPI. I would assume that means they could be used without any problem (also Table 4 in the SoftDevice Spec), but as posted above TWI uses some PPI channels, which will cause problems. What's the best guidance on accessing hardware while the SD is enabled?

RE: Best place to get started

Wobs — Tue, 13 Aug 2013 20:08:40 GMT

right, the problem was something else I believe, now it works, thanks!

RE: Best place to get started

sd — Tue, 13 Aug 2013 12:47:25 GMT

Are you using the SoftDevice? If so, use the code Håkon attached above. It worked for me!

RE: Best place to get started

Wobs — Mon, 12 Aug 2013 18:25:53 GMT

Hi,

I'm using the attached, modified, SoftDevice compatible TWI code with the BLE heart rate example for the pca10001. I initialize the TWI master like in this order:

int main(void)
{
    uint32_t err_code;

    timers_init();
    gpiote_init();
    buttons_init();
	
    // Initialize TWI
    twi_master_init();

and the code fails at the asserts and forces a system reset...

    /*
    NRF_PPI->CH[0].EEP = (uint32_t)&NRF_TWI1->EVENTS_BB;
    NRF_PPI->CH[0].TEP = (uint32_t)&NRF_TWI1->TASKS_SUSPEND;
    NRF_PPI->CHENCLR = PPI_CHENCLR_CH0_Msk;*/
    err_code = sd_ppi_channel_assign(0,
                                     &(NRF_TWI1->EVENTS_BB),
                                     &(NRF_TWI1->TASKS_SUSPEND));
    ASSERT(err_code == NRF_SUCCESS);

What is the problem here, shall I initialize the TWI in a different order?

RE: Best place to get started

Ole Morten — Thu, 01 Aug 2013 10:53:36 GMT

To clean things up, I'd be happy if you could evaluate the answer you have received and accept it if you feel it's sufficient. If not, it might be useful to expand your question a little and provide further information.

RE: Best place to get started

Håkon Alseth — Fri, 12 Jul 2013 12:33:17 GMT

You can see the "twi_sw_master_example" in the SDK to see how to init the library (it uses bit banged TWI, but library calls are equal). The "ble_app_template" has one button set up, which is "WAKEUP_BUTTON_PIN". This must match the button on your board (GPIO 16 or 17, if my memory serves me right). Other than that there should be no other issues using this example on the ev board.

RE: Best place to get started

sd — Fri, 12 Jul 2013 12:25:35 GMT

Thanks! The "ble_app_template" is under a different board; does that matter? Also, the TWI example is the API -- is there an example of how to set the pins and other registers?

RE: Best place to get started

Håkon Alseth — Fri, 12 Jul 2013 10:35:18 GMT

Hi,

If you want to start with a new project and setup all your characteristics and services, there is a blank project called "ble_app_template".

The TWI uses some PPI channels, which is restricted when the SoftDevice S110 is active. Please use the attached .c file for TWI communication when using it with S110 BLE stack.

The getting started is a small part of the user guide for the EV/DEV kit. Here's a quick link to the EV kit user guide: www.nordicsemi.com/.../21312489

BR Håkon

sd_twi_hw_master (2).c