[Matt Brown]

I think that’s what I was doing but it seems something must be different!

If/when I switch back to looking at the Dot-Examples I check what I was doing and let you know more details if it is still happening.

[Matt Brown]

FYI, I moved on to experimenting with the Dot-Examples and they worked.

So I don’t know if there is something wrong with the AT command interface or my fingers but I don’t care because I’m not planning on using the AT command interface for our product (it was just the first thing I tried with my new xDot).

[Matt Brown]

static bool deep_sleep = false;

It says “sleeping 10s” but then nothing happens even if I wait much longer than 10 s; no debug messages and no activity on TTN.

If I press the button it transmits so the interrupt is working.

sleep_wake_rtc_or_interrupt(deep_sleep); yes.

I switched to the stable library (and mbed 5.4 and gcc 4.9) and it worked as I think you would expect, i.e. transmitted every 10 s.

Matt

[Matt Brown]

I have now.

I downloaded Arm GCC 4.9 from launchpad, it took me a while to find it. I went for 2015 Q3 update.

https://launchpad.net/gcc-arm-embedded/4.9

Now I can link.

Thanks,
Matt

[Matt Brown]

I’ve also tried to build Dot-Examples using GCC ARM, although I’m building OTA_EXAMPLE rather than AUTO_OTA_EXAMPLE.

The first undefined reference I see is mDot::getReturnCodeString.

Initially I was using ‘6 2017-q2-update’, which was installed by Mbed CLI. But, I’ve also tried ‘7 2017-q4-major’.

I changed to the online compiler but would much rather be using the CLI and ARM GCC.

HTH,
Matt

[Matt Brown]

It appears that joining the network isn’t as easy as I first thought.

I didn’t notice the first time but while messing around this morning I’ve discovered that at+join always fails on the first attempt after a reset and I always have to do at+join twice.

Matt

[Author]

Posts