Will,
Thank you for the kick in the right direction. I miss that
disabled->txen shortcut exists, will dig it tomorrow (my day is
finished, I need to go).
Can't show you 'newt target' output since we use GNUmake instead of newt
build. Go is too exotic for our embedded team) Even python-based SCons
is more comfortable than Go. Sorry.
Thank you for your help.
BR,
Andrey
On 11.04.2017 17:46, will sanfilippo wrote:
Andrey:
The PHY code does not write directly to TASKS_TXEN; it uses shortcuts to
automatically start transmissions.
Can you show me the target you are using? Just paste the output of: newt target show
<your_target_name>
We test regularly with the nrf51 but that does not mean that a particular
commit in time may have issues. I will give it a try in a bit (well, I just
woke up so it might be an hour or so) :-)
On Apr 11, 2017, at 7:36 AM, Andrey Serdtsev <[email protected]>
wrote:
Hi there.
Would like to know if someone ever test nimble on nRF51? There is a mynewt port
for nRF51DK but I fail to make it work.
It looks like that nRF51 BLE Tx code is broken. I tried to add gdb watchpoint to
address 0x40001000 (where NRF_RADIO->TASKS_TXEN mapped): it never hits, i.e, Tx
is never started and I can't see my advertising packets.
I use code from master branch, starting from here:
commit a7b80beee894584c6b32d90e925518784f375504
Author: Marko Kiiskila <[email protected]>
Date: Wed Mar 22 11:40:39 2017 -0700
repository.yml; add 1.0.0 tag
I don't see similar problems in mailing list. Either nobody tried nRF51 before
or I'm doing something wrong. Any suggestions?
Many thanks.
BR,
Andrey
