Timer conflict(?) between UNO and nRF8001

RE: Timer conflict(?) between UNO and nRF8001

TreasureHunter — Tue, 10 May 2016 13:46:21 GMT

I have no clue :(

RE: Timer conflict(?) between UNO and nRF8001

run_ar — Tue, 10 May 2016 06:03:19 GMT

And for furter debugging, you could try to add some delays, as the serial interface is quite slow, you might get past sei() even if it looks like you don't. I would guess you are failing in BTLEserial.begin() as this is essentially the only change in the setup part of your code, compared to the version without ble???

RE: Timer conflict(?) between UNO and nRF8001

run_ar — Tue, 10 May 2016 05:45:39 GMT

Could you check that you are not doing something strange when configuring your interrupts? As far as I can see, the adafruit library is a bit different from the nordic library (which means I'm not sure exactly what they are doing...), maybe you should check the way they configure interrupts in hal_aci_tl.

RE: Timer conflict(?) between UNO and nRF8001

TreasureHunter — Mon, 09 May 2016 14:05:16 GMT

I tried the tutorial code again, it works fine, I then tried the code in the "pastebin" again, nothing.. I put a Serial.print("TEST"); before cli() in setup() stage, and put Serial.print("TEST1"); after sei().

The result was: a "T" appeared in the serial monitor, nothing more.. so the problem must be between cli() and sei() with those registers or something.. I don't get it..

RE: Timer conflict(?) between UNO and nRF8001

Wojtek — Mon, 09 May 2016 13:55:59 GMT

I have heared about the bug that is somehow connected with newest IDE. As other people were saying (i have not experienced that by myself! maybe because i am not using arduino at all.) program may be stuck when you have USB cable plugged in board and serial monitor is closed. Could you try restarting serial monitor?

RE: Timer conflict(?) between UNO and nRF8001

TreasureHunter — Mon, 09 May 2016 13:50:00 GMT

When I run the program, it doesn't even reach the loop() cycle, because the serial.print("TEST3") doesn't print out at the beginning. I though it's a timer problem because nRF8001 uses a clock at SCK pin, so I though it needs a timer of some sort.

I call BTLEserial.write in the end of the code, but we doesn't reach that, because it doesn't even starts to advertise.

RE: Timer conflict(?) between UNO and nRF8001

run_ar — Mon, 09 May 2016 13:05:52 GMT

As far as I can see the adafruite library isn't using any timer. Why do you suspect that this is a timer conflict?

RE: Timer conflict(?) between UNO and nRF8001

run_ar — Mon, 09 May 2016 12:39:12 GMT

Are you getting any indications why it is not working? Is BTLEserial.write called? what is returned from BTLEserial.write? etc...