It might be worth a shot to look carefully at the palo board to see if there is any sign of shorting. I recently received a Chestnut board that had the SPI clk shorted to ground for the TS controller. I've seen other people on the list mention finding shorts in various places. If you have access to an oscilloscope, it might be good to check the usual suspects (like the pixel clock, or the LCD EN line). Then again, it could also be software like you said...

Hope this helps,

On Wed, Dec 30, 2009 at 1:50 PM, Trevor Woerner <> wrote:
I don't know if this is related or not, but I also seem to get some
JFFS warnings and notices as the device sits idle:

|       |                  .-.
|   |   |-----.-----.-----.| |   .----..-----.-----.
|       |     | __  |  ---'| '--.|  .-'|     |     |
|   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
'---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
               -'  |

The Angstrom Distribution overo ttyS2

Angstrom 2009.X-test-20090620 overo ttyS2

overo login: JFFS2 warning: (1810) jffs2_sum_write_data: Not enough
space for summary, padsize = -11
JFFS2 notice: (1073) check_node_data: wrong data CRC in data node at
0x014af4e8: read 0x2fc39fe6, c.

This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
gumstix-users mailing list