#qi-hardware IRC log for Tuesday, 2011-04-05

wpwraktuxbrain: btw, when you get the boards from adam, you may want to try the user space tools to check that things work. that's still the most "useful" process to date: http://lists.en.qi-hardware.com/pipermail/discussion/2011-March/007587.html00:50
panda|x201wolfspra1l, ping07:53
panda|x201xiangfu, ping07:53
xiangfupanda|x201: pong08:00
whitequa1kxiangfu: what about jzboot integration? I've sent you a reply08:51
xiangfuwhitequa1k: sorry. I put too much time on milkymist one recently. sorry.08:53
xiangfuwhitequa1k: I was thinking. we can add support nanonote to jzboot. then we can just delete the usbboot in future. and keep the xbboot.08:54
xiangfuwhitequa1k: do you think we should merge to source code repo?08:55
kyakwhat's the difference between jzboot and usbboot?08:55
whitequa1kxiangfu: no problem, I just wanted to be sure that my letter wan't eaten by spam-filter or something like that08:57
xiangfuusbboot source code is very very bad. the target source code are copy  from ingenic.cn08:58
xiangfukyak: only the target image source code is bad :)08:58
kyakso you mean that jzboot is much cleaner?08:58
kyakwhat about the functionality?08:58
xiangfukyak: I think so.08:58
whitequa1kI don't think that merging repositories is a good idea, jzboot is completely different from usbboot08:59
kyakxiangfu: i'm thinking about that bug in latest usbboot, that corrupted the bootloader. Maybe it'll work good in jzboot?08:59
whitequa1kI think you can set up a repo for 'qi-jzboot' and then we'll add all relevant changes to it09:00
xiangfuwhitequa1k: where is the source code of firmware in jzboot09:00
whitequa1kalso, it uses target images from usbboot/ingenic. the main difference is in host functionality09:01
xiangfuwhitequa1k: so you don't have touch the firmware source code. only the host app?09:01
whitequa1kthe host app was rewrittten from scratch, through09:02
xiangfuwhitequa1k:maybe the first step is include the 'jzboot' in debian package xburst-tools. :)09:02
xiangfuwhitequa1k: ok. understand now.09:03
whitequa1kthen it makes sense to include jzboot in your repo, yeah09:03
xiangfuwhitequa1k: hmm.. then the sync will be a problem. I will ask debian people if the package can build base on two repo :)09:03
xiangfukyak: if they using the firmware from ingenic.cn.  then jzboot will be the same as lastest usbboot.09:05
kyakxiangfu: does it mean that older usbboot wasn't using the firmware from ingenic?09:06
whitequa1kxiangfu: I mean that we can just include it in a subdirectory, not merging anything (in this context word merge can have different meanings), and then it won't be a problem to build the package09:06
whitequa1kI think it's OK to make repository on qi-hardware the main one for jzboot09:06
xiangfuwhitequa1k: oh. yes. a subdirectory will not a problem09:07
kyakxiangfu: this is strange, i'm using the same firmware with both older and latest usbboot, but only latest usbboot has this problem09:07
whitequa1kkyak: the firmware has some glitches , which have workarounds in jzb[D[D[D[D[D[D[D[D[D[D[D[D[Doot09:08
whitequa1kokay, I'll find a better internet connection then09:09
whitequa1kI'll return in ~2 hours09:09
xiangfuwhitequa1k: (main one for jzboot) . ok talk to you when you back :)09:10
xiangfukyak: which commit of the older usbboot?09:14
xiangfukyak: can you test reflash twice u-boot on your nanonote. ?09:24
kyakxiangfu: i reflashed in several million times :)09:56
kyakit doesn't help09:56
kyakxiangfu: which commit - i don't know. I tested the old release (mentioned in my e-mail back then) and the latest one from git09:57
whitequa1kxiangfu: I'm here11:46
xiangfuwhitequa1k: Hi   (main one for jzboot)  so we make a sub-folder under xburst-tools?11:48
xiangfuwhitequa1k: ok. great. I remember I saw some document that we can import all git history to another git sub-folder.11:48
whitequa1kthat is called 'git submodules'11:49
tuxbrainwpwrak aw_ parcel with atben atusb and jtag had just arrived :)11:49
xiangfuwhitequa1k: oh. do you have an account in projects.qi-hardware.com?11:50
whitequa1kI'll register now then11:51
aw_tuxbrain, pls just send to list then we can view it. :-)11:51
tuxbrainI have a lot of other work to do but I will try to follow the wpwrak howto asap and do some post about it, also sugru is on its way so I will also make some lamer test on if it cause any perceptible effect11:52
aw_tuxbrain, sorry that I was thought it's the panelized gerber. :-)11:52
tuxbrainaw_:  no was your p├árcel :P the pcb maker is not so quick :P11:53
aw_tuxbrain, yup...;-)11:53
whitequa1kxiangfu: done, username is whitequark11:56
tuxbrainwpwrak: the atusb is making my dmesg crazy http://pastebin.com/Q25rmNX7 :P11:57
xiangfuwhitequark: add you as the project admin :) http://projects.qi-hardware.com/index.php/p/xburst-tools/11:57
xiangfuwhitequark: then you have the write access to xburst-tools.11:58
whitequarkxiangfu: good. I'm waiting for ssh key to propagate itself11:59
xiangfuwhitequark: for add jzboot to xburst-tools just run "cd xburst-tools && git submodule add /PATH/to/jzboot/ jzboot" right?12:01
xiangfuwhitequark: I don't this command before.12:01
xiangfuI don't know this command before.12:03
whitequarkxiangfu: yeah, but it is better to use a remote repository, so that everyone may clone the submodule12:07
whitequarkI currently have one on git.whitequark.org, but maybe it makes sense to set up a qi-hardware project in the case whitequark.org goes down12:09
xiangfuwhitequark: sure.12:10
xiangfuwhitequark: after you create the jzboot.git in qi-hardawre. you merge those two repo is better. never use the 'git submodule' before12:12
whitequarkxiangfu: hmm, how can I create a project in qi-hardware?12:23
xiangfuwhitequark: sorry. I don't know if normal user can create project in qi-hardware.12:26
xiangfuwhitequark: I just create one named 'jzboot' : http://projects.qi-hardware.com/index.php/p/jzboot/12:26
xiangfuadd you as the admin.12:26
xiangfuthere should be a 'Project Management' tab after you goto http://projects.qi-hardware.com/index.php/p/jzboot/. you can update the detail there. add members. etc.12:28
whitequarkyeah, already12:32
qi-bot[commit] Peter Zotov: Added jzboot as submodule. http://qi-hw.com/p/xburst-tools/9546fde12:34
whitequarkprobably I need to include jzboot to autoconf build now. hm, I've never had any autoconf experience12:37
xiangfuupdating my local xburst-tools12:38
xiangfuwhitequark: after update local xburst-tools. the jzboot folder is empty. what should I do ?12:42
xiangfurunning "git submodule update --init jzboot/"12:43
xiangfuwhitequark: I made a small patch for jzboot.12:51
whitequarkxiangfu: have you pushed it?12:53
xiangfuwhitequark: not yet. I still not very clear how submodules works. needs add one Makefile.am to the jzboot.12:53
whitequarkthe submodule is basically a link to a particular commit in other repository12:54
whitequarkso when you fetch a commit X from main repository, and run 'git submodule update', it will always fetch commit Y (recorded in .gitmodules) from the submodule repo12:54
whitequarkthe submodule itself is a perfectly normal git repository12:55
whitequarkso, after you update the submodule (i.e. checkout other commit in the subdirectory), you need to commit the parent repo as well12:55
xiangfuwhitequark: so for add a new file Makefile.am . I have to push it to jzboot.git?12:55
whitequarkwill qi-bot announce commits in jzboot?13:00
wolfspra1lnot yet :-)13:00
xiangfuwhitequark: I will add me as the jzboot.git member. then add the new file Makefile.am13:02
whitequarkxiangfu: I've already added you13:02
Action: xiangfu is adding jzboot to qi-bot.13:08
xiangfuok. wolfgang is faster then me. :)13:11
qi-bot[commit] Xiangfu Liu: add Makefile.am for xburst-tools autoconf http://qi-hw.com/p/jzboot/da72c3513:12
qi-bot[commit] Xiangfu Liu: add jzboot to build system http://qi-hw.com/p/xburst-tools/461712a13:15
whitequarkhm, that was easy13:15
whitequarkah no, it wants Makefile.in13:15
jow_laptop:D :D13:16
xiangfuwhitequark: ./autogen.sh && ./configure CROSS_COMPILE=mipsel-openwrt-linux-13:16
whitequarkautogen.sh fails13:16
whitequarkah yes. that's exactly the thing I hate about submodules13:17
xiangfuwhitequark: I am under xburst-tools.git. it show me that "modified:   jzboot" what I should do before run "git submodule update' ?13:17
whitequarknow you need to do 'git add jzboot; git commit'13:18
whitequarkthat will record the fact jzboot HEAD has changed in .gitmodules of xburst-tools13:19
qi-bot[commit] Xiangfu Liu: those file auto created by automake system http://qi-hw.com/p/jzboot/ce7446f13:30
qi-bot[commit] Xiangfu Liu: update jzboot http://qi-hw.com/p/xburst-tools/1eaeb7d13:32
xiangfuwhitequark: now. it's clear now.13:33
xiangfuwhitequark: what is the error of your 'autogen.sh' ?13:33
whitequarkthat was caused by nonexistent Makefile.am because jzboot has not updated13:34
whitequarkit's fine now13:34
tuxbrainroh wpwrak aw_ wolfspra1l sugru also arrives... sigh why by the love of $DEITY fun stuff arrives when your plenty of boooring stuff to take care off13:35
whitequarkxiangfu: jzboot has readline support, but currently it's enabled by compiling make READLINE=113:36
whitequarkI wonder how that should be hooked into autoconf13:36
xiangfuneeds add one option to './configure.ac' and the 'jzboot/makefile.am' check the ./configure.ac line 12.13:38
xiangfuthere is a '--enalbe-firmware' '--disable-firmware' in configure now. for enable/disable firmware under usbboot13:39
whitequarkokay, I'll do that13:40
xiangfuusbboot/src/Makefile.am line 1513:41
xiangfuwhitequark: thanks13:41
whitequarkwhy there is a .mailmap file in xburst-tools root?13:48
tuxbrainbtw guys another topic question... what people do you think about RFID technology? Is a pantent trap? I think a rfid-6lowpan device can be cool by itself but also a good complement for nanonote as datalogger.13:50
xiangfuwhitequark: it's commit by Jonathan Nieder, for 'git shorlog'13:56
whitequarksure, but what purpose it has? I've never seen that before13:59
wpwraktuxbrain: (parcel arrived) wonderful ! and great timing ! ;-)14:00
wpwraktuxbrain: (atusb) hmm, both of them ?14:01
tuxbrainwpwrak: (atusb) no, the atusb6 is the crazy one, the 7 gives me [192239.352519] usb 2-1: new full speed USB device using uhci_hcd and address 9014:05
tuxbrain[192239.480312] usb 2-1: device descriptor read/64, error -7114:05
tuxbrain[192239.965081] usb 2-1: configuration #1 chosen from 1 choice14:05
tuxbrainand a pretty lsusb14:06
tuxbrainBus 002 Device 091: ID 20b7:154014:06
xiangfuwhitequark: I guess it's for "debian/changelog.upstream.awk"14:07
whitequarkxiangfu: ah right, thanks14:07
whitequarkI'm currently converting the entire jzboot to automake14:07
xiangfuwhitequark: we need cleanup the debian build code. since we don't using the git commit any more. instead we start to release the source tar ball.14:07
wpwraktuxbrain: (atusb6) hmm. maybe the USB reset problem has a time component. or some hardware issue re-appeared. do you have something that can measure frequency up to > 1 MHz ? (ideally, 8 MHz, but anything above 1 MHz should do)14:14
tuxbrainwpwrak: nop14:15
tuxbrainI doubt my old faithfull digital voltmeter can do what you said, or maybe yes but my eyes  can't pericive the fluctuations  >0,01MHz14:17
whitequarktuxbrain: ahem... do you want to say you can catch 10kHz with your eyes?14:19
whitequarkthat's pretty impressive14:19
jlamotheClearly you're superman.  :)14:20
tuxbrainnah! just trained with codificated porn films during my adolescense14:20
tuxbrainIn spain there is a full male generation able to do that :)14:22
tuxbrainhehehe zumbi is another one of those :P14:26
wpwraktuxbrain: (no instruments) hmm, could also be that it just doesn't have the correct firmware. i expected that we'd have to reflash for some updates anyway, so i didn't particularly check. you can change the firmware with the process described here: http://lists.en.qi-hardware.com/pipermail/discussion/2011-March/007641.html14:30
wpwraktuxbrain: programming would be the  make prog-app  step14:30
wpwraktuxbrain: there are basically four things that can cause problems with USB: 1) a problem in the USB-ATmega32U2 side connection. that should be very unlikely (could happen in production, though, e.g., if they produce a short across one of the TVS)14:32
wpwraktuxbrain: 2) the yet unresolved USB reset/enumeration problem on its own. that is just a guess. 3) having both DFU and application in the flash. that would cause them to cycle endlessly through reset, due to the USB reset problem. the solution is to just flash the application, without flashing the DFU boot loader.14:34
tuxbrainwpwrak: roger, I will try to reflash it today night or tomorrow, now I must leave14:35
wpwraktuxbrain: 4) if the ATmega32U2 fails to switch the clock speed. the transceiver produced a 1 MHz clock after reset. the MCU needs 8 MHz, so it tells the transceiver to switch. if this goes wrong, the system will run at an incorrect speed.14:36
tuxbrainwpwrak: btw pretty impresive piece of artesany both atben/atusb.... do you think about dedicate to jewelry?14:36
wpwrak(jewelry) thanks ! maybe we should start a fashion trend that uses electronic as jewelry ;-)14:37
tuxbrainad 6lowpan biometrics to this and you have a win product :)14:41
tuxbrainbtw wpwrak what do you think about RFID tech?14:41
tuxbrainmust leave read you later14:42
qi-bot[commit] Peter Zotov: Changed everything to use autotools. http://qi-hw.com/p/jzboot/8b4338f15:59
qi-bot[commit] Peter Zotov: Adjusted configure.ac to search for libraries required for jzboot. http://qi-hw.com/p/xburst-tools/c26a0ce16:00
whitequarkxiangfu: I've ported that to autotools. even with fancy --with-readline switch16:02
wpwraktuxbrain: (rfid) no idea. i don't know the use cases too well. okay, except as fancy bar codes.16:03
xiangfuwhitequark: cool.16:05
whitequarki'll try to hook up debian packaging for jzboot then16:07
tuxbrainwpwrak: animal control on farms, logistics, personal identification for security... but yes all uses cases can be sumarized on fancy bar codes :)16:13
tuxbrainwhat I mean is to have an auntonomouse device with 6lowpan and rdif reader to integrate in a 6lowpan network, but I don't know is rfid is pantent tainted technology or how dificult is to implement16:16
wpwraktuxbrain: don't know about RFID IPR issues either16:28
tuxbrainIPR (Intellectual property reclaim?)16:29
C-Keenrights I guess16:29
wpwraktuxbrain: if you have some RFID thingy that tasks plain SPI, there should be no problem connecting it to a 6LoWPAN device. there are a lot of MCU+IEEE 802.15.4 chips, and many of then are supported by contiki16:29
wpwraktuxbrain: Intellectual "Property" "Rights"16:30
C-Keenwpwrak: "intellectual" too16:30
wpwrakC-Keen: heh, particularly when combined with the other two :)16:31
C-Keenwpwrak: they always play together16:32
tuxbrainwprack so, maybe UBB+ this http://www.cutedigi.com/product_info.php?cPath=278_299&products_id=4365&osCsid=76ba07b577801bae061ddb65ed61062d = NanoNote RFID reader/writer?16:46
tuxbrainwhat to add to the avove module to have a tinny to make autonomous 6lowpan?16:47
tuxbraindue then NN+atben +RFID thing = example on how to expand Nanonote wiressly16:49
tuxbrainwiressly-> wirelessly16:49
tuxbrainor maybe better with this one http://www.priority1design.com.au/rfidread-mrw.pdf17:03
wpwraktuxbrain: for an autonomous wireless system, you could use, say, the freescale mc13224v17:03
wpwraktuxbrain: that's an arm7 (plus RF). even has the balun integrated. a bit difficult to solder, though - sort of a hybrid between QFN and BGA17:04
whitequa1kit's also cheap for such a good soc17:05
whitequa1k$9 here17:06
whitequa1kbtw, can anyone suggest an easy-to-use 2.4GHz transciever with no external components?17:06
wpwrakwhitequa1k: you mean a chip (which probably doesn't exist) or a module ?17:09
wpwrakwhitequa1k: also, what do you do with the rf signal ? antenna or connector would be "external components", right ? so it has to be a module then17:10
tuxbrainwpwrak: I think can have access to someone able to solder it.... so in theory connecting this freescale to the avobe rfidreader, some source of power and we are done?17:11
whitequa1kwpwrak: a chip. I've found TI's CC2500, but a few people that worked with it complain to unstabilites17:11
whitequa1kit technically requires only several caps and a PCB antenna17:11
wpwrakwhitequa1k: and a crystal, plus for anything but a dipole, a balun. that's just like the at86rf23117:16
wpwraktuxbrain: could work, yes17:17
wpwrakwhitequa1k: the crystal is almost unavoidable - you need 40 ppm stability17:17
whitequa1kwpwrak: oh sure, a crystal too, and load capacitors17:18
wpwrakwhitequa1k: someone could design a "parasitic" oscillator that takes another station as its reference, but afaik, nobody has done such a thing yet17:18
wpwrakwhitequa1k: i think the mc1322x may be your best best for low component count. no external xtal load caps, integrated balun. unfortunately, the chip itself is a bit large. but still smaller than a module17:19
whitequa1kwpwrak: it's not only large, it has pads underneath it. I won't be able to do pcb for it by myself17:20
whitequa1kso unfortunately I don't think that is an option17:20
whitequa1katrfs are nice, but I wasn't able to find any in russia (you can buy a thousand, but not one)17:21
wpwrakwhitequa1k: if you can buy a thousand, someone must have spares :)17:23
wpwrakwhitequa1k: maybe ask atmel ? otherwise, the cc2500 may be a suitable alternative. oddly enough, that one has us export restrictions while the at86rf231 doesn't ;-)17:24
whitequa1kwpwrak: do you mean, ask them for samples?17:25
whitequa1kah well, terraelectronica has some cc2500 in stock. the problem is solved then17:28
whitequa1kalso, are those 'chip antennas' as good as they're described on vendor site?:)17:34
Action: wpwrak curses blackouts19:55
wpwrakwhitequa1k: (atmel) samples or names of distributors19:57
wpwrakwhitequa1k: (chip antenna) dunno. it's said that their performance varies a lot with their surroundings, so they may need careful tuning19:58
--- Wed Apr 6 201100:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!