Yes it it is WiLink8 on-chip RAM that is a hardware limit.
I didn't write the documentation so this is my interpretation.
- The mesh can contain up to 32 nodes in the entire network. My guess is
that this is a limitation in the open80211 software for the number of nodes
that can be kept track
Hi,
The limit is in the RAM on the WiLink8. There is only enough to hold the
state information for 10 connections.
The 11th connection will just fail.
Iain
On Friday, April 5, 2019 at 3:25:46 PM UTC+1, don_wrt wrote:
>
> Dear All,
>
> At most how many beaglebone black wireless modules have you
Neil,
Its not clear from your message if the example you refer to is working or
not.
Are you asking for help in getting the example to work on BBBW or just how
to write serial data?
If it is just getting serial comms working then I'd suggest you look at the
source for the TI Linux side
Hi,
I'm wondering if anyone has experience/recommendations for getting a custom
case made for a BBG + cape. I need cut outs for the USB + ethernet at one
end and some 4mm sockets from the cape at the other.
Not sure whether to try custom case or off the shelf case and adjust cape
to mount in an
Chris,
I've used the E14 cape on multiple customer projects. They have been both
debian based and TI SDK based. From memory its just been a case of picking
up the correct dtb file in u-boot. I've never touch the CC device on it
though as I've just needed Wi-Fi and/or Bluetooth.
I can't imagine
To add a little bit of background to this;
There are several posts on TI's e2e forum stating that ad-hoc mode is no
longer supported. In TI's use cases ad-hoc was replaced by Wi-Fi Direct.
http://e2e.ti.com/support/wireless-connectivity/wifi/f/968/t/367550
TI supported 802.11s meshing
There is no support for ad-hoc mode in the wl18xx driver. It was dropped
several years ago.
Iain
On Wednesday, January 23, 2019 at 2:25:21 PM UTC, M I Syed wrote:
>
> I am working on a project where I have to build a mesh (ad-hoc network). I
> have few Beaglebone Black Wireless for that but
At first glance I would say yes. The BBBW uses mmc2 (mmc3 in device tree)
for its on board interface to WL183x and the Stream unlimited cape uses
mmc1 (mmc2 in device tree). The GPIOs don't seem to clash either.
You can get the Stream Unlimited device tree details
from
Hi Matthew,
My comments here are based on WL18xx experience rather than BBBW
specifically.
For WL18xx to stay active while the host (AM335x) is suspended the WL_EN
pin needs to be kept high. However if I look at
am335x-boneblack-wl1835.dtsi (from 4.9.88-ti-rt-r107 which I happened to
have) I
Hi WenZhan,
The only access you have to the Bluetooth inside the WL183x device is via
an HCI interface over UART. There is no specification I am aware of that
would allow you to infer time of Rx/Tx at the bluetooth physical layer from
the time the HCI interface delivers information.
If you
In principle the answer is yes.
- first question would be to ask which board with WL18xxMOD on it you would
be planning to connect.
- you would need to use the SPI mode of the WL18xxMOD as there is no space
MMC interface on the pocket beagle. This is normally built with
CONFIG_WLCORE_SPI to
Hi,
Do you have wifi enabled and are you using it? The most likely explanation
is that the antenna is shared between the Wifi and BLE radios. So when it
is busy doing wifi it cannot be listening on BLE for advertisements. As the
WL18xx does not know when advertisements will be taking place it
Thanks for your comments. I have today tracked the paging problem down to a
need to flush the TLBs before enabling the MMU. This was done via the
TLBIALLH.
At the moment I've done in in xen head.s but maybe better to be done as
part of u-boot as it seems to be an AM57xx uboot problem rather
Hi,
I am trying to get xen hypervisor to run on an X15 but I have a prefetch
abort when the first instruction at a virtual address is fetched. The
paging tables appear to be being setup correctly.
I am using u-boot v2017.01 to boot the xen image. u-boot by default is in
hypervisor mode with
Hi Alek,
I think you need more than a 1A supply. I use one of these
https://www.amazon.co.uk/Charger-RAVPower-4-Port-Charge-Smartphones-White/dp/B018Q7HNRQ/ref=sr_1_4
to power 4 BBGWs.
I suspect the board is suffering a brown out when the WL1835 does its short
calibration (a couple of ms but at
Hi,
There is no open source support of WiLink8 drivers in anything apart from
Linux. So quick answer is no.
If you are looking for a commercial port to an RTOS you could try
www.clarinox.com. They have typically ported to ARM cortex-M devices so
they may have nothing to run on BBB in FreeRTOS.
Hi Trinadh,
This is not actually an ERROR, it should be a warning as the WL18xx driver
will create a default configuration and use it instead. So it is probably
not the cause of your failure to boot.
Having said that using the wl18xx-conf.bin that Robert pointed you to in
your filesystem is
In 3.02.00.05 it is u-boot.img so that is correct.
I'd recommend an FTDI TTL uart cable to debug this so that you can see if
uboot is actually being loaded in a terminal.
Are you pressing switch S2 when you insert power to force the boot from SD
card?
Iain
On Tuesday, 30 May 2017 14:54:20
Hi Benjamin,
First some background before we go into the details.
There are two types of wilink8 driver deliveries
- TI driver release. R8.7 is the latest. This is the full feature driver
release that includes all features including mesh. It is built via the
build script at the link you
Hi Stephane,
Yes WL18xx does have a power save mode which is on by default. It can be
disabled with
echo 0 > /sys/kernel/debug/ieee80211/phy0/wlcore/sleep_auth
The SW interrupt message means that the linux driver did not get a response
from the WL18xx firmware within a defined time and so
Hi,
Is there a page documenting the BBGW build process? I'm assuming
https://eewiki.net/display/linuxonarm/BeagleBone+Black does not cover it as
BBGW is not listed as an available board.
Thanks, Iain
--
For more options, visit http://beagleboard.org/discuss
---
You received this message
There is a TI reference design for 4-20mA loop
interfaces http://www.ti.com/tool/tida-00550. It is designed as a cape.
Iain
On Thursday, August 18, 2016 at 4:24:45 PM UTC+1, Graham wrote:
>
> If you would think to Google "4-20 mA receiver" you could learn a lot.
>
> Peripheral IC's from TI and
Hi Juliusz,
As far as the wl1835 driver is concerned it has MIMO enabled.
It is defined in the file /lib/firmware/ti-connectivity/wl18xx-conf.bin in
the entry wl18xx.phy.number_of_assembled_ant2_4 = 0x02.
You can inspect the contents of this file with
#wlconf -i
I missed your USB question.
If you don't have enough power from USB for the Wi-Fi calibration you will
get a driver timeout just after initialisation.
I use a 2.1A powered Hub for my BBGW having seen failures on other
"supplies".
Iain
On Tuesday, August 2, 2016 at 6:00:35 PM UTC+1,
I suspect this is due to concurrent Wi-Fi activity. On the BBGW the antenna is
shared by Wi-Fi and Bluetooth. So if it is doing Wi-Fi it can't be scanning
Bluetooth.
If you can, can you disable Wi-Fi and see if it improves behaviour.
Iain
--
For more options, visit
If you are looking for the TI WL18xx family then there are capes with it
which are integrated into Robert Nelson's build. However, the only one you
can buy today is from StreamUnlimited
(http://streamunlimited.com/products/wifiaudiocape.html). This is quite
expensive though as it is a
Hi,
I think it must be the ubuntu fs change that is causing the problem. I have
just rerun the script as is with debian 8.1 with
BBB_KERNEL_TAG=4.2.5-bone2
and it boots fine.
As some background the -12 error is out of memory but it is also used by
the wlcore driver when it cannot parse the
Hi,
Which wilink device are you building for?
The wl18xx family is now fully supported in 4.1 kernel. There is a device tree
file for the wl1835 cape in the kernel that is best place to look.
If you are looking at wl127x or wl128x then device tree will be similar but
you'll need to build the
Robert,
I now have the console image working with usb over ethernet with both Linux
and Windows PCs.
The change I had to make was to remove udhcpd and its conf files and then
install dnsmasq
#apt-get remove udhcpd
#rm /etc/default/udhcp*
#apt-get install dnsmasq
#reboot
This change then
Hi,
I have created SD card images from the June 29th debian 8.1 images for both
console and lxqt.
With the lxqt image I was successfully getting a linux machine to create an
new interface eth1with address 192.168.7.1 when USB was connected.
I know that the console image is stripped down and
30 matches
Mail list logo
