Jason, This is a new board developed to support BeaglePilot <https://github.com/BeaglePilot> (a simplification of what i've been doing with Erle <http://erlerobot.com>) thereby i need to flash the EEPROM myself.
After removing some components that were creating conflicts with SYS_BOOT pins the behavior changed: - Out of 5 boards we manufactured we've been able to program the EEPROM of *only one* using the image i mentioned before ( *Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.11.22.img.xz*). This is what leads me to thing to a manufacturing issue. - The other 4 boards, apparently look good (tty interface appears when connected through miniUSB, no microSD card on) but once I introduce a microSD card with *Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.11.22.img.xz image* and the miniUSB is connected, the PWR LED turns on for about a second and then it switches off. No new tty interface appears under /dev/. This behavior doesn't happen with newer images but neither i can use them to flash the EEPROM. Kind regards 2014-07-02 14:04 GMT+02:00 Jason Kridner <jkrid...@gmail.com>: > > > On Wednesday, July 2, 2014, Víctor MV <v.mayor...@gmail.com> wrote: > >> A small update on this matter: >> >> I tried booting with different images, specially with one that in the >> past probed to do the job (refer to this thread >> <https://groups.google.com/forum/#!searchin/beagleboard/Incorrect$20magic$20number$20in$20EEPROM/beagleboard/Q65z5O4haYc/jnWWXsHz0CkJ> >> ): >> *Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.11.22.img.xz.* >> >> The odd thing is that the board doesn't boot (the PWR LED doesn't even >> light up) when this image is used. If new images are used PWR LED switches >> on but i get messages as: >> >> *-Boot SPL 2013.07-dirty (Sep 01 2013 - 12:08:18)* >> *Incorrect magic number (0xffffffff) in EEPROM* >> *Could not get board ID.* >> *Unknown board, cannot configure pinmux.### ERROR ### Please RESET the >> board ###* >> >> Not being able to access u-boot to flash the EEPROM. Has anyone seen >> such a behaviour (some images make the board work and some not)? >> >> @Gerald, do you thing this could be hardware related? >> > > Don't know if you should be thinking hardware issues yet. I don't think > you've said why the EEPROM wasn't programmed. > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
