cmwslws code is available here: http://github.com/cmwslw/nanotron and it shares most of the detection code with mine, but is much cleaner.
Stefan Krastanov schrieb: > May I see the code you used to detect the state of your Ipod. Even if it is > not commented I can save much time just looking at it. > > 2009/12/13 The Seven <these...@gmx.net> > >> Stefan Krastanov schrieb: >>> Questions about >>> http://l4n.clustur.com/index.php/Nanotron_3000#Testing_for_freeze >>> >>> For the kernel log you are using dmesg, right? Why not clearing it before >>> every note with "sudo dmesg -c"? >> As dmesg -c will also return the dmesg ring buffer contents before >> clearing it, it's probably the best way to do it, unless you maybe want >> to also be able to look at it manually... >>> The usb cable is connected _all_ the time, right? >> Yes >>> May I see the shell code that you are using on the PC? >> AFAIK tucenaber built his nanotron software based on cmwslws. However, >> both the arduino controller and the detection code was done by himself, >> and I haven't seen him on IRC in a long time. >>> I still don't understand very well how are you determining the state of >> the >>> Ipod. As far as I understand it is like this: if there is that nice >> message >>> in the kernel log you keep the note for future testing, if the message is >>> not there you are going to the next note? >> We're basically looking for the ipod to either connect and immediately >> disconnect again (crash), or to connect but stop responding to commands >> after some time (freeze), or to connect and fully enumerate (works). >> >>> Why then is someone using a light sensor to check for the backlight of >> the >>> Ipod? >> My nanotron contained a light sensor because I thought that we might >> need it back when building the hardware, but then found a way to do the >> whole detection via USB (even though I was using the platform >> independent approach to detect its state, by just checking whether we >> can access the ipods drive some seconds after it should have finished >> booting, and holding the disk mode combo during that time to catch it in >> disk mode (recognized via timing) if it crashes). I don't think anyone >> has ever actually used a light sensor for the state detection :-) >>> Do you have those timing specs for the 3g nano? >> Tucenaber probably has them, but I don't think he put them into the wiki. >>> Regards >>> Stefan >> >> _______________________________________________ >> Linux4nano-dev mailing list >> Linux4nano-dev@gna.org >> https://mail.gna.org/listinfo/linux4nano-dev >> http://www.linux4nano.org >> > _______________________________________________ > Linux4nano-dev mailing list > Linux4nano-dev@gna.org > https://mail.gna.org/listinfo/linux4nano-dev > http://www.linux4nano.org > _______________________________________________ Linux4nano-dev mailing list Linux4nano-dev@gna.org https://mail.gna.org/listinfo/linux4nano-dev http://www.linux4nano.org
