<qi-bot> [commit] Werner Almesberger: m1/perf/sched.c: don't try to unblock references of next setter twice (more) (master) http://qi-hw.com/p/wernermisc/0f80dcf
<qi-bot> [commit] Werner Almesberger: m1/perf/Makefile: use -fno-builtin, use profiling libc, set -DPRINTF_FLOAT (master) http://qi-hw.com/p/wernermisc/e2c133e
<qi-bot> [commit] Werner Almesberger: m1/perf/tabular: print total run time at the end (master) http://qi-hw.com/p/wernermisc/af8935f
<qi-bot> [commit] Werner Almesberger: m1rc3/norruption/LOG: updated with the "endless" run (master) http://qi-hw.com/p/wernermisc/37f2c60
<qi-bot> [commit] kyak: kernel-3.0: add fbcon color fonts patch (master) http://qi-hw.com/p/openwrt-xburst/c32e1d3
<kristianpaul> DocScrutinizer: wolfspra1l ^
<DocScrutinizer> \o/ finally, I already searched for it but it wasn't up back when
<DocScrutinizer> now those guys are messing not only with local carriers and authorities, but also with international big business and politics and 3letter agencies - YAY
<DocScrutinizer> feels the black helis approaching in the night
<DocScrutinizer> hmm OK, OTG pin control bit POR default: 0=disabled
<DocScrutinizer> ( Table 5. Control/Battery Voltage Register (Read/Write) Memory Location: 02, Reset State: 0000 1010  B0(LSB) )
<DocScrutinizer> s after POR it acts like 24150?
<DocScrutinizer> ooops ETAB, sorry
<qi-bot> [commit] Maarten ter Huurne: MIPS: A320: Do not mark line-in as not connected. (jz-3.0) http://qi-hw.com/p/qi-kernel/cf663bf
<jlamothe> Does anyone happen to know what the maximum current of the 5v output on an Arduino Nano is?  I know the Digital outputs are 40mA, but I can't find anything on the regulated output.
<killi> Hi, ive been having some problems with my ben after i tried updating today. At first it all seem to go well, the reflash ben script manages to boot the device, but on flashing the bootloader it says that it has finished 2/2 but it exits and the following message is display: error - cant read bulk data from ingenic device: -100. After this when i tried booting once, wich caused a kernel panic, and later this evening i cant get any life in
<killi> Sorry for the long message...
<kristianpaul> try reflash again, try short usb cable
<kristianpaul> i must leave will be back in 2 hrs
<killi> ill try a shorter cable, but i dont think i even get it into usb boot modeÂ
<erikkugel> hi Killi did you try shorting the pins behind the batter for getting into USB mode?
<erikkugel> *USB boot mode
<killi> I havnt really tried that.
<killi> ill do that
<erikkugel> It's really easy and you can do it with a piece of foil if you lost the little rubber cap that shipped with the nanonote. Then, you can try running reflash_ben.sh again, or following the safer steps and flush manually with a series of commands.
<erikkugel> I remember recovering a Nanonote like this once, assuming you don't have a permanent hardware failure.
<killi> i didnt do it earlier because i couldnt find my carbonized rubber thingie, but i figured the "soft" version would be equally good.
<erikkugel> Normally it is, but, if you bricked your Nanonote the software keys wont work - there will be nothing running to read them (that's my understanding, might be wrong). You can use and kind of conductive material - foil is usually found in most kitchens :)
<erikkugel> *and = any
<killi> hehe, ill find some foil then:=
<killi> :)
<erikkugel> by the way, I lost my rubber cap too :)
<killi> hmm, taking the battery out and plugging it into my computer with the pins connected only result in a wierd clicking sound from inside the machine.
<erikkugel> hmmm that does not sound right, I mean, there should be no moving parts inside the nanonote, so what could be clicking?
<killi> dunno, sounds wierd. But there are good news! I got up in lsusb on another machine, gonna try to reflash. crossing my fingers!
<erikkugel> great! the instructions you should be following are under "Hardware Boot" here: http://en.qi-hardware.com/wiki/USB_BOOT_mode
<erikkugel> If reflash_ben.sh fails a second time, use the instruction to flush the ban manually.
<erikkugel> Use the instructions here: http://en.qi-hardware.com/wiki/Updating_Ben_with_usbboot
<erikkugel> that should keep you busy for a while, but feel free to write here and the mailing list if all else fails. Goodluck.
<wpwrak> ben, flash or be flushed ... what a cruel fate ...
<erikkugel> lolz indeed! but on the bright side how many devices give you the satisfaction of shorting pins to recover them?
<erikkugel> except routers, I guess :P
<erikkugel> ... and with kitchen materials, too!
<killi> hehe:)
<killi> thanks for the help, reflash_ben failed so ill try the "hard" way
<erikkugel> no worries. You might be looking at a genuinely bricked nanonote, though those are pretty rare ;) I that's the case maybe you can offer it for forensics to the guys at Qi :P
<erikkugel> by genuinely bricked I mean with a hardware failure
<erikkugel> Which error did reflash_ben.sh fail with the second time, just out of curiosity?
<killi> im getting some progress, steps 1 and 2 worked, now im stuck when going to nprog open....root.ubi, nprog says not enough arguments, but that i will figure out... So i dont think its bricked:)
<killi> i got the same error, ... ingenic device: -100
<killi> nprog 2048 openwrt-xburst-qi_lb60-root.ubi 0 0 -n is the correct command? keep getting:  not enough argument.
<erikkugel> are you located in the folder wehere openwrt-xburst-qi_lb60-root.ubi is located?
<killi> yes, but i added an e at the and, and it started flashing, so ill see where this gets me:)
<killi> thanks for all help erikkugel
<wpwrak> hmm, was that -100 or -110 ? -110 would be common, timeout. often a transmission problem.
<erikkugel> sounds like -110 is pretty generic, I wonder what -100 could be, and where could we get the legend for those codes, after all, its opensource hardware (mostly :p )
<erikkugel> I'm just calling -110 generic because in TCP/IP timeouts are generic - could mean anything :)
<kristianpaul> may be outdated xburst tools
<erikkugel> ha, good point.
<qi-bot> [commit] Werner Almesberger: m1/perf/Makefile: use libfpvm/x86-linux/Makefile (master) http://qi-hw.com/p/wernermisc/b2e2364
<qi-bot> [commit] Werner Almesberger: m1/perf/sched.c: removed "assert" hack (since we now use regular libc) (master) http://qi-hw.com/p/wernermisc/9db83ae
<qi-bot> [commit] Werner Almesberger: m1/perf/sched.c: tried and rejected more accurate LCPF distance heuristics (master) http://qi-hw.com/p/wernermisc/bb8c1ce
<qi-bot> [commit] Werner Almesberger: m1/perf/sched.c: if register allocation fails, return an error instead of aborting (master) http://qi-hw.com/p/wernermisc/3da0074
<qi-bot> [commit] Werner Almesberger: m1/perf/favg: tool to extract values from ./tabulate -h and to calculate averages (master) http://qi-hw.com/p/wernermisc/71cdeb8