No need to apologize; but even the kick in the right direction should not address your issue. I just built a test program (bletest) which does advertising and it is advertising fine on the nrf51. If you cannot share your target, what app are you building?
Assuming you have statistics enabled you can take a look at the phy stats and LL stats. You can use the console to display them (if you are building with that) or you can halt in the debugger and look at the following variables: p ble_phy_stats p ble_ll_stats If they are hard to interpret, paste them and send them to us and we will decipher. PS: I will say this though (just my opinion): the newt tool and build and package management system simply blows away a makefile any day of the week, and twice on Sunday! > On Apr 11, 2017, at 8:17 AM, Andrey Serdtsev > <andrey.serdt...@yotadevices.com> wrote: > > 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 >>> <andrey.serdt...@yotadevices.com> 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 <ma...@runtime.io> >>> 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 >>> >
