Chettimada, Vinayak Kariappa
toggle quoted messageShow quoted text
Yes, we (for myself) are listening ;-)
You say beacon hex flashed to ble nano2 works (advertises).
1. Does hello world sample work (print out on UART)?
2. Does the samples/basic/blinky work (flash LED) ?
Lets proceed with these.
On 14 Sep 2017, at 21:03, Steve Brown <sbrown@...
Thu, 2017-09-14 at 14:49 -0300, Ricardo Salveti de Araujo wrote:
On Thu, Sep 14, 2017 at 5:53 AM, Steve Brown <sbrown@...>
for the info on the CMSIS firmware. I'm not using it, but
that it might be connected to my radio problem. From your
flashes the device with the expected console output.
radio doesn't work.
ordered another 2 from Digikey and will see how they behave. When
ordered them from Seeed, I never thought to check if they were
wonder if they got zapped during customs inspection. They probably x-
the small boxes. I hope the customs inspector wears a film badge.
anybody from Nordic is listening, maybe they have an opinion.
On Thu, 2017-09-14 at 01:47 -0300, Ricardo Salveti de Araujo wrote:
On Wed, Sep 13, 2017 at 6:37 PM, Steve Brown <sbrown@...
Has anyone had success with samples/bluetooth/beacon on this
Even the nitrogen_beacon.hex file from 96boards.org won't
console messages are as expected, but nothing on the air. Same
on two recent boards from Seeed.
The same .hex file flashed to a redbear ble nano2 does
is no console output because a different uart is used, but the
are on the air.
The designation on the nRF52 is N52832/QFAAB0/1616BD. I looked
errata and didn't see anything obvious.
It is supposed to just work, without any additional changes, so
if this could be hw issues.
Can you check the hw revision for your Nitrogens (should be
v0.9, v1.0 or v1.1)?
I got several from v0.9 and v1.1 and they are all functional.
tested the beacon sample from Zephyr 1.9 and it is working just
The boards are:
v1.0 build date 09/19/2016
v1.1 build date 02/16/2017
The nitrogen build uses pyOCD to flash the device. This works as
By works as expected you mean including the BT radio?
However, copying a .bin file to /media/$USER/MBED gives the
"The interface firmware FAILED to parse the hex file" in FAIL.TXT
If I copy a .hex file to the MBED disk, it isn't processed and the
remains in the folder.
Both boards exhibit identical behavior.
Yeah, this looks like an issue in the firmware flashed in LPC11U35.
Talking with Seeeds, it seems they originally flashed
https://github.com/xiongyihui/CMSIS-DAP/tree/arch_ble, but I didn't
yet investigate to see why this is currently broken. Maybe it assumes
the user will flash softdevice compatible fw by default, not sure.