<w|zzy>
wpwrak: Ive used the broadcom WICED platform.
<w|zzy>
Hardest part was getting a dev board in AU
wolfspraul has joined #qi-hardware
<wpwrak>
w|zzy: and how was the experience ? which module did you use ?
<w|zzy>
BCMUSI11 : USI 43362-based WICED+ Module (STM32F205 MCU, 8Mbit serial flash) mounted on BCM9WCD1MFI1
<w|zzy>
Thats the platform i am using. One of the early dev boards..
<w|zzy>
Its a very easy build environment. The provide everything needed to compiler/upload (and also the source and instructions if you want to compile yourself) so that there are no issues with the build env
<w|zzy>
Code is pretty neat and easy to follow.
<w|zzy>
Plenty of neat little examples.
<wpwrak>
i have an USI board with a WM-N-BM-08. i think it should be very similar to your board then.
<wpwrak>
(neat code) that sounds encouraging :)
<w|zzy>
You haven't got the SDK yet?
<wpwrak>
i have it but haven't done anything with it besides having a very quick look. tried to build something for my board but of course the build didn't even accept my configuration.
<w|zzy>
The SDK is up to 2.3.1
<w|zzy>
I dislike how they authorise access to the SDK.. Its cookie based or something silly.
<w|zzy>
anyway thats not important.
<w|zzy>
build system is pretty easy
<w|zzy>
1sbrb
<w|zzy>
make demo.temp_control-BCMUSI11 download run
<w|zzy>
So.. it looks in the Apps folder for the demo folder, then the temp_control folder
<w|zzy>
and compiles for a BCMUSI11 board
<w|zzy>
then download and run
<wpwrak>
i have version 2.3.0. doesn't like that command
<w|zzy>
hardest part is working out which board you have.
<wpwrak>
oh wait ... now i see it. it's ./make, not "make". argh.
<w|zzy>
you have to use make from inside the folder.
<wpwrak>
my board ought to be BCM9WCDUSI09
<wpwrak>
(if it's any of them at all)
<w|zzy>
I should note that my wifes cousin developed half of the SDK.
<w|zzy>
if you have any queries i can ask.
<w|zzy>
you can just try
<w|zzy>
the platforms are in the readme file
<wpwrak>
seems to work ;)
<w|zzy>
The appliance demo is pretty good.
<wpwrak>
now ..to see what it's doing ...
<w|zzy>
Indeed. You can specify which rtos to use.. or go raw...
<wpwrak>
seems that it defaults to ThreadX
<w|zzy>
they bought ThreadX and NetX for people to use with their wireless platform.
<w|zzy>
Yeah.
<w|zzy>
I should say they bought a license to cover the use of ThreadX and NetX..
<wpwrak>
the less closed the better :) so i'll try my luck with freertos.
<w|zzy>
how to change that is specified in the makefile
<wpwrak>
but first i need to see if i can get a serial console. i suppose it reports things there ?
<w|zzy>
Its a fairly nice build system
<w|zzy>
Yeah
<w|zzy>
115200 8N1
<wpwrak>
yeah, i just have to build the right magic config string
<w|zzy>
snip/config_mode is pretty cool.
<wpwrak>
i found the instructions once, i'll find them again :)
<w|zzy>
make demo.temp_control-BCMUSI11-FreeRTOS-LwIP download run
<w|zzy>
Also.... Everything gets built in the SDK/build directory.
<w|zzy>
Also.. There is an image for the wireless chip itself that is store in the chip rom.. It is possible to load that into an eeprom or such.
<wpwrak>
kewl. wlan scan is running. picks up half the city even without an antenna ;-))
<w|zzy>
:)
<w|zzy>
Any ideas what you will use it for?
<w|zzy>
Does your board have the current IC?
<wpwrak>
what's the current IC ?
<wpwrak>
the plan is to use this for a wpan-wlan gateway
<wpwrak>
demo.temp_control doesn't seem to do anything
<wpwrak>
or maybe it doesn't like freertos
<wpwrak>
let's try config_mode
<wpwrak>
ah, pilot error :)
<w|zzy>
you have the serial port happening?
<wpwrak>
i had copied your config string without changing it to my board :)
<w|zzy>
btw cosm doesn't exist any more.. so it won't work..
<w|zzy>
compile appliance...
<w|zzy>
Its more interesting.
<w|zzy>
xively replaced cosm...
<w|zzy>
also.. the downside of the current license is you can't publish our share it... I know the developers are pushing to make it more accessible.
<wpwrak>
yeah, the license is very bad
<wpwrak>
hmm, running snip.config_mode but it doens't let me associate
<wpwrak>
ah, now
unclouded has joined #qi-hardware
<w|zzy>
:-)
<wpwrak>
kewl. the critter works :)
<wpwrak>
apparently, the 43362 is a simplified 4330. so perhaps one could get the linux driver to talk to it.
<w|zzy>
perhaps...
<w|zzy>
not my domain
<wpwrak>
but very much mine :)
<w|zzy>
if you do let me know.. they could hook it in with the picture
<w|zzy>
pi
arossdotme has quit [Ping timeout: 246 seconds]
wolfspraul has quit [Quit: leaving]
<w|zzy>
All figured out wpwrak ?
<wpwrak>
all i had hoped for, at least for today :) thanks a lot !
unclouded has quit [Ping timeout: 245 seconds]
<wpwrak>
i think the next step will be to map the i/os. USI call them just "GPIO_n", "SPI", etc., without mentioning which of the many units of the same kind this refers to
<wpwrak>
maybe it's somewhere in the sources. at least the U(S)ART should be.
ffio has joined #qi-hardware
wolfspraul has joined #qi-hardware
jekhor has joined #qi-hardware
ffio has quit [Quit: WeeChat 0.4.1]
kuribas has joined #qi-hardware
wej has joined #qi-hardware
mth has quit []
viric has quit [Remote host closed the connection]
viric has joined #qi-hardware
viric_ has joined #qi-hardware
viric has quit [Ping timeout: 240 seconds]
viric_ is now known as viric
mth has joined #qi-hardware
jekhor has quit [Ping timeout: 248 seconds]
jekhor has joined #qi-hardware
viric has quit [Remote host closed the connection]
viric_ has joined #qi-hardware
viric_ is now known as viric
wej has quit [Ping timeout: 245 seconds]
wolfspraul has quit [Quit: leaving]
wej has joined #qi-hardware
w|zzy_ has joined #qi-hardware
w|zzy has quit [Ping timeout: 248 seconds]
panda|x201 has quit [Ping timeout: 240 seconds]
rodgort` has quit [*.net *.split]
qi-bot has quit [*.net *.split]
w|zzy_ has joined #qi-hardware
w|zzy_ has quit [Changing host]
qi-bot has joined #qi-hardware
rodgort` has joined #qi-hardware
lekernel has joined #qi-hardware
jekhor has quit [Read error: Connection reset by peer]
sivoais has quit [Ping timeout: 264 seconds]
sivoais has joined #qi-hardware
viric has quit [Ping timeout: 240 seconds]
ffio has joined #qi-hardware
w|zzy_ is now known as w|xyz
panda|x201 has joined #qi-hardware
w|xyz is now known as w|zzy
panda|x201 has quit [Ping timeout: 256 seconds]
rz2k has joined #qi-hardware
ffio has quit [Quit: WeeChat 0.4.1]
wej_ has joined #qi-hardware
wej has quit [Ping timeout: 248 seconds]
jekhor has joined #qi-hardware
LunaVorax has joined #qi-hardware
LunaVorax has quit [Ping timeout: 256 seconds]
bikepunk-Work has joined #qi-hardware
Freemor has left #qi-hardware [#qi-hardware]
wolfspraul has joined #qi-hardware
Freemor has joined #qi-hardware
arossdotme has joined #qi-hardware
Jurting_pc2 has joined #qi-hardware
ffio has joined #qi-hardware
viric has joined #qi-hardware
newcup has quit [Read error: Operation timed out]
ffio has quit [Quit: WeeChat 0.4.1]
FDCX has quit [Quit: Leaving]
FDCX has joined #qi-hardware
<arossdotme>
wpwrak: regarding my NN charging problems. it does charge but very very slowly. Though I have had it powder on while charging so it could log the bat voltage and some time powdered off. It's been 2-3days after getting it to red, 3.5v If I remember correctly. its now 3.984
<arossdotme>
whitequark:
<viric>
lekernel: reminded me of kickstarter ;) Is kamikaze the older release of openwrt?
<arossdotme>
Could any of charging circuit components get fried if they get 6vish? Didn't see any component doc on the wiki. Haven't open up & probed my NN yet btw.
LunaVorax has joined #qi-hardware
<lekernel>
viric, bookmarked. will print and hang out at next ehsm.
<viric>
lekernel: great! I think it's very descriptive