https://devzone.nordicsemi.com/f/nordic-q-a/12618/freertos-with-gazell-problem-on-nrf51Hi All, We have been developing device with pca10028 evaluation board and in the process we use also few other custom boards with nrf51822. We use IAR. The device system is based on FreeRTOS, contains SPI controlled lcd display, the buttons of pca10028en-USTelligent Community 13Thu, 26 May 2016 07:37:18 GMThttps://devzone.nordicsemi.com/thread/47922?ContentTypeID=1Thu, 26 May 2016 07:37:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c9162d55-4cea-4d04-af87-7a4439f64cabmilen.icom<p>A little update on the matter. We are on the final development stage of our product. So we moved from the pca10028 to our product board which uses NRF51822QFAAH0. The pairing library is preprogrammed and does not use any pairing procedure functions. But we started to experience again the same problem, crashing with FreeRTOS the same way as described above when Gazell Device out of range this time. With the pca10028 (nrf51422) we do not have any problems using the very same firmware with only changed microcontroller type. On the other side we use for our Gazell Host the same NRF51822 without OS and it works just fine.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/47921?ContentTypeID=1Wed, 23 Mar 2016 07:24:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c2e4b360-593f-48f7-9673-8af72910acf7milen.icom<p>Up to now we were conducting these test with empty Device pairing database i.e. when it is erased and all set to 0xff. We tried the same tests after we have paired with Host and saved its ID data, so after restart the table to be not empty. It works stable this way, so the problem appears after initial programming and no pairing data saved before that in the Device.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/47920?ContentTypeID=1Mon, 21 Mar 2016 08:22:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:977c3129-f65b-444b-8432-5d8937e21d4amilen.icom<p>I will add new test results. We have left Gazell to work for extended period of few days also without OS (FreeRTOS) and after 24+ hours when Device makes endless scans for Host to pair with it freezes again. The same system with Gazell only initialized and started, but no Gazell API calls, with or without FreeRTOS works fine.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/47919?ContentTypeID=1Fri, 18 Mar 2016 13:45:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bc0d7712-f5bd-471c-a73a-fc5f410a8eb1milen.icom<p>We run just Gazell. In its dedicated task it runs like in the example code from the SDK - Gazell Device with Dynamic Pairing example. I forgot to mention that we run it only in encrypted mode with the settings same as in the SDK example, but however once the device is paired and in range all works without problems for hours.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/47918?ContentTypeID=1Fri, 18 Mar 2016 13:33:03 GMT137ad170-7792-4731-bb38-c0d22fbe4515:334a9f37-c206-4e90-bb8d-07594a19d014Anders Strand<p>Are you running Gazell and BLE concurrently, or just Gazell? (i.e do you have a softdevice?)</p><div style="clear:both;"></div>