|
Re: IPSP bluetooth sample with QEMU (ping fails)
Hello Priyanka,
Priyanka Rawat <priyanka.rawat@...> wrote:
I tested it on BOARD=96b_carbon (real hardware) straight before 1.9
release, everything worked well, and I captured docs required to
Hello Priyanka,
Priyanka Rawat <priyanka.rawat@...> wrote:
I tested it on BOARD=96b_carbon (real hardware) straight before 1.9
release, everything worked well, and I captured docs required to
|
By
Paul Sokolovsky
·
#183
·
|
|
Re: Testing Bluetooth with QEMU
Hi Paul
Yes, first I did use "make run".
In the Zephyr's application console QEMU :
-------------------------------------------------------------
Bluetooth gets initialized and Beacon started. All
Hi Paul
Yes, first I did use "make run".
In the Zephyr's application console QEMU :
-------------------------------------------------------------
Bluetooth gets initialized and Beacon started. All
|
By
Priyanka
·
#182
·
|
|
IPSP bluetooth sample with QEMU (ping fails)
Hi
While testing bluetooth IPSP sample (recent master branch of zephyr) with Qemu, ping fails (no response found) and
ping: sendmsg: No buffer space available (wireshark capture attached).
I noticed
Hi
While testing bluetooth IPSP sample (recent master branch of zephyr) with Qemu, ping fails (no response found) and
ping: sendmsg: No buffer space available (wireshark capture attached).
I noticed
|
By
Priyanka
·
#181
·
|
|
Re: Testing Bluetooth with QEMU
Hello Priyanka,
By
Paul Sokolovsky
·
#180
·
|
|
Re: Testing Bluetooth with QEMU
Hi Priyanka,
I don't get this error when using a real controller:
Starting Beacon Demo
[bt] [INF] show_dev_info: Identity: 00:1b:dc:07:31:88 (public)
[bt] [INF] show_dev_info: HCI: version 4.0
Hi Priyanka,
I don't get this error when using a real controller:
Starting Beacon Demo
[bt] [INF] show_dev_info: Identity: 00:1b:dc:07:31:88 (public)
[bt] [INF] show_dev_info: HCI: version 4.0
|
By
Luiz Augusto von Dentz
·
#179
·
|
|
Re: 96boards Nitrogen
Hi Vanayak,
I've got some more information.
I converted the SDK's radio_test to run on both the nano2 and the
nitrogen.
The nano2 is transmitting continuous carrier (test "c") on 2402 and
Hi Vanayak,
I've got some more information.
I converted the SDK's radio_test to run on both the nano2 and the
nitrogen.
The nano2 is transmitting continuous carrier (test "c") on 2402 and
|
By
Steve Brown
·
#178
·
|
|
Testing Bluetooth with QEMU
Hi
I am testing samples/bluetooth/beacon with QEMU.
The version of zephyr is recent master branch.
1)
The beacon sample test with local Bluetooth adapter on Linux PC, gives the init failed
Hi
I am testing samples/bluetooth/beacon with QEMU.
The version of zephyr is recent master branch.
1)
The beacon sample test with local Bluetooth adapter on Linux PC, gives the init failed
|
By
Priyanka
·
#177
·
|
|
Re: 96boards Nitrogen
Vinayak,
The identity address is persistent across power resets.
I'll report on the behavior of the 2 units arriving this week. If they
also show compatibility issues, I'll continue to
Vinayak,
The identity address is persistent across power resets.
I'll report on the behavior of the 2 units arriving this week. If they
also show compatibility issues, I'll continue to
|
By
Steve Brown
·
#176
·
|
|
Re: 96boards Nitrogen
Hi Steve,
Good. You have clarified that indeed radio h/w is live and kicking.
May be something around the antenna matching is bad that only some peer see the transmissions.
I can be suspicious that
Hi Steve,
Good. You have clarified that indeed radio h/w is live and kicking.
May be something around the antenna matching is bad that only some peer see the transmissions.
I can be suspicious that
|
By
Vinayak Kariappa
·
#175
·
|
|
Re: 96boards Nitrogen
More
These tests were run using tests/bluetooth/shell.
I found and fired up an ubertooth. The 3 advertising freqs are spot on.
Whatever is on the air isn't decoded by ubertooth-btle or bluez w/
More
These tests were run using tests/bluetooth/shell.
I found and fired up an ubertooth. The 3 advertising freqs are spot on.
Whatever is on the air isn't decoded by ubertooth-btle or bluez w/
|
By
Steve Brown
·
#174
·
|
|
Re: TCP assert error logs
Hello Vakul,
By
Paul Sokolovsky
·
#173
·
|
|
Re: 96boards Nitrogen
Vinayak,
I found tests/bluetooth/shell. I also found my wispy toy spec analyzer.
With "scan on", I receive advertisements. So, the 32Mhz xtal is ok.
With "advertise on", I observe rf on 3 freq's.
Vinayak,
I found tests/bluetooth/shell. I also found my wispy toy spec analyzer.
With "scan on", I receive advertisements. So, the 32Mhz xtal is ok.
With "advertise on", I observe rf on 3 freq's.
|
By
Steve Brown
·
#172
·
|
|
Re: 96boards Nitrogen
Ok, so the CPU and UART works :-)
And, the 32KHz clock domain works, hence the blinks.
Now, CPU can run from internal High Frequency RC or External crystal.
If your 32MHz crystal on the board has dry
Ok, so the CPU and UART works :-)
And, the 32KHz clock domain works, hence the blinks.
Now, CPU can run from internal High Frequency RC or External crystal.
If your 32MHz crystal on the board has dry
|
By
Chettimada, Vinayak Kariappa
·
#171
·
|
|
Re: 96boards Nitrogen
Hi Vinayak,
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
Hi Vinayak,
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
|
By
Steve Brown
·
#170
·
|
|
Re: 96boards Nitrogen
Hi Steve,
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
Hi Steve,
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
|
By
Chettimada, Vinayak Kariappa
·
#169
·
|
|
Re: 96boards Nitrogen
Ricardo,
Thanks for the info on the CMSIS firmware. I'm not using it, but
thought that it might be connected to my radio problem. From your
comments, it's not.
pyocd-flashtool flashes the device
Ricardo,
Thanks for the info on the CMSIS firmware. I'm not using it, but
thought that it might be connected to my radio problem. From your
comments, it's not.
pyocd-flashtool flashes the device
|
By
Steve Brown
·
#168
·
|
|
Re: 96boards Nitrogen
By works as expected you mean including the BT radio?
Yeah, this looks like an issue in the firmware flashed in LPC11U35.
Talking with Seeeds, it seems they originally
By works as expected you mean including the BT radio?
Yeah, this looks like an issue in the firmware flashed in LPC11U35.
Talking with Seeeds, it seems they originally
|
By
Ricardo Salveti de Araujo <ricardo.salveti@...>
·
#167
·
|
|
Re: 96boards Nitrogen
Richardo,
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
expected. However, copying a .bin file to
Richardo,
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
expected. However, copying a .bin file to
|
By
Steve Brown
·
#166
·
|
|
Re: TCP assert error logs
Hi Paul
By
Vakul Garg <vakul.garg@...>
·
#165
·
|
|
Re: 96boards Nitrogen
It is supposed to just work, without any additional changes, so wonder
if this could be hw issues.
Can you check the hw revision for your Nitrogens (should be either
v0.9, v1.0 or v1.1)?
I got
It is supposed to just work, without any additional changes, so wonder
if this could be hw issues.
Can you check the hw revision for your Nitrogens (should be either
v0.9, v1.0 or v1.1)?
I got
|
By
Ricardo Salveti de Araujo <ricardo.salveti@...>
·
#164
·
|