Bluetooth on the WL500g? Yes!
We (Philips Semiconductors) are using the WL500g as test vehicle for our MIPS systems to verify code. During these exercises we ported the Affix Bluetooth stack to the WL500g. The actual code is too big to fit in the current firmware (above 4MB), so you need an external flash disk. Since also a USB Bluetooth dongle is needed, you need a compatible USB hub.
For more information go to:
Affix on WL500g
Please read the limitations:
- Binaries are statically compiled, so larger than actually needed.
- A specific libc.so.6 file is needed simply because the WL500g version is too limited
- PAN interface seems not to be routed through the WL500g. As a BT PAN client it is possible to access the internal webpage of the WL500g. When a tcpdump is made the box claims that “source route failed”. I have no clue yet what is causing this problem.
The last problem is causing me headaches. I haven't found a solution yet.
Last remark, the code is based on affix version 2.1.2 .
Status of bluetooth and QoS || New (possible) Idea?!
hi guys,
what is the status of this projects (http://wl500g.info/showthread.php?s=&threadid=212 and http://wl500g.info/showthread.php?s=&threadid=262)? it would be very nice if 500g start Gatekeeper (http://opengatekeeper.sourceforge.net/) from a usb-stick(or usb-hdd), and start a conection to your bluetooth phone(e.g.s60 phones) over the "audio gateway" profile.
the result is a mobile ip phone.
does everbody think that this is possible(for cpu of 500g and the other hardware)?:confused:
@oleg
thx a lot for all your hard work!did you already tought about donations?
1 Attachment(s)
Bluetooth for the WL500g Update
I noticed that the file you can download from my site causes "segmentation errors" with the latest version of Oleg's firmware. Therefore an update can be found on the page. Also, a very pleasant side-effect, libc has been replaced by ulibc in the package making it much smaller (still the wl500g build-in libc is not compatible with affix). In fact the /affix-release/lib directory only has to contain libc.so.6 since the binaries are compiled statically.
Attached you can find the new version.
PS can someone copy this to the wiki pages, I do not understand it how to use it, I am just a simple "ing" ;) .
Code:
It is possible to run Bluetooth on the WL500g! This can be done via
the USB interface in combination with a USB dongle running the Affix stack.
The following dongles have been tested:
* MSI
* 3COM
* TDK
For enabling Bluetooth on the WL500g the following is needed:
* a WL500g ;-)
* Precompiled binary, see attachement
* A USB flash disk
* A USB BT dongle
* A USB Hub (to be able to connect the USB BT & flashdisk simultaneously
to the WL500g)
Extract the affix-release.zip file and be sure to preserve the paths, it will
look as follows:
/affix-release
├───bin
│ └───kernel
│ ├───drivers
│ │ └───affix
│ └───net
│ └───affix
├───etc
│ ├───affix
│ ├───devfs
│ │ └───conf.d
│ ├───modutils
│ └───pcmcia
├───include
│ └───openobex
├───lib
├───share
│ └───aclocal
└───usr
└───include
└───affix
On the USB disk make a directory for incoming and outgoing Obex file transfer
files:
mkdir /incoming
Be shure to insert a USB BT dongle in the box and start bluetooth services via
telnet (see chupa forum how to enable telnet), by issuing the following
command:
/mnt/usbfs/affix-release/bin/start_bt
Everything should start up now. Test the affix stack by entering the following
command in a Telnet session:
btctl discovery
Known limitations:
* Binaries are statically compiled, so larger than actually needed.
* A specific libc.so.6 file is needed simply because the WL500g version is
too limited
* PAN interface seems not to be routed through the WL500g. As a BT PAN
client it is possible to access the internal webpage of the WL500g. When
a tcpdump is made the box claimes that “source route failed”. I have no
clue yet what is causing this problem
