This setup you describe-- right now you are just trying
to talk to it via ADK ARM debug? We got that far,
using ARM 2.11a sdk on a windows 98 box..
We had a similar problem with
no response from angel and switched all the baudrate
settings to 9600. Now we can run the test apps.
Or we could. The brutus board seems to taken a
hike south. The numeric LED is showing a 7 now
everytime we power up and we can't make a connection
to it either with the debugger SDK or angleboot on linux.
Anyone seen the 7? It's not documented anyplace that I can
find.
Thanks,
Dave
-----Original Message-----
From: Vasant Ramasubramanian <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, October 07, 1999 12:27 AM
Subject: Brutus Woes, any help?
>Hello all!
>
>I'm trying to setup my Brutus board to run the basic test programs that
>come with the Kit (requires the SDT 2.50 to run, which I have) and I am
>not even sure that my Brutus is working. From all the documentation I've
>read (what little is provided) connecting the null-modem cable to J23 on
>the Brutus and to a COM port on the PC should at least bring up a message
>about Angel running on Brutus, right?
>
>I used 9600,8,N,1 and 115200,8.N,1 for the serial port settings yet when I
>turned Brutus on, I didn't get anything. I'm certain the PC is fine, the
>serial port is fine, the null modem cable is fine, I've checked those
>things out. I also made sure all the dip swtiches were in the default
>position specified in the .pdf documentation for Brutus. Any ideas?
>
>I haven't gotten to using angelboot.tgz or putting my RAM DISK on there or
>anything like that.
>
>For the ARM SDT 2.5 portion, I was using Win95 OSR2.
>
>I'm running Red Hat 6.0 for the Linux end of things, hopefully if my
>Brutus is working I can get it to boot Linux...
>
>I'd appreciate any help/suggestions.
>
>Thanks, Vasant.
>
>unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
>
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
