On Thu, 2017-09-14 at 19:14 +0000, Chettimada, Vinayak Kariappa wrote:
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 <email@example.com> wrote:
On Thu, 2017-09-14 at 14:49 -0300, Ricardo Salveti de Araujo wrote:
On Thu, Sep 14, 2017 at 5:53 AM, Steve Brown <firstname.lastname@example.orgThanks for the info on the CMSIS firmware. I'm not using it, but
Richardo,By works as expected you mean including the BT radio?
On Thu, 2017-09-14 at 01:47 -0300, Ricardo Salveti de Araujo
On Wed, Sep 13, 2017 at 6:37 PM, Steve Brown <sbrown@cortlandThe boards are:
Has anyone had success with samples/bluetooth/beacon onIt is supposed to just work, without any additional changes,
Even the nitrogen_beacon.hex file from 96boards.org won't
console messages are as expected, but nothing on the air.
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
are on the air.
The designation on the nRF52 is N52832/QFAAB0/1616BD. I
errata and didn't see anything obvious.
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
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
However, copying a .bin file to /media/$USER/MBED gives theYeah, this looks like an issue in the firmware flashed in
"The interface firmware FAILED to parse the hex file" in
If I copy a .hex file to the MBED disk, it isn't processed and
remains in the folder.
Both boards exhibit identical behavior.
Talking with Seeeds, it seems they originally flashed
https://github.com/xiongyihui/CMSIS-DAP/tree/arch_ble, but I
yet investigate to see why this is currently broken. Maybe it
the user will flash softdevice compatible fw by default, not
thought that it might be connected to my radio problem. From your
comments, it's not.
pyocd-flashtool flashes the device with the expected console
The radio doesn't work.
I've ordered another 2 from Digikey and will see how they behave.
I ordered them from Seeed, I never thought to check if they were
I wonder if they got zapped during customs inspection. They
ray the small boxes. I hope the customs inspector wears a film
If anybody from Nordic is listening, maybe they have an opinion.
Zephyr-users mailing list
Hello and blinky work. BT does not.
And, yes nitrogen_beacon.hex from http://builds.96boards.org/releases/n
itrogen/zephyr-1.8/ flashed to the nano2 advertises. There's no console
output as I explained previously.
I'm now more convinced that the devices somehow got damaged in transit
I'll report when I get the ones I ordered from Digikey. I expect them
to work just fine.
If you are curious about what happened to the radios, I'd be glad to
send you the 2 I got from Seeed.
The shipment didn't seem to have been opened. I'm pretty ESD conscious
at my end.