This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

micro esb and ble on 130 v2 project

Hi, Because I didn't want to keep with the last question when this is a tottaly new one, so created another question. I've tried to get this project to work:

github.com/.../nrf51-ble-micro-esb-uart

It doesn't compile from start. I'm missing bsp.c.h files, I'm having an error on the app_timer_init setup call. To get this project up I've used sdk 10 and 9.0 and as result none of the combinations works. When ignoring the bsp include and changing the app_timmer_init to something like: "APP_TIMER_INIT(APP_TIMER_PRESCALER, 5, 0);" it compiles. Tried to get it working along with s130 1.0 and 2.0 but keeps running into hard_fault. (Yes I took in consideration the different sizes of the SDs, setting the correct memory start address on the project defenitions )

Is there any chance you can point me to a full project that I can just download and get working? Thank you for your attention and help, looking forward for your reply.

Parents
  • Hi, the QFACA1 build code is the latest 3rd revision of the nRF51-series, and the variant with the largest RAM size. So this should be good. A few things you might check: devzone.nordicsemi.com/.../

  • Right, So I've been around and around the disassemble and some tick counters and concluded that the end of time slot request was being done to late, or so it seems. So, instead of using the end of slot interrupt setting and handler to end the time slot, I've called the end of time slot directly from the soft device timer0 interrupt signal, and this sorted the situation!

    Then piped the uesb rx data to the ble tx and the ble rx to the uesb tx and can now have 2 devices connected messaging to each other through ble piped through uesb.

    I'm still trying to understand exactly if the hard fault was due to end of slot irq being happening after slot timeout or if there was something else going on...

    Any who, this is where I'm now. Please advise about calling the end of slot from inside the SD timer0 handler.

    Thank you

Reply
  • Right, So I've been around and around the disassemble and some tick counters and concluded that the end of time slot request was being done to late, or so it seems. So, instead of using the end of slot interrupt setting and handler to end the time slot, I've called the end of time slot directly from the soft device timer0 interrupt signal, and this sorted the situation!

    Then piped the uesb rx data to the ble tx and the ble rx to the uesb tx and can now have 2 devices connected messaging to each other through ble piped through uesb.

    I'm still trying to understand exactly if the hard fault was due to end of slot irq being happening after slot timeout or if there was something else going on...

    Any who, this is where I'm now. Please advise about calling the end of slot from inside the SD timer0 handler.

    Thank you

Children
No Data
Related