B4 autoinstallation fails (gives a 'help' prompt)
Current firmware: Q2C25 Upgrading to: Q2C26, OS579 ** Trying with SD card ** (use of the microSD adapter is a BIIIG mistake, came out half torn! :) Pressing 'X' and powering on takes me to: USB 2 devices: /pci/[EMAIL PROTECTED],5/[EMAIL PROTECTED],0 USB 1 devices: Type the ESC key to interrupt automatic startup Boot device: /sd/disk:\boot\olpc.fth Arguments: Type 'help' for more information. ok The Type help for more information and ok are not mentioned in the instructions I've read. The SD card is FAT16 formatted 512MB microSD (with adapter). Formatted within OS X but should be right. Anyone else seen the help prompt; what is it about? Typing boot there seems to go somewhere, but no text whatsoever is printed on screen. ** Trying with a USB 1 era SD/USB adapter ** USB 2 devices: /pci/[EMAIL PROTECTED],5/[EMAIL PROTECTED],0 USB 1 devices: /pci/[EMAIL PROTECTED],4/[EMAIL PROTECTED],0 /pci/[EMAIL PROTECTED],4/[EMAIL PROTECTED],0/disk Found USB 1.1 disk! Type the ESC key to interrupt automatic startup Boot device: /[EMAIL PROTECTED],4/disk:\boot\olpc.fth Arguments: Type 'help' for more information. ok Again, I should not be getting the 'help' notion, right? Typing 'boot' here gives: autore-version$ isn't unique do-usb-upgrade? isn't unique ... and a lot of such not unique things So, this points to olpc.fth having problems executing. Could it be linefeed issue? I've downloaded the file in OS X and it seems to have retained Linux/ OS X (LF) linefeeds. Any ideas? :? -asko ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: B4 autoinstallation fails (gives a 'help' prompt)
Asko Kauppi wrote: Current firmware: Q2C25 Upgrading to: Q2C26, OS579 What machine type? A-test? B1? B2-1? B2-2? B3? B4? C1? ** Trying with SD card ** (use of the microSD adapter is a BIIIG mistake, came out half torn! :) Pressing 'X' and powering on takes me to: USB 2 devices: /pci/[EMAIL PROTECTED],5/[EMAIL PROTECTED],0 USB 1 devices: Type the ESC key to interrupt automatic startup Boot device: /sd/disk:\boot\olpc.fth Arguments: Type 'help' for more information. ok The Type help for more information and ok are not mentioned in the instructions I've read. The SD card is FAT16 formatted 512MB microSD (with adapter).Formatted within OS X but should be right. Anyone else seen the help prompt; what is it about? Before issuing the ok prompt for the first time, OFW issues the Type 'help' message. If you then type help at the ok prompt you will get a summary of some of the most important OFW commands. That's all it is, just general information. Something is going wrong in the olpc.fth script. Which version of the script is it? You can find out by typing: ok more sd:\boot\olpc.fth The version string is on the seventh line, e.g.: Autoreinstallation version: 2007-09-13 21:09Z My best guess is that the olpc.fth file is getting truncated, so that the last few lines, which do most of the work by calling functions defined earlier, are not being executed. What are the last few lines that are displayed when you do the more command above? The expected last few lines are: update-activate-and-boot then then ; autore-version$ count type cr cr do-upgrade The next to last line (autore-version$ count type cr cr) is supposed to display the version string of the autoupdater script. The fact that you don't show that message suggests that the script is truncated before that line. Typing boot there seems to go somewhere, but no text whatsoever is printed on screen. ** Trying with a USB 1 era SD/USB adapter ** USB 2 devices: /pci/[EMAIL PROTECTED],5/[EMAIL PROTECTED],0 USB 1 devices: /pci/[EMAIL PROTECTED],4/[EMAIL PROTECTED],0 /pci/[EMAIL PROTECTED],4/[EMAIL PROTECTED],0/disk Found USB 1.1 disk! Type the ESC key to interrupt automatic startup Boot device: /[EMAIL PROTECTED],4/disk:\boot\olpc.fth Arguments: Type 'help' for more information. ok Again, I should not be getting the 'help' notion, right? The help is just a side effect. The real problem is that the script is returning to the ok prompt instead of doing the upgrade thing. Typing 'boot' here gives: autore-version$ isn't unique do-usb-upgrade? isn't unique ... and a lot of such not unique things That implies that major portions of the script are working correctly by defining new functions. The isn't unique messages indicate that those functions are being redefined after having already been defined once before by the first (automatic) attempt to run olpc.fth . The name (first word) on the last such isn't unique message is a clue about how far the script is getting before it dies. So, this points to olpc.fth having problems executing. Could it be linefeed issue? It is probably not a linefeed issue, unless the file contains mixed line endings. OFW automatically senses the line-ending style by looking at the first line, and uses that style for the rest of the file. The fact that you saw the isn't unique messages tells me that line endings are probably not the problem. I've downloaded the file in OS X and it seems to have retained Linux/ OS X (LF) linefeeds. Any ideas? :? -asko ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Anybody do BGA rework?
Hello, Been there, done that, for different devices - mostly PDAs. First you *must* check the specs : optimism won't get you far if the pins have different fonctions (like they have been swapped) or require some minor adaptations. Get the reference sheets for each device, read them and understand them. If you still believe it should work, then comes the actual physical work of reballing, etc: normally you would use a BGA rework station, but that ain't cheap. However, you can do that with easy to find and unexpansive tools. There is a nice visual guide with pictures and explainations on : http://digit.que.ne.jp/visit/index.cgi?Linux%a5%b6%a5%a6%a5%eb%a5%b9%b3%ab%c8%af%a5%e1%a5%e2%2f%a5%cf%a1%bc%a5%c9%a5%a6%a5%a7%a5%a2%2fC700%a5%e1%a5%e2%a5%ea%c1%fd%c0%df You can use excite.co.jp if you need translations, but the pictures alone are quite evident. Train yourself with dead hardware from ebay - you make many mistakes the first time :-) Be sure to have a soldering iron with the thinnest tip you can find, stripping wire, and a hotglue gun. It will come handy should you damage the motherboard by accident (it can happen; cutting a track, etc). If you need more information/help, tell me. I'm not sure I can help you (it's been a while since my last serious hardware hack) but I'd be happy to point you to people who can. Guylhem On 9/14/07, Albert Cahalan [EMAIL PROTECTED] wrote: I'm wondering if one could replace the 88W8385 on a gumstix board with an 88W8388 swiped from an Xbox 360 wireless device. They appear to be the same chip package. This of course does not ensure that enough of the connections are compatible, but I think there is reason to be optimistic. It's this horrifying package: TBGA 132pin 8x8x1 (any better ideas for getting 88W8388 hardware?) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Roadmap
Thanks, Kim. - Bert - On Sep 14, 2007, at 19:18 , Kim Quirk wrote: Sorry Bert... I feel like I updated this at the beginning of the week when we pushed code freeze out... but it looks like the change didn't take or something. I'm updating Trial-3 dates right now. Kim On 9/14/07, Bert Freudenberg [EMAIL PROTECTED] wrote: Hi everyone, is the roadmap up to date? http://dev.laptop.org/roadmap In particular the dates in it? - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Get involved - Measure Activity on the XO
Measure Activity on the XO (The Activity which converts the XO into an oscilloscope, a spectrum analyzer and a data logger !) Release 9 of the Measure Activity (build 575 onwards) features an improved UI and the following basic features - * Apply an AC or DC signal into Mic_In port, or simply observe the sound signal picked up from the Mic on the XO * Watch the signal in time domain for frequency domain representation * Toggle the bias voltage at the Mic_in port ON/OFF. This voltage is required by many sensors. * Log data at a specified interval, take a snapshot of the current waveform; and draw a graph of the logged data too. How can you help ? (1) Help in software development of the activity. There are many refinements and features that can further be added. I have put some of the priority ones down as tickets in Trac. Have a look at #3435, #3437, #3438 and #3461. (2) Do projects (and help document them ) around the Measure Activity. Ideas ranging from building a low cost ECG system to a low cost intrusion alarm system. I've built and tested two ideas illustrating the concept : ='A low cost intrusion alarm system' that makes use of a toy laser that I powered from the USB and used a simple LDR (light dependent resistor) connected to the MIC_IN. Switch on the bias, set the activity to DC mode; observe the voltage change when the light path of laser upon the LDR is cut! ='Temperature' monitoring system that I made simply with an LM35 temp sensor, and I powered the sensor from the USB port. (3) Help develop content and curriculum around the Measure activity. Science experiments, Physics concepts...being able to relate concepts with physical phenomena through hands on experiments makes for great learning ! For example, kids can whistle into the mic and using the frequency domain display mode in Measure, compare and learn about frequencies... (4) Want to build a low cost science/physics/chemistry lab ? A tele-health monitoring system ? Lots of possibilities to be explored. All new ideas welcome! (5) Help document such projects and other cool ideas . We would , in probability, be going in for Makezine DIY style documentation of such projects - with cool illustrations, photographs and explanation... Get in touch with me at [EMAIL PROTECTED] for any details/clarifications. Looking forward to great collaboration and support from the community. sincerely, Arjun -- Arjun Sarwal ( [EMAIL PROTECTED] ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
