From: Benjamin M. <be...@dy...> - 2008-01-04 04:10:17
|
Hi, I have a Verdex XL6P attached to a console-vx (R1753). It does not seem to recognise when any USB devices are plugged in and it is providing no power to the USB port. It is currently running r1410 of the firmware that I downloaded from Sourceforge, but I have also tried it with the latest firmware (r1578) that I built with buildroot. I have tried both USB flash drives and bluetooth adapters, but nothing appears to be logged when I type dmesg (I have tested that they work on other computers). I have made sure that the ohci-hcd module is loaded and I have removed "auto usb0" from /etc/network/interfaces. Because the USB port is not providing any power, I made a USB cable that provides 5V so now at least I can see that the bluetooth adapter is being powered, but there is still nothing reported by the gumstix. Is there something wrong with my console-vx board or am I missing something? Thanks, Ben |
From: thaGod <th...@gm...> - 2008-01-04 04:38:20
|
The usb host should work out of the box. Have you tried USB keyboard? You have to mount the USB flash drive before it will work. I guess you've probably tried that? mount -t vfat /dev/sda1 Put a multimeter on the usb pin 1 and see if there's 5VDC.. if not then there's a hardware problem. Erick Benjamin Murray wrote: > > Hi, > > I have a Verdex XL6P attached to a console-vx (R1753). It does not > seem to recognise when any USB devices are plugged in and it is > providing no power to the USB port. > > It is currently running r1410 of the firmware that I downloaded from > Sourceforge, but I have also tried it with the latest firmware (r1578) > that I built with buildroot. > > I have tried both USB flash drives and bluetooth adapters, but nothing > appears to be logged when I type dmesg (I have tested that they work > on other computers). > > I have made sure that the ohci-hcd module is loaded and I have removed > "auto usb0" from /etc/network/interfaces. > > Because the USB port is not providing any power, I made a USB cable > that provides 5V so now at least I can see that the bluetooth adapter > is being powered, but there is still nothing reported by the gumstix. > > Is there something wrong with my console-vx board or am I missing > something? > > Thanks, > > Ben > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Verdex-USB-Host-not-working-%28no-power%29-tp14610600p14610766.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Christian R. <chr...@nd...> - 2008-01-09 20:23:00
|
Hi Guys, I'm at my wits end here. At the suggestion of you forum chaps I've installed open-embedded to try get some joy with the touchscreen since the buildroot thing is lacking the driver, etc, etc.. Great its got the i2c driver sorted and the TSC2003 driver finds the device 0x48, but then it gives i2c error: timeout messages and the ts_calibrate app doesn't do jack when I touch the calibrate cross hairs or any part of the screen for that matter. Not only that, I get TONS of jffs2 CRC failures. Why is the image corrupted? What am I doing wrong here? Does ANYONE have the touchscreen working? I read in one post that a wire needs to be soldered from some resistor to another point on the consoleLCD-vx board. Is this truly necessary? Could my hardware be broken? Thanks in advance. Xris. |
From: Marc H. <mhu...@lo...> - 2008-01-10 01:29:20
|
Last weekend I added the wire and built gumstix-oe version 110 of the gumstix-x11-image. I reflashed the board per the standard uboot 1.2 instructions (I used tftp to xfer the files though instead of serial port). Configuration is a xl6p with consoleLCD-vx plus Samsung LCD and netwifi-microSD card - without the wifi module attached. (The wifi worked too and even got two IP addresses right out of the shoot one on eth0 and the other on wlan0 without touching anything but it went into thermal shutdown after a while) Configuration has been up and running for 3 days without the wifi module plugged in though. The first time it booted it automatically showed the calibration crosshairs. I went thru the calibration procedure and touchscreen seems to work fairly well. It is a little noisy and as far as I can tell its mostly sensitive to flexing of the flex cable into the touch panel. Haven't looked into whether the cable is just poorly seated at this point or if its simply sensitive to vibration in general. Not sure on the cause of jffs2 crc errors. Marc -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Christian Ruocco Sent: Wednesday, January 09, 2008 3:23 PM To: General mailing list for gumstix users. Subject: [Gumstix-users] OE - Touchscreen - i2c timeout - JFFS2 CRC failures! Help ! Hi Guys, I'm at my wits end here. At the suggestion of you forum chaps I've installed open-embedded to try get some joy with the touchscreen since the buildroot thing is lacking the driver, etc, etc.. Great its got the i2c driver sorted and the TSC2003 driver finds the device 0x48, but then it gives i2c error: timeout messages and the ts_calibrate app doesn't do jack when I touch the calibrate cross hairs or any part of the screen for that matter. Not only that, I get TONS of jffs2 CRC failures. Why is the image corrupted? What am I doing wrong here? Does ANYONE have the touchscreen working? I read in one post that a wire needs to be soldered from some resistor to another point on the consoleLCD-vx board. Is this truly necessary? Could my hardware be broken? Thanks in advance. Xris. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Steve S. <sa...@gm...> - 2008-01-09 21:49:25
|
Yes, quite a few folks have functioning touchscreens! You do need to solder the wire on your consoleLCD-vx board. See the image below for where to solder it. http://www.sakoman.net/oe/B10003.rew.png As to the CRC errors, that shouldn't be happening. It might be bad hardware. Let's try to eliminate the possibility that your image is corrupted somehow. Could you reflash with one of the known good pre-built images? See the following for where to get the image: http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html Try an image from revision 113. Steve On Jan 9, 2008 12:23 PM, Christian Ruocco <chr...@nd...> wrote: > Hi Guys, > > I'm at my wits end here. At the suggestion of you forum chaps I've > installed open-embedded to try get some joy with the touchscreen since > the buildroot thing is lacking the driver, etc, etc.. Great its got the > i2c driver sorted and the TSC2003 driver finds the device 0x48, but then > it gives i2c error: timeout messages and the ts_calibrate app doesn't do > jack when I touch the calibrate cross hairs or any part of the screen > for that matter. Not only that, I get TONS of jffs2 CRC failures. Why > is the image corrupted? What am I doing wrong here? > > Does ANYONE have the touchscreen working? > > I read in one post that a wire needs to be soldered from some resistor > to another point on the consoleLCD-vx board. Is this truly necessary? > Could my hardware be broken? > > Thanks in advance. > > Xris. > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Steve S. <sa...@gm...> - 2008-01-15 15:21:18
|
Have you tried checking the crc of the image after you download it and comparing it with the crc from your build machine? That will eliminate transfercorruption as a possibility. IIRC, you have a verdex 600? Steve On Jan 15, 2008 6:54 AM, Christian Ruocco <chr...@nd...> wrote: > > Hi Steve/Guys, > > Got the touchscreen going! Loverly stuff. Thanks for the help. > > As for my JFFS2 CRC errors, I've tried the current image from > > > http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html > and I'm still getting TONS of CRC errors. In fact.. a hell of a lot more > that the buildroot images (they were a bit smaller).. It seems to actually > be quite variable. It seems every time I flash I get a different amount of > errors but I always get them. The OE image I'm using also complains it can't > create or find certain folders (dmesg) so I'm assuming the CRC errors > indicate real damage. > > Is it possible that my terminal app's kermit implementation could be > broken? I have tried hyperterm too and I still get CRC errors so I guess > that rules that out. > > Any ideas? > > Xris. > > > > Steve Sakoman wrote: > Yes, quite a few folks have functioning touchscreens! You do need to > solder the wire on your consoleLCD-vx board. See the image below for > where to solder it. > > http://www.sakoman.net/oe/B10003.rew.png > > As to the CRC errors, that shouldn't be happening. It might be bad hardware. > > Let's try to eliminate the possibility that your image is corrupted somehow. > > Could you reflash with one of the known good pre-built images? See > the following for where to get the image: > > http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html > > Try an image from revision 113. > > Steve > > On Jan 9, 2008 12:23 PM, Christian Ruocco <chr...@nd...> wrote: > > > Hi Guys, > > I'm at my wits end here. At the suggestion of you forum chaps I've > installed open-embedded to try get some joy with the touchscreen since > the buildroot thing is lacking the driver, etc, etc.. Great its got the > i2c driver sorted and the TSC2003 driver finds the device 0x48, but then > it gives i2c error: timeout messages and the ts_calibrate app doesn't do > jack when I touch the calibrate cross hairs or any part of the screen > for that matter. Not only that, I get TONS of jffs2 CRC failures. Why > is the image corrupted? What am I doing wrong here? > > Does ANYONE have the touchscreen working? > > I read in one post that a wire needs to be soldered from some resistor > to another point on the consoleLCD-vx board. Is this truly necessary? > Could my hardware be broken? > > Thanks in advance. > > Xris. > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Leonard S. <lsa...@co...> - 2008-01-17 04:25:40
|
Steve and any other developers having questions about the JFFS2 CRC errors... Here's a quick update (but not a fix ...) We received our Verdex XL6P 600 MHz with NetMicroSD and consoleVX, and it reported the "many CRC errors", so I have been digging around a bit. Here's the story so far (abbreviated to save bandwidth): 0) Was able to use the system on delivery, it booted though it had problems. Held together with screw/spacer combination, physical connectivity was consistent, not loose. 0.1) Good serial connectivity, good Ethernet connectivity, good microSD read/write, USB not tested 0.2) JFFS2 file system stable enough to modify /etc/resolv.conf, /etc/network/interfaces, though it took several tries for the changes to actually "stick" through reboot 0.3) Able to SSH into dropbear 0.4) Able to load "hello world" executables into /tmp (both C and C++ versions) and they ran correctly. 0.5) After these modifications to the JFFS2 filesystem, number of CRC errors dropped dramatically. (possible hint?) 1) Reproduced the 1559 buildroot jffs2 image, loaded it, same lots of CRC errors as first boot when we first received the unit 1.1) Was able to reproduce all previously observed behavior 1.2) u-boot fsinfo reported no errors 2) Disconnected NetmicroSD so the unit is only "motherboard" and consoleVX; reloaded JFFS2 image (Ymodem) 2.1) CRC checked memory image and flashed image, they are identical: 0x60132A18 2.2) Booted Linux, saw the JFFS2 header CRC errors 2.3) Rebooted down to u-boot, ran CRC check of flash image (thank goodness for crc.b command!), identical 0x60132A18 2.4) fsinfo looks OK U-boot produces consistent results in its interactions with the flash. I do not have a convenient tool for CRC32 checking the JFFS2 root filesystem image; if I find one, I'll check it on my host system. In the meantime, it appears that u-boot seems to work with the flash but Linux seems not to. Linux is SVN revision 1559 (now built on my host system), kernel 2.6.21gum unmodified from delivery. I have not loaded the buildroot-generated kernel onto the unit. I hope this info helps in the search for understanding! Len Samuelson ============ Here are some logs showing the loady/CRC results =========== GUM> loady a2000000 ## Ready for binary (ymodem) download to 0xA2000000 at 115200 bps... C## Total Size = 0x0090bc9c = 9485468 Bytes GUM> erase 40000 a5ffff ................................................................................. done Erased 81 sectors GUM> cp.b a2000000 40000 ${filesize} Copy to Flash... done GUM> help crc32 crc32 address count [addr] - compute CRC32 checksum [save at addr] -v address count crc - verify crc of memory area GUM> crc32 a2000000 ${filesize} CRC32 for a2000000 ... a290bc9b ==> 60132a18 GUM> crc32.b 40000 ${filesize} CRC32 for 00040000 ... 0094bc9b ==> 60132a18 GUM> boot Instruction Cache is ON Copying kernel to 0xa2000000 from 0x01f00000 (length 0x00100000)...done ## Booting image at a2000000 ... Image Name: uImage Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 992440 Bytes = 969.2 kB Load Address: a0008000 Entry Point: a0008000 OK <!-- Linux runs, has errors, I reboot --> U-Boot 1.2.0 (Nov 9 2007 - 15:22:26) - PXA270@600 MHz - 1559 *** Welcome to Gumstix *** DRAM: 128 MB Flash: 32 MB Using default environment Hit any key to stop autoboot: 0 GUM> crc32.b 40000 90bc9c CRC32 for 00040000 ... 0094bc9b ==> 60132a18 GUM> fsinfo ### filesystem type is JFFS2 Scanning JFFS2 FS: .......... done. Compression: NONE frag count: 618 compressed sum: 28363 uncompressed sum: 28363 Compression: ZERO frag count: 0 compressed sum: 0 uncompressed sum: 0 Compression: RTIME frag count: 26 compressed sum: 464 uncompressed sum: 20760 Compression: RUBINMIPS frag count: 0 compressed sum: 0 uncompressed sum: 0 Compression: COPY frag count: 0 compressed sum: 0 uncompressed sum: 0 Compression: DYNRUBIN frag count: 0 compressed sum: 0 uncompressed sum: 0 Compression: ZLIB frag count: 4664 compressed sum: 8810097 uncompressed sum: 17698831 GUM> boot Instruction Cache is ON Copying kernel to 0xa2000000 from 0x01f00000 (length 0x00100000)...done ## Booting image at a2000000 ... Image Name: uImage Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 992440 Bytes = 969.2 kB Load Address: a0008000 Entry Point: a0008000 OK Starting kernel ... <!-- linux runs, has errors, I reboot --> U-Boot 1.2.0 (Nov 9 2007 - 15:22:26) - PXA270@600 MHz - 1559 *** Welcome to Gumstix *** DRAM: 128 MB Flash: 32 MB Using default environment Hit any key to stop autoboot: 0 GUM> crc32.b 40000 90bc9c CRC32 for 00040000 ... 0094bc9b ==> 60132a18 GUM> Steve Sakoman wrote: > Have you tried checking the crc of the image after you download it and > comparing it with the crc from your build machine? That will > eliminate transfercorruption as a possibility. > > IIRC, you have a verdex 600? > > Steve > > On Jan 15, 2008 6:54 AM, Christian Ruocco <chr...@nd...> wrote: > >> Hi Steve/Guys, >> >> Got the touchscreen going! Loverly stuff. Thanks for the help. >> >> As for my JFFS2 CRC errors, I've tried the current image from >> >> >> http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html >> and I'm still getting TONS of CRC errors. In fact.. a hell of a lot more >> that the buildroot images (they were a bit smaller).. It seems to actually >> be quite variable. It seems every time I flash I get a different amount of >> errors but I always get them. The OE image I'm using also complains it can't >> create or find certain folders (dmesg) so I'm assuming the CRC errors >> indicate real damage. >> >> Is it possible that my terminal app's kermit implementation could be >> broken? I have tried hyperterm too and I still get CRC errors so I guess >> that rules that out. >> >> Any ideas? >> >> Xris. >> |
From: Dave H. <dhy...@gm...> - 2008-01-04 04:51:52
|
HI Ben, > I have a Verdex XL6P attached to a console-vx (R1753). It does not > seem to recognise when any USB devices are plugged in and it is > providing no power to the USB port. Since the power is hard-wired, the fact that you're not getting any voltage indicates that you've got a bad board. I seem to recall that somebody else got a board where the USB connection wasn't soldered down properly and the whole connector was lifted slightly off the board. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Grahame J. <gb...@th...> - 2008-01-09 21:44:03
|
I think you need to solder the wire. http://www.sakoman.net/oe/B10003.rew.png Steve - Will this be fixed in hardware in some new revision? Cheers Grahame Jordan Christian Ruocco wrote: > Hi Guys, > > I'm at my wits end here. At the suggestion of you forum chaps I've > installed open-embedded to try get some joy with the touchscreen since > the buildroot thing is lacking the driver, etc, etc.. Great its got the > i2c driver sorted and the TSC2003 driver finds the device 0x48, but then > it gives i2c error: timeout messages and the ts_calibrate app doesn't do > jack when I touch the calibrate cross hairs or any part of the screen > for that matter. Not only that, I get TONS of jffs2 CRC failures. Why > is the image corrupted? What am I doing wrong here? > > Does ANYONE have the touchscreen working? > > I read in one post that a wire needs to be soldered from some resistor > to another point on the consoleLCD-vx board. Is this truly necessary? > Could my hardware be broken? > > Thanks in advance. > > Xris. > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Steve S. <sa...@gm...> - 2008-01-09 21:49:59
|
> Steve - Will this be fixed in hardware in some new revision? Yes :-) |
From: Christian R. <chr...@nd...> - 2008-01-15 14:54:28
|
Hi Steve/Guys, Got the touchscreen going! Loverly stuff. Thanks for the help. As for my JFFS2 CRC errors, I've tried the current image from http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html and I'm still getting TONS of CRC errors. In fact.. a hell of a lot more that the buildroot images (they were a bit smaller).. It seems to actually be quite variable. It seems every time I flash I get a different amount of errors but I always get them. The OE image I'm using also complains it can't create or find certain folders (dmesg) so I'm assuming the CRC errors indicate real damage. Is it possible that my terminal app's kermit implementation could be broken? I have tried hyperterm too and I still get CRC errors so I guess that rules that out. Any ideas? Xris. Steve Sakoman wrote: > Yes, quite a few folks have functioning touchscreens! You do need to > solder the wire on your consoleLCD-vx board. See the image below for > where to solder it. > > http://www.sakoman.net/oe/B10003.rew.png > > As to the CRC errors, that shouldn't be happening. It might be bad hardware. > > Let's try to eliminate the possibility that your image is corrupted somehow. > > Could you reflash with one of the known good pre-built images? See > the following for where to get the image: > > http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html > > Try an image from revision 113. > > Steve > > On Jan 9, 2008 12:23 PM, Christian Ruocco <chr...@nd...> wrote: > >> Hi Guys, >> >> I'm at my wits end here. At the suggestion of you forum chaps I've >> installed open-embedded to try get some joy with the touchscreen since >> the buildroot thing is lacking the driver, etc, etc.. Great its got the >> i2c driver sorted and the TSC2003 driver finds the device 0x48, but then >> it gives i2c error: timeout messages and the ts_calibrate app doesn't do >> jack when I touch the calibrate cross hairs or any part of the screen >> for that matter. Not only that, I get TONS of jffs2 CRC failures. Why >> is the image corrupted? What am I doing wrong here? >> >> Does ANYONE have the touchscreen working? >> >> I read in one post that a wire needs to be soldered from some resistor >> to another point on the consoleLCD-vx board. Is this truly necessary? >> Could my hardware be broken? >> >> Thanks in advance. >> >> Xris. >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Felix D. <fe...@gm...> - 2008-01-15 23:09:43
|
Steve- It seems lots of people who received their 600MHz Verdex recently seem to be having JFFS2 CRC errors. It can't be that we're all doing transfers wrong (the errors were even there on the first boot using the factory-installed image on my verdex). Does Gumstix have any plans for addressing this issue (maybe a bad batch of memory chips came through)? Felix On Jan 16, 2008 1:21 AM, Steve Sakoman <sa...@gm...> wrote: > Have you tried checking the crc of the image after you download it and > comparing it with the crc from your build machine? That will > eliminate transfercorruption as a possibility. > > IIRC, you have a verdex 600? > > Steve > > On Jan 15, 2008 6:54 AM, Christian Ruocco <chr...@nd...> wrote: > > > > Hi Steve/Guys, > > > > Got the touchscreen going! Loverly stuff. Thanks for the help. > > > > As for my JFFS2 CRC errors, I've tried the current image from > > > > > > > http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html > > and I'm still getting TONS of CRC errors. In fact.. a hell of a lot > more > > that the buildroot images (they were a bit smaller).. It seems to > actually > > be quite variable. It seems every time I flash I get a different amount > of > > errors but I always get them. The OE image I'm using also complains it > can't > > create or find certain folders (dmesg) so I'm assuming the CRC errors > > indicate real damage. > > > > Is it possible that my terminal app's kermit implementation could be > > broken? I have tried hyperterm too and I still get CRC errors so I guess > > that rules that out. > > > > Any ideas? > > > > Xris. > > > > > > > > Steve Sakoman wrote: > > Yes, quite a few folks have functioning touchscreens! You do need to > > solder the wire on your consoleLCD-vx board. See the image below for > > where to solder it. > > > > http://www.sakoman.net/oe/B10003.rew.png > > > > As to the CRC errors, that shouldn't be happening. It might be bad > hardware. > > > > Let's try to eliminate the possibility that your image is corrupted > somehow. > > > > Could you reflash with one of the known good pre-built images? See > > the following for where to get the image: > > > > > http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html > > > > Try an image from revision 113. > > > > Steve > > > > On Jan 9, 2008 12:23 PM, Christian Ruocco <chr...@nd...> wrote: > > > > > > Hi Guys, > > > > I'm at my wits end here. At the suggestion of you forum chaps I've > > installed open-embedded to try get some joy with the touchscreen since > > the buildroot thing is lacking the driver, etc, etc.. Great its got the > > i2c driver sorted and the TSC2003 driver finds the device 0x48, but then > > it gives i2c error: timeout messages and the ts_calibrate app doesn't do > > jack when I touch the calibrate cross hairs or any part of the screen > > for that matter. Not only that, I get TONS of jffs2 CRC failures. Why > > is the image corrupted? What am I doing wrong here? > > > > Does ANYONE have the touchscreen working? > > > > I read in one post that a wire needs to be soldered from some resistor > > to another point on the consoleLCD-vx board. Is this truly necessary? > > Could my hardware be broken? > > > > Thanks in advance. > > > > Xris. > > > > > ------------------------------------------------------------------------- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Leonard S. <lsa...@co...> - 2008-01-16 00:50:01
|
Steve, My company received a Verdex X6LP (600 MHz), and its first boot showed both the long initial delay and lots of CRC errors that others are complaining about. Subsequent boots report similar numbers of errors but with a significantly reduced delay. It is a X6LP with plain (nonLCD) consoleVX and netmicroSD (without WiFi). The characteristic of CRC error reports appear to be unaffected by presence/absence of a 1G microSD in the slot. Successful attempts to modify the content of the JFFS2 filesystem *appear* to reduce the number of reported CRC errors, though I cannot guarantee that. In an attempt to see whether the system could run basic functionality even with the CRC error reports, I modified a few files (/etc/resolv.conf, /etc/modules to enable MMC and disable pcmcia), and though it took a few tries to get the changes to "take", once they did the number of reported CRC errors seem to fall dramatically. To try to narrow down the problem, I built a JFFS2 image from buildroot SVN revision 1559 (from /etc/gumstix-release number), and it behaves the same way as the first boot reports as near as I can tell (there are several hundred CRC error reports...). So the problem seems to be consistently produced using the mkfs.jffs2 that lives in buildroot revision 1559. Do you have a quick answer as to whether and/or when the mkfs.jffs2 tool has been updated since 1559? Perhaps it's worth going to a more recent buildroot. Len Samuelson Steve Sakoman wrote: > Have you tried checking the crc of the image after you download it and > comparing it with the crc from your build machine? That will > eliminate transfercorruption as a possibility. > > IIRC, you have a verdex 600? > > Steve > |
From: Dave H. <dhy...@gm...> - 2008-01-16 01:13:43
|
Hi Leonard, > My company received a Verdex X6LP (600 MHz), and its first boot showed > both the long initial delay and lots of CRC errors that others are > complaining about. Subsequent boots report similar numbers of errors > but with a significantly reduced delay. > > It is a X6LP with plain (nonLCD) consoleVX and netmicroSD (without > WiFi). The characteristic of CRC error reports appear to be unaffected > by presence/absence of a 1G microSD in the slot. Successful attempts to > modify the content of the JFFS2 filesystem *appear* to reduce the number > of reported CRC errors, though I cannot guarantee that. > > In an attempt to see whether the system could run basic functionality > even with the CRC error reports, I modified a few files > (/etc/resolv.conf, /etc/modules to enable MMC and disable pcmcia), and > though it took a few tries to get the changes to "take", once they did > the number of reported CRC errors seem to fall dramatically. > > To try to narrow down the problem, I built a JFFS2 image from buildroot > SVN revision 1559 (from /etc/gumstix-release number), and it behaves the > same way as the first boot reports as near as I can tell (there are > several hundred CRC error reports...). So the problem seems to be > consistently produced using the mkfs.jffs2 that lives in buildroot > revision 1559. > > Do you have a quick answer as to whether and/or when the mkfs.jffs2 tool > has been updated since 1559? Perhaps it's worth going to a more recent > buildroot. Several people have reported similar problems even using my 1533 image, for which I've never seen a CRC error (but I only have a 400 MHz verdex) Since the problem seems to be on the 600 MHz parts, I'm suspecting one of two causes: 1 - u-boot is misconfiguring the hardware, and the CRC errors are actually real, because the flash is being read out of spec and returning bad data 2 - There's some type of real hardware problem, either the PXA270 isn't really a 600MHz part, or the flash isn't rated for the faster bus, or there's just some bad parts. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Steve S. <sa...@gm...> - 2008-01-16 03:47:18
|
> It can't be that we're all doing transfers wrong I agree, I'm just trying to rule out possibilities. I'll work with Gordon to see if he can find any failing units in stock. It would help me get to the root problem more quickly if I had a unit to debug. Steve On Jan 15, 2008 3:09 PM, Felix Duvallet <fe...@gm...> wrote: > Steve- > > It seems lots of people who received their 600MHz Verdex recently seem to be > having JFFS2 CRC errors. It can't be that we're all doing transfers wrong > (the errors were even there on the first boot using the factory-installed > image on my verdex). Does Gumstix have any plans for addressing this issue > (maybe a bad batch of memory chips came through)? > > Felix > > > > > On Jan 16, 2008 1:21 AM, Steve Sakoman <sa...@gm...> wrote: > > > > > > > > Have you tried checking the crc of the image after you download it and > > comparing it with the crc from your build machine? That will > > eliminate transfercorruption as a possibility. > > > > IIRC, you have a verdex 600? > > > > Steve > > > > > > > > > > On Jan 15, 2008 6:54 AM, Christian Ruocco <chr...@nd...> wrote: > > > > > > Hi Steve/Guys, > > > > > > Got the touchscreen going! Loverly stuff. Thanks for the help. > > > > > > As for my JFFS2 CRC errors, I've tried the current image from > > > > > > > > > > http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html > > > and I'm still getting TONS of CRC errors. In fact.. a hell of a lot > more > > > that the buildroot images (they were a bit smaller).. It seems to > actually > > > be quite variable. It seems every time I flash I get a different amount > of > > > errors but I always get them. The OE image I'm using also complains it > can't > > > create or find certain folders (dmesg) so I'm assuming the CRC errors > > > indicate real damage. > > > > > > Is it possible that my terminal app's kermit implementation could be > > > broken? I have tried hyperterm too and I still get CRC errors so I guess > > > that rules that out. > > > > > > Any ideas? > > > > > > Xris. > > > > > > > > > > > > Steve Sakoman wrote: > > > Yes, quite a few folks have functioning touchscreens! You do need to > > > solder the wire on your consoleLCD-vx board. See the image below for > > > where to solder it. > > > > > > http://www.sakoman.net/oe/B10003.rew.png > > > > > > As to the CRC errors, that shouldn't be happening. It might be bad > hardware. > > > > > > Let's try to eliminate the possibility that your image is corrupted > somehow. > > > > > > Could you reflash with one of the known good pre-built images? See > > > the following for where to get the image: > > > > > > > http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html > > > > > > Try an image from revision 113. > > > > > > Steve > > > > > > On Jan 9, 2008 12:23 PM, Christian Ruocco <chr...@nd...> wrote: > > > > > > > > > Hi Guys, > > > > > > I'm at my wits end here. At the suggestion of you forum chaps I've > > > installed open-embedded to try get some joy with the touchscreen since > > > the buildroot thing is lacking the driver, etc, etc.. Great its got the > > > i2c driver sorted and the TSC2003 driver finds the device 0x48, but then > > > it gives i2c error: timeout messages and the ts_calibrate app doesn't do > > > jack when I touch the calibrate cross hairs or any part of the screen > > > for that matter. Not only that, I get TONS of jffs2 CRC failures. Why > > > is the image corrupted? What am I doing wrong here? > > > > > > Does ANYONE have the touchscreen working? > > > > > > I read in one post that a wire needs to be soldered from some resistor > > > to another point on the consoleLCD-vx board. Is this truly necessary? > > > Could my hardware be broken? > > > > > > Thanks in advance. > > > > > > Xris. > > > > > > > ------------------------------------------------------------------------- > > > Check out the new SourceForge.net Marketplace. > > > It's the best place to buy or sell services for > > > just about anything Open Source. > > > > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > > > _______________________________________________ > > > gumstix-users mailing list > > > gum...@li... > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > > > ------------------------------------------------------------------------- > > > Check out the new SourceForge.net Marketplace. > > > It's the best place to buy or sell services for > > > just about anything Open Source. > > > > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > > > _______________________________________________ > > > gumstix-users mailing list > > > gum...@li... > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Microsoft > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > > > > > > > > > _______________________________________________ > > > gumstix-users mailing list > > > gum...@li... > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > > > > > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: J. L. <len...@gm...> - 2008-09-25 23:46:03
|
Hi Guys, got any advance about this problem ? It still exists, i get tons of "CRC failed" messages during boot with a Verdex XL6P, NetWifiMicroSD, Breakout-vx. Sometimes, when i modify a file (e.g. /etc/network/interfaces to configure IP addresses), after the next reboot, the file seems to be unmodified... it's a flash problem ? LJ 2008/1/16 Steve Sakoman <sa...@gm...>: >> It can't be that we're all doing transfers wrong > > I agree, I'm just trying to rule out possibilities. > > I'll work with Gordon to see if he can find any failing units in > stock. It would help me get to the root problem more quickly if I had > a unit to debug. > > Steve > > On Jan 15, 2008 3:09 PM, Felix Duvallet <fe...@gm...> wrote: >> Steve- >> >> It seems lots of people who received their 600MHz Verdex recently seem to be >> having JFFS2 CRC errors. It can't be that we're all doing transfers wrong >> (the errors were even there on the first boot using the factory-installed >> image on my verdex). Does Gumstix have any plans for addressing this issue >> (maybe a bad batch of memory chips came through)? >> >> Felix >> >> >> >> >> On Jan 16, 2008 1:21 AM, Steve Sakoman <sa...@gm...> wrote: >> > >> > >> > >> > Have you tried checking the crc of the image after you download it and >> > comparing it with the crc from your build machine? That will >> > eliminate transfercorruption as a possibility. >> > >> > IIRC, you have a verdex 600? >> > >> > Steve >> > >> > >> > >> > >> > On Jan 15, 2008 6:54 AM, Christian Ruocco <chr...@nd...> wrote: >> > > >> > > Hi Steve/Guys, >> > > >> > > Got the touchscreen going! Loverly stuff. Thanks for the help. >> > > >> > > As for my JFFS2 CRC errors, I've tried the current image from >> > > >> > > >> > > >> http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html >> > > and I'm still getting TONS of CRC errors. In fact.. a hell of a lot >> more >> > > that the buildroot images (they were a bit smaller).. It seems to >> actually >> > > be quite variable. It seems every time I flash I get a different amount >> of >> > > errors but I always get them. The OE image I'm using also complains it >> can't >> > > create or find certain folders (dmesg) so I'm assuming the CRC errors >> > > indicate real damage. >> > > >> > > Is it possible that my terminal app's kermit implementation could be >> > > broken? I have tried hyperterm too and I still get CRC errors so I guess >> > > that rules that out. >> > > >> > > Any ideas? >> > > >> > > Xris. >> > > >> > > >> > > >> > > Steve Sakoman wrote: >> > > Yes, quite a few folks have functioning touchscreens! You do need to >> > > solder the wire on your consoleLCD-vx board. See the image below for >> > > where to solder it. >> > > >> > > http://www.sakoman.net/oe/B10003.rew.png >> > > >> > > As to the CRC errors, that shouldn't be happening. It might be bad >> hardware. >> > > >> > > Let's try to eliminate the possibility that your image is corrupted >> somehow. >> > > >> > > Could you reflash with one of the known good pre-built images? See >> > > the following for where to get the image: >> > > >> > > >> http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/32.html >> > > >> > > Try an image from revision 113. >> > > >> > > Steve >> > > >> > > On Jan 9, 2008 12:23 PM, Christian Ruocco <chr...@nd...> wrote: >> > > >> > > >> > > Hi Guys, >> > > >> > > I'm at my wits end here. At the suggestion of you forum chaps I've >> > > installed open-embedded to try get some joy with the touchscreen since >> > > the buildroot thing is lacking the driver, etc, etc.. Great its got the >> > > i2c driver sorted and the TSC2003 driver finds the device 0x48, but then >> > > it gives i2c error: timeout messages and the ts_calibrate app doesn't do >> > > jack when I touch the calibrate cross hairs or any part of the screen >> > > for that matter. Not only that, I get TONS of jffs2 CRC failures. Why >> > > is the image corrupted? What am I doing wrong here? >> > > >> > > Does ANYONE have the touchscreen working? >> > > >> > > I read in one post that a wire needs to be soldered from some resistor >> > > to another point on the consoleLCD-vx board. Is this truly necessary? >> > > Could my hardware be broken? >> > > >> > > Thanks in advance. >> > > >> > > Xris. >> > > >> > > >> ------------------------------------------------------------------------- >> > > Check out the new SourceForge.net Marketplace. >> > > It's the best place to buy or sell services for >> > > just about anything Open Source. >> > > >> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace >> > > _______________________________________________ >> > > gumstix-users mailing list >> > > gum...@li... >> > > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > >> > > >> > > >> ------------------------------------------------------------------------- >> > > Check out the new SourceForge.net Marketplace. >> > > It's the best place to buy or sell services for >> > > just about anything Open Source. >> > > >> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace >> > > _______________________________________________ >> > > gumstix-users mailing list >> > > gum...@li... >> > > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > >> > > >> > > >> > > >> ------------------------------------------------------------------------- >> > > This SF.net email is sponsored by: Microsoft >> > > Defy all challenges. Microsoft(R) Visual Studio 2008. >> > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> > >> > >> > >> > >> > > _______________________________________________ >> > > gumstix-users mailing list >> > > gum...@li... >> > > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > >> > > >> > >> > ------------------------------------------------------------------------- >> > >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> > >> > >> > >> > _______________________________________________ >> > gumstix-users mailing list >> > gum...@li... >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |