Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
cladamw has joined #qi-hardware
xiangfu has joined #qi-hardware
orson_zhai has joined #qi-hardware
wolfspraul has joined #qi-hardware
<unclouded>
xiangfu: is there any source material for the Ben character printed on to outside of the NanoNote case?
orson_zhai has quit [#qi-hardware]
<xiangfu>
unclouded, yes. I also try to find out that one. then will let you know.
<unclouded>
xiangfu: thanks. So is the character I used slightly different then?
<whitequark>
DocScrutinizer51: as you're now into that modem stuff, can you enlighten me...
<whitequark>
I ran `strings' (and IDA, but that was less interesting) on modem firmware, and it looks like it's some 20 year old codebase from ten different companies including stericsson, siemens, someone bought by intel and more
<whitequark>
all loosely screwed together and patched three times in a row
<whitequark>
(on Samsung Galaxy SII modem fw)
<DocScrutinizer51>
ooops 5780 inside, not 5730
<viric>
xiangfu: ah ok :)
<viric>
DocScrutinizer51: what's good in a 5730?
<viric>
or 5780
<DocScrutinizer51>
the fact that I know it 'from inside' :)
<viric>
ahh
<DocScrutinizer51>
actually I'm the one working on the tickets against this modem here
wolfspraul has joined #qi-hardware
ab5tract has joined #qi-hardware
rejon has joined #qi-hardware
Ayla has joined #qi-hardware
LunaVorax has joined #qi-hardware
LunaVorax has joined #qi-hardware
wolfspra1l has joined #qi-hardware
<jivs>
Hi
<rz2k>
whitequark: you and grindars published any info about that coding horror on #xda-devs or #cyanogenmod channels/forums? wonder if anyone did same to sgs2 modem.
<jivs>
trying to get dirtpan working with the latest qi-image
<jivs>
the izcoordinator seems to run fine, but when i run iz assoc with another ben, there is no resonse
<jivs>
can anyone here plz help to debug the problem
<wpwrak>
does dmesg reveal anything ?
<jivs>
it doesn;t load spi_atben.ko, so i am manually doing insmod
<jivs>
after that it says spi_atben is ready for mischief
<jivs>
is there anything else i could check
<wpwrak>
hmm, with spi_atben not loaded, you could check whether communication works at all - by using the tools from ben-wpan
<wpwrak>
and the at86rf230 driver is compiled as a module ? if yes, it seems that you didn't load it. but then i don't understand where your wpan-phy0 comes from
<jivs>
wpan-phy0 might be coming from fakehard as well
<wpwrak>
(mmc driver) hmm yes, it should spit out some errors because it can't figure out what to do with atben
<jivs>
didn;t give any error for me
<wpwrak>
i'd get rid of fakehard. it can only make things worse :)
<jivs>
at86rf230 driver will be displayed on lsmod?
<wpwrak>
assuming it's a module, yes. does dmesg | grep -i rf23 show anything ?
<jivs>
i doubt i have at86rf230
<jivs>
nothing
<wpwrak>
then there's very little reason for atben to do more than sit there, looking pretty ;-)
<wpwrak>
but you also have to get rid of the conflicting drivers. anything else that uses MMC will clash.
urandom__ has joined #qi-hardware
<jivs>
lsmod has mmc_spi
<wpwrak>
perhaps just unloading the critters will make them clean up properly
<jivs>
do you thing that might be an issue?
<antoniodariush>
wpwrak, do you have a list of the minimum required packages that we need to select from the toolchain to get it working
<wpwrak>
mmc_spi is a little strange. not sure what it tries to do. i'd get rid of it.
<jivs>
okay
<wpwrak>
antoniodariush: i don't how things map into packages. i always build things from scratch, without going though openwrt
<antoniodariush>
we used to do that as well but we'd like to avoid that and get it working out of the box
<wpwrak>
(mmc_spi) that's an MMC driver that works on top of SPI. what's weird about it is that we have a perfectly good MMC controller. do if it uses the same pins, it would be a grossly inefficient alternative to the proper controller (and driver). if it uses other pins, i'd kinda wonder which.
<wpwrak>
(mmc_spi) so that's another item where nothing good can come from having it
<jivs>
i am recompiling w/o these packages now
<jivs>
the at86rf230 driver is selected on the toolchain
<wpwrak>
too bad xiangfu is probably asleep now. he must have tested the packaging and have a working sequence.
<jivs>
but i am not sure if it is being build/loaded properly
<wpwrak>
ks8995 is that sdio-wlan device, right ? do you actually have that ? if not, one more item to get rid of
<jivs>
no we dont use that
<wpwrak>
okay. so trading all the devices that don't make sense for the one that does ought to improve the situation :)
<jivs>
:-)
<wpwrak>
i don't know if there are internal dependencies in the openwrt build process that would knock out at86rf230. chances are that it's just not loaded
emeb has joined #qi-hardware
<jivs>
is spi_gpio is needed?
zenlunatic has joined #qi-hardware
<wpwrak>
sholdn't be. atben talks to the ports directly
<wpwrak>
well, spi_atben
<wpwrak>
ah yes, that's another driver that's missing
<jivs>
ok
kilae has joined #qi-hardware
<jivs>
[ 561.980000] at86rf230: probe of spi32766.0 failed with error -16
<jivs>
actually when we are doing insmod on at86rf230.ko, it is giving that error
<jivs>
hints anything?
panda|x201 has joined #qi-hardware
antoniodariush has joined #qi-hardware
<wpwrak>
that's EBUSY. perhaps something else is in the way ?
<jivs>
got rid of that error with echo jz470-mmc...
<jivs>
testing further now
<jivs>
yeh it works now
<jivs>
got short address from coordinator
<jivs>
thanks wpwrak
<jivs>
will test dirtpan now
<wpwrak>
whee ! :)
<jivs>
thanks.. :-)
antgreen has joined #qi-hardware
<wpwrak>
so it all works now ?
<antoniodariush>
wpwrak, so far so good we only have a problem on the dirtpan now
<antoniodariush>
"/dev/net/tun: No such file or directory"
Ayla has joined #qi-hardware
jekhor has joined #qi-hardware
Ayla has joined #qi-hardware
kuribas has joined #qi-hardware
zedstar has joined #qi-hardware
zedstar has joined #qi-hardware
uwe_mobile has joined #qi-hardware
mstevens has joined #qi-hardware
jekhor has joined #qi-hardware
abushcrafterforg has joined #qi-hardware
abushcrafterforg has joined #qi-hardware
* zenlunatic
just got his BNN... about to unbox
<zenlunatic>
is the screen supposed to be a little flickery?
<viric>
zenlunatic: not that I remember. but maybe my retina has a longer integration time
<viric>
talking about flickering...
<viric>
These christmas, the governmet put the street decoration lights a lot using LEDs
<viric>
which had such a power supply, that were lighting only half of the 50Hz AC cycle
<viric>
and a long street blinking at 50Hz flashes instead of 100Hz was quite nocieable
<viric>
noticeable
<viric>
(I exposed the opposite way I was experiencing and deducing the situation)
<rz2k>
lol
Artyom has joined #qi-hardware
<zenlunatic>
seems to be a driver problem
<zenlunatic>
cool... wheezy sees it
Ayla has joined #qi-hardware
LunaVorax has joined #qi-hardware
<DocScrutinizer51>
whitequark: I have no idea what Samsung flashes to the modem, but I dwefinitely not seen such crap you mentionee, anywhere in gthe image I build every day
<DocScrutinizer51>
whitequark: maybe OSE has some special curls for Siemens etc, and this might show up in a binary
<DocScrutinizer51>
whitequark: also are you sure you've not scanned the APE stuff Samsung added? you know, I'm just talking about modem