From: Andy O. <and...@ho...> - 2012-01-10 10:56:11
|
Hello, I've recently bought a number of Overo Water COMs, but when fitting them to a Tobi board and connecting the serial cable, all I get is: Texas Instruments X-Loader 1.4.3 (Mar 2 2010 - 22:34:59) Unsupported Chip! X-Loader hangs Gumstix, any advice? Thanks, Andy -- View this message in context: http://gumstix.8.n6.nabble.com/Unsupported-chip-tp3531121p3531121.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: sturnfie <stu...@gm...> - 2012-01-10 16:47:10
|
Andy Odgers wrote > > Hello, > > I've recently bought a number of Overo Water COMs, but when fitting them > to a Tobi board and connecting the serial cable, all I get is: > > Texas Instruments X-Loader 1.4.3 (Mar 2 2010 - 22:34:59) > Unsupported Chip! > X-Loader hangs > > Gumstix, any advice? > > Thanks, > > Andy > Hi Andy, I'd suggest modifying X-Load to print the version information received from the chip. Greping the source for "Unsupported Chip" will show you where the conditional statements are (and provide examples of how to print the parsed version string). With that information, you can more accurately determine why this error is occurring. Lucas ----- -- Lucas Sturnfield stu...@gm... -- View this message in context: http://gumstix.8.n6.nabble.com/Unsupported-chip-tp3531121p3539166.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2012-01-10 16:52:51
|
The version of x-load (aka MLO) is rather old. I recommend creating a bootable microSD (http://gumstix.org/create-a-bootable-microsd-card.html) with a newer version of x-load (http://cumulus.gumstix.org/images/angstrom/developer/). On Tue, Jan 10, 2012 at 8:47 AM, sturnfie <stu...@gm...> wrote: > > Andy Odgers wrote >> >> Hello, >> >> I've recently bought a number of Overo Water COMs, but when fitting them >> to a Tobi board and connecting the serial cable, all I get is: >> >> Texas Instruments X-Loader 1.4.3 (Mar 2 2010 - 22:34:59) >> Unsupported Chip! >> X-Loader hangs >> >> Gumstix, any advice? >> >> Thanks, >> >> Andy >> > > Hi Andy, > > I'd suggest modifying X-Load to print the version information received from > the chip. Greping the source for "Unsupported Chip" will show you where the > conditional statements are (and provide examples of how to print the parsed > version string). > > With that information, you can more accurately determine why this error is > occurring. > > Lucas > > > ----- > -- > Lucas Sturnfield > stu...@gm... > > -- > View this message in context: http://gumstix.8.n6.nabble.com/Unsupported-chip-tp3531121p3539166.html > Sent from the Gumstix mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: sturnfie <stu...@gm...> - 2012-01-18 03:33:07
|
Ash Charles wrote > > The version of x-load (aka MLO) is rather old. I recommend creating a > bootable microSD > (http://gumstix.org/create-a-bootable-microsd-card.html) with a newer > version of x-load > (http://cumulus.gumstix.org/images/angstrom/developer/). > > I actually have a Gumstix board that has been having Unsupported Chip errors as well. The output from the newest build from Gumstix (Ash's link): Texas Instruments X-Loader 1.4.4ss (Oct 3 2011 - 15:03:12) Unknown chip: mfr was 0x82c, id was 0x8ba Unsupported Chip! X-Loader hangs Re-building xload with the unsupported conditional commented out allows the system to boot fully, albeit without NAND (u-boot throws some errors and defaults to hardcoded enviroment variable values). Lucas ----- -- Lucas Sturnfield stu...@gm... -- View this message in context: http://gumstix.8.n6.nabble.com/Unsupported-chip-tp3531121p3705305.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: sturnfie <stu...@gm...> - 2012-01-18 16:53:07
|
Here is the boot output when the "return 1" of the x-load conditional is commented out. The conditional checks mfr and id strings against hardcoded values to determine if the NAND memory model is supported. The system boots into userspace. Texas Instruments X-Loader 1.4.4ss (Jan 18 2012 - 10:16:49) Unknown chip: mfr was 0x82c, id was 0x8ba Unsupported Chip! OMAP3530-GP ES3.1 Board revision: 0 Reading boot sector Loading u-boot.bin from mmc U-Boot 2010.12 (Dec 16 2011 - 12:06:55) OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz Gumstix Overo board + LPDDR/NAND I2C: ready DRAM: 256 MiB NAND: nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x08, Chip ID8 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In: serial Out: serial Err: serial Board revision: 0 Tranceiver detected on mmc2 No EEPROM on expansion board Die ID #2d2c0004000000000403a5b609017014 Net: smc911x: Invalid chip endian 0xff08ff08 No ethernet found. Hit any key to stop autoboot: 0 reading uImage 1949292 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 82000000 ... Image Name: Angstrom/2.6.36/overo Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1949228 Bytes = 1.9 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. ----- -- Lucas Sturnfield stu...@gm... -- View this message in context: http://gumstix.8.n6.nabble.com/Unsupported-chip-tp3531121p3739350.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2012-01-18 18:14:53
|
Hey, According to http://www.linux-mtd.infradead.org/nand-data/nanddata.html, your NAND id doesn't match anything. Can you try compiling Steve's xloader? Specifically: $ git clone git://www.sakoman.com/git/x-loader.git $ cd x-loader $ git checkout gnome-r13 $ make overo_config $ make CROSS_COMPILE=arm-linux-gnueabi- -j2 Your cross-compiler may vary. -Ash On Wed, Jan 18, 2012 at 8:53 AM, sturnfie <stu...@gm...> wrote: > Here is the boot output when the "return 1" of the x-load conditional is > commented out. The conditional checks mfr and id strings against hardcoded > values to determine if the NAND memory model is supported. The system boots > into userspace. > > Texas Instruments X-Loader 1.4.4ss (Jan 18 2012 - 10:16:49) > Unknown chip: mfr was 0x82c, id was 0x8ba > Unsupported Chip! > OMAP3530-GP ES3.1 > Board revision: 0 > Reading boot sector > Loading u-boot.bin from mmc > > > U-Boot 2010.12 (Dec 16 2011 - 12:06:55) > > OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz > Gumstix Overo board + LPDDR/NAND > I2C: ready > DRAM: 256 MiB > NAND: nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x08, Chip > ID8 > 0 MiB > MMC: OMAP SD/MMC: 0 > *** Warning - readenv() failed, using default environment > > In: serial > Out: serial > Err: serial > Board revision: 0 > Tranceiver detected on mmc2 > No EEPROM on expansion board > Die ID #2d2c0004000000000403a5b609017014 > Net: smc911x: Invalid chip endian 0xff08ff08 > No ethernet found. > Hit any key to stop autoboot: 0 > > reading uImage > > 1949292 bytes read > Booting from mmc ... > ## Booting kernel from Legacy Image at 82000000 ... > Image Name: Angstrom/2.6.36/overo > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 1949228 Bytes = 1.9 MiB > Load Address: 80008000 > Entry Point: 80008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > ----- > -- > Lucas Sturnfield > stu...@gm... > > -- > View this message in context: http://gumstix.8.n6.nabble.com/Unsupported-chip-tp3531121p3739350.html > Sent from the Gumstix mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: sturnfie <stu...@gm...> - 2012-01-18 23:05:12
|
Ash Charles wrote > > Hey, > > According to http://www.linux-mtd.infradead.org/nand-data/nanddata.html, > your NAND id doesn't match anything. > > Can you try compiling Steve's xloader? Specifically: > $ git clone git://www.sakoman.com/git/x-loader.git > $ cd x-loader > $ git checkout gnome-r13 > $ make overo_config > $ make CROSS_COMPILE=arm-linux-gnueabi- -j2 > > Your cross-compiler may vary. > > -Ash > > Thanks for the response! I'm fairly certain this is not a software issue. I should have realized this initially, but the failures are only seen on a recent custom daughterboard we have in-house. I tried the Overo in one of my older designs and no issues are seen. (a build of the linked x-load source results in same error; and the MFR/ID listings in the driver are the same between that source and the source I've been building from). So I am left trying to figure out what could cause an extraneous bit or two to be read from the NAND interface when pulling the mfr/id strings. Removing a GPIO level shifter effectively removes all new peripheral components, leaving a known good circuit. I don't think it is the electrical circuit. I'm thinking I made the 3.3V traces to J1 way too thin...I'm going to see if a wire jump from the regulator solves my problem....maybe some internal brown-out is happening when the NAND is initialized? Lucas ----- -- Lucas Sturnfield stu...@gm... -- View this message in context: http://gumstix.8.n6.nabble.com/Unsupported-chip-tp3531121p3813152.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Steve S. <sa...@gm...> - 2012-01-18 23:13:24
|
On Wed, Jan 18, 2012 at 3:05 PM, sturnfie <stu...@gm...> wrote: > I'm fairly certain this is not a software issue. I should have realized this > initially, but the failures are only seen on a recent custom daughterboard > we have in-house. I tried the Overo in one of my older designs and no issues > are seen. (a build of the linked x-load source results in same error; and > the MFR/ID listings in the driver are the same between that source and the > source I've been building from). > > So I am left trying to figure out what could cause an extraneous bit or two > to be read from the NAND interface when pulling the mfr/id strings. Removing > a GPIO level shifter effectively removes all new peripheral components, > leaving a known good circuit. I don't think it is the electrical circuit. > > I'm thinking I made the 3.3V traces to J1 way too thin...I'm going to see if > a wire jump from the regulator solves my problem....maybe some internal > brown-out is happening when the NAND is initialized? NAND is on the GPMC bus, so if your custom daughterboard uses those signals I would look there first. If your card is affecting the state of the GPMC data or address pins that would explain why the NAND type isn't being detected properly. Make sure no GPMC address/data lines are shorted together or to power/ground. Steve |
From: sturnfie <stu...@gm...> - 2012-01-25 14:57:05
|
Steve Sakoman wrote > > NAND is on the GPMC bus, so if your custom daughterboard uses those > signals I would look there first. If your card is affecting the state > of the GPMC data or address pins that would explain why the NAND type > isn't being detected properly. > > Make sure no GPMC address/data lines are shorted together or to > power/ground. > > Steve > > Thanks Steve. A hot-air reflow of the J4 connector remedied the issue. Lucas ----- -- Lucas Sturnfield stu...@gm... -- View this message in context: http://gumstix.8.n6.nabble.com/Unsupported-chip-tp3531121p4338336.html Sent from the Gumstix mailing list archive at Nabble.com. |