Re: [ECOS] Video mode code / eCos demo

["Kumanan" <kumanan at mindless dot com>]

Hello,

I am curious about the VESA data that the program did print out before it
crashed.

I suspect the crash is because the program I am running (gfxmode.c from the
HAL sources) assumes it will find meaningful VESA information and my board
does not quite supply the correct information.

I will however run the debugger to validate my suspicion regarding the
crash.

Kumanan


----- Original Message ----- 
From: "Gary Thomas" <gary@mlbassoc.com>
To: "Kumanan" <kumanan@mindless.com>
Cc: "David N. Welton" <davidw@dedasys.com>; "eCos Discussion"
<ecos-discuss@sources.redhat.com>
Sent: Sunday, August 24, 2003 7:35 AM
Subject: Re: [ECOS] Video mode code / eCos demo


> On Sat, 2003-08-23 at 18:52, Kumanan wrote:
> > Hello,
> >
> > So, I found the gfxmode.c test app and ran it after telling RedBoot to
use
> > video mode 0x110 (not that that should matter).
> >
> > Here's the output I got, which leads to suspect that either I messed
> > something up, or the board does not support VBE for VESA mode setting.
Can
> > someone clarify for me?
> >
> > (For those who care, I am trying to work with a STB3036N from GCT
Allwell
> > technologies, which is a Geode x86 platform using the TVIA CyberPro 5005
> > chip for graphics & video.)
> >
> > -----8<----------
> > RedBoot> load -v -m yMODEM
> > CCEntry point: 0x00108000, address range: 0x00108000-0x001201e0
> > xyzModem - CRC mode, 2(SOH)/278(STX)/0(CAN) packets, 5 retries
> > RedBoot> go
> > VESA info:
> > version ffff
> > OEM  Òç
> > total memory 4194240K
> > oem software rev ffff
> > OEM vendor  Òç
> > OEM product name  Òç
> > OEM product revision  Òç
> > Capabilities: ff, ff, ff, ff
> > $T0bthread:00000002;08:dc861000;04:843d1200;#c7
> > --------------------------
> >
>
> This says that your application has crashed and it's waiting for
> you to discover why!  Just disconnect your "terminal" (minicom or
> whatever) and then connect to it with GDB.  Then you can explore
> what's going on.  e.g. on a Linux box, one might do it this way:
>   % i386-elf-gdb -nw APPLICATION
>   (gdb) tar rem /dev/ttyS0
>   (gdb) info reg
>   (gdb) bt
> where "APPLICATION" is the name of the ELF application that you
> downloaded and ran.  The last two commands will tell you something
> about where in the program it failed and how you got there.
>
> -- 
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
>


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss