From: Darren G. <ts...@ya...> - 2005-02-01 03:15:04
|
Craig, Have you had any luck tracking down the ucb1400 reset issue? I'm making good progress on my app and will hopefully be ready to test it on the gumstix in a week or two. I got my tweener and was finally able to experiment a bit with the Audiostix. Besides hearing the resets that you mentioned, I tried running several PortAudio test programs. PortAudio is able to open the OSS device fine, but audio output seems to get hosed after one shot. I execute a test program, and I can never get audio output again until I reboot. Sometimes an example program will hang mysteriously. These programs all work fine on my SUSE and OS X boxes so I figure there must be something gumstix specific going south. Is there a howto yet for doing remote gdb on the gumstix? Or could you give me a pointer to an applicable generic remote gdb howto/tutorial? thanks, darren |
From: Dave H. <dhy...@gm...> - 2005-02-01 03:23:51
|
Hi Darren, > Is there a howto yet for doing remote gdb on the gumstix? Or could you > give me a pointer to an applicable generic remote gdb howto/tutorial? There are a couple of things that you need to do: 1 - Compile gdb on your host, but targeted for the gumstix 2 - Cross-compile gdbserver for the gumstix. I've done this for other ARM platforms, but not yet for the gumstix. Copy gdbserver to the gumstix. You then run gdbserver and tell it to launch your program. You can connect to gdbserver using a serial port or a TCP/IP connection. When I get around to doing this myself I'll write up a howto (unless somebody beats me to it) I also see kgdb is available for 2.6 now, which is really nice for debugging stuff in the kernel. Dave Hylands |
From: Craig H. <cr...@hu...> - 2005-02-01 05:11:57
|
On Jan 31, 2005, at 7:15 PM, Darren Gibbs wrote: > Craig, > > Have you had any luck tracking down the ucb1400 reset issue? I'm > making good progress on my app and will hopefully be ready to test it > on the gumstix in a week or two. Not yet. I'm trying to find a local buddy who has a digital scope which I can borrow to watch the AC97 bus and see if there is some rogue "write to register 0" command being sent to the UCB1400. As far as I can tell, the kernel doesn't think it's sending this, but it's possible that there's either some rogue writing going on, or that there's just noise on the line (less likely I think). Until I actually scope the thing though, I have pretty well exhausted all my ideas on what might be going on. > I got my tweener and was finally able to experiment a bit with the > Audiostix. Besides hearing the resets that you mentioned, I tried > running several PortAudio test programs. PortAudio is able to open > the OSS device fine, but audio output seems to get hosed after one > shot. I execute a test program, and I can never get audio output > again until I reboot. Sometimes an example program will hang > mysteriously. These programs all work fine on my SUSE and OS X boxes > so I figure there must be something gumstix specific going south. I added some extra info to the dump in /proc/drivers/ac97/ucb1400 (I think that's the path -- don't have an audiostix fired up right now...) which basically gives a dump of various AC97 registers -- you can tell the thing's reset when all the register values abruptly change. Could be that the reset is happening when you're doing whatever your app is doing, but it's just not making the "click" one can normally hear across the reset. Check /proc/... to see if it's in fact reset itself. C |
From: Darren G. <ts...@ya...> - 2005-02-06 01:11:40
|
On Jan 31, 2005, at 9:11 PM, Craig Hughes wrote: > I added some extra info to the dump in /proc/drivers/ac97/ucb1400 /proc/driver/ucb1400/ac97 Cool... One thing that I reckon you've noticed is that the ucb1400 seems to be fine if you don't play any audio. I've left it sitting for 5 minutes or so without a reset. When I try to play audio, it resets within 10-15 seconds. Don't know if this is helpful, but figured I'd mention it. |
From: Craig H. <cr...@hu...> - 2005-02-06 02:50:26
|
On Feb 5, 2005, at 5:11 PM, Darren Gibbs wrote: > > On Jan 31, 2005, at 9:11 PM, Craig Hughes wrote: >> I added some extra info to the dump in /proc/drivers/ac97/ucb1400 > > /proc/driver/ucb1400/ac97 > > Cool... > > One thing that I reckon you've noticed is that the ucb1400 seems to be > fine if you don't play any audio. I've left it sitting for 5 minutes > or so without a reset. When I try to play audio, it resets within > 10-15 seconds. Don't know if this is helpful, but figured I'd mention > it. Yup, until first audio is played, there's not problem. You can even record, change mixer levels, etc without triggering the reset. But some random time interval after the first time you play anything, the reset triggers. Sometimes it's 10-15 seconds, sometimes it's practically instantaneous, sometimes it's not for 5-10 minutes. C |