I have yet to find a solution to this problem. I've found threads after I did
it saying not to do it.
When I try to reinstall Angstrom I keep getting errors. I tried tftp and SD
but nothing seems to work.
I'm very new to Gumstix and Linux and I need some help to get this up and
View this message in context: http://gumstix.8.n6.nabble.com/opkg-update-upgrade-screwed-up-my-system-tp4958459.html
Sent from the Gumstix mailing list archive at Nabble.com.
From: Keane, Ben (STRX) <ben.keane@ka...> - 2012-05-08 06:46:57
I am trying to use UART3_CTS / GPIO163 as an GPIO pin configured as output and the value set high. Currently I change the muxing and set the pin high via uboot.
I have recently upgraded my Linux Kernel from 2.6.32 to 3.3.0. The kernel used to leave this pin along during boot, but the new kernel changes the muxing/value. I am unable to find where in the kernel it is changing the muxing. I of course could add more code that changes it back (like in the arch/arm/mach-omap2/board-overo.c in the overo_init() function, but this causes the pin to pulse low, and then back high and as this line is used as the power latch for the supply on a custom pcb it won't work.
I believe I have worked out it is happening sometime between the .init_early and the .init_machine functions.
So I am hoping someone might have already worked out where the kernel is changing the muxing for this particular ball?
Thanks in advance,
PROPRIETARY: This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the authority by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail.
Get latest updates about Open Source Projects, Conferences and News.