[ECOS] redboot problem

[ECOS] redboot problem

[Kaustubh Purandare]

Hi,

I am using redboot for iX86 PC. I have created a bootable floppy 
for booting the PC with eCos.

There is one problem I am facing whenever I load any thread for 
e.g. tcp_lo_test.exe, after executing correctly the redboot PC 
hangs. I always need to reboot the PC  with redboot to load any 
other thread.

Is this the correct procedure? Do we always need to reboot the PC 
each time with redboot for running different threads?

Note: I am using latest sources / tools rom the repository.

Regards,

Kaustubh



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

Re: [ECOS] redboot problem

[Jonathan Larmour]

Kaustubh Purandare wrote:
> 
> Hi,
> 
> I am using redboot for iX86 PC. I have created a bootable floppy
> for booting the PC with eCos.
> 
> There is one problem I am facing whenever I load any thread for
> e.g. tcp_lo_test.exe, after executing correctly the redboot PC
> hangs. I always need to reboot the PC  with redboot to load any
> other thread.
> 
> Is this the correct procedure? Do we always need to reboot the PC
> each time with redboot for running different threads?

In general yes, as a new program can't start up when the hardware has been
left in an unknown state.

You could _try_ setting a breakpoint on cyg_test_exit, and then when it is
reached, just quitting GDB, and then run GDB again with a new program. But
it may not work at all, or may not work reliably. The only way to be sure
is to reboot each time.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

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

RE: [ECOS] Redboot problem

[Oscar]

Well...now work fine. In the last version of redboot.cdl the option "Allow
redboot to support disk" is ON to default. I don't know the reason but this
option give me the fail. With the option OFF all work fine. I add the flash
support too and seem run well. If somebody can help me to understand why my
platform was fail ...
OSCAR

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of Oscar
Sent: mercoledì 26 novembre 2003 23.02
To: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Redboot problem


I have realized that the last version of redboot.cdl file give me the
problem. Now I must unterstand why. OSCAR

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of Oscar
Sent: mercoledì 26 novembre 2003 15.39
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Redboot problem


Hi all,
i've get trouble with redboot from last package update. I builted my last
fine redboot version the 01/11/2003. Now, immediately terminated the
application download in RAM by GDB, GDB show me the follow message: "Program
received signal SIGBUS, BUS error" I have tried to check the redboot's
changelog file and tried to load a older version of main.c but nothing
change. At the moment i'm using redboot without NET and FLASH support. Have
you any idea? THANKS OSCAR 



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



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



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

RE: [ECOS] Redboot problem

[Oscar]

I have realized that the last version of redboot.cdl file give me the
problem.
Now I must unterstand why.
OSCAR

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of Oscar
Sent: mercoledì 26 novembre 2003 15.39
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Redboot problem


Hi all,
i've get trouble with redboot from last package update. I builted my last
fine redboot version the 01/11/2003. Now, immediately terminated the
application download in RAM by GDB, GDB show me the follow message:
"Program received signal SIGBUS, BUS error" I have tried to check the
redboot's  changelog file and tried to load a older version of main.c but
nothing change. At the moment i'm using redboot without NET and FLASH
support. Have you any idea? THANKS OSCAR 



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



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

[ECOS] Redboot problem

[Oscar]

Hi all,
i've get trouble with redboot from last package update. I builted my last
fine redboot version the 01/11/2003.
Now, immediately terminated the application download in RAM by GDB, GDB show
me the follow message:  "Program received signal SIGBUS, BUS error"
I have tried to check the redboot's  changelog file and tried to load a
older version of main.c but nothing change.
At the moment i'm using redboot without NET and FLASH support.
Have you any idea?
THANKS
OSCAR 



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

Re: [ECOS] redboot problem

[Jonathan Larmour]

flagship wrote:
> 
> i've got my ethernet card's PCI id: 2449
> it's seem to be NOT supported, isn't it?

It appears that it is compatible, so you will need to update the source for
the driver with this PCI ID. By looking at the Linux driver, the same is
true of ID 0x1029 so I'll add that to the main sources too.

Here's what I changed:


Index: src/if_i82559.c
===================================================================
RCS file: /home/cvs/ecc/ecc/devs/eth/intel/i82559/current/src/if_i82559.c,v
retrieving revision 1.40
diff -u -5 -p -r1.40 if_i82559.c
--- src/if_i82559.c	2002/01/04 01:23:14	1.40
+++ src/if_i82559.c	2002/01/10 07:51:38
@@ -2665,11 +2665,13 @@ find_82559s_match_func( cyg_uint16 v, cy
 {
     return
         (0x8086 == v) &&
         ((0x1030 == d) ||
          (0x1229 == d) ||
-         (0x1209 == d));
+         (0x1209 == d) ||
+         (0x1029 == d) ||
+         (0x2449 == d));
 }
 
 static int
 pci_init_find_82559s( void )
 {

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

Re: [ECOS] redboot problem

[flagship]

i've got my ethernet card's PCI id: 2449
it's seem to be NOT supported, isn't it?

----- Original Message ----- 
From: "Jonathan Larmour" <jlarmour@redhat.com>
To: "flagship" <ecos-mu@263.net>
Cc: "Gustav Kälvesten" <gustav.kalvesten@axis.com>; <ecos-discuss@sources.redhat.com>
Sent: Tuesday, January 08, 2002 10:51 PM
Subject: Re: [ECOS] redboot problem


> flagship wrote:
> > 
> > Thanks a lot.
> > But since it can't work yet, i think is it somewhat configuration problem?
> > Here's my redboot build process, are there any problems?
> > #ecosconfig new pc redboot
> > #ecosconfig import $ECOS_REPOSITORY/hal/i386/pc/current/misc/redboot_FLOOPY.ecm
> > #ecosconfig tree
> > #make
> > #dd conv=sync if=install/bin/redboot.bin of=/dev/fd0
> > 
> > Then, when i use the floopy to boot, it said "no network interfaces found"....... :( Are there any extra configurations should be done?
> 
> That should be sufficient. Perhaps it is using a different PCI ID that the
> driver doesn't recognise. The driver assumes a vendor ID of 0x8086 and a
> device ID of either 0x1030, 0x1229 or 0x1209. Do you know its PCI ID? You
> can see everything on the PCI bus by running the pci1 eCos test.
> 
> You could also enable the CYGDBG_DEVS_ETH_INTEL_I82559_CHATTER CDL option
> and rebuild redboot. That might give more info.
> 
> Jifl
> -- 
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

Re: [ECOS] redboot problem

[flagship]

Thanks and thanks again...:) I'll try it immediately.

----- Original Message ----- 
From: "Jonathan Larmour" <jlarmour@redhat.com>
To: "flagship" <ecos-mu@263.net>
Cc: "Gustav Kälvesten" <gustav.kalvesten@axis.com>; <ecos-discuss@sources.redhat.com>
Sent: Tuesday, January 08, 2002 10:51 PM
Subject: Re: [ECOS] redboot problem


> flagship wrote:
> > 
> > Thanks a lot.
> > But since it can't work yet, i think is it somewhat configuration problem?
> > Here's my redboot build process, are there any problems?
> > #ecosconfig new pc redboot
> > #ecosconfig import $ECOS_REPOSITORY/hal/i386/pc/current/misc/redboot_FLOOPY.ecm
> > #ecosconfig tree
> > #make
> > #dd conv=sync if=install/bin/redboot.bin of=/dev/fd0
> > 
> > Then, when i use the floopy to boot, it said "no network interfaces found"....... :( Are there any extra configurations should be done?
> 
> That should be sufficient. Perhaps it is using a different PCI ID that the
> driver doesn't recognise. The driver assumes a vendor ID of 0x8086 and a
> device ID of either 0x1030, 0x1229 or 0x1209. Do you know its PCI ID? You
> can see everything on the PCI bus by running the pci1 eCos test.
> 
> You could also enable the CYGDBG_DEVS_ETH_INTEL_I82559_CHATTER CDL option
> and rebuild redboot. That might give more info.
> 
> Jifl
> -- 
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

Re: [ECOS] redboot problem

[Jonathan Larmour]

flagship wrote:
> 
> Thanks a lot.
> But since it can't work yet, i think is it somewhat configuration problem?
> Here's my redboot build process, are there any problems?
> #ecosconfig new pc redboot
> #ecosconfig import $ECOS_REPOSITORY/hal/i386/pc/current/misc/redboot_FLOOPY.ecm
> #ecosconfig tree
> #make
> #dd conv=sync if=install/bin/redboot.bin of=/dev/fd0
> 
> Then, when i use the floopy to boot, it said "no network interfaces found"....... :( Are there any extra configurations should be done?

That should be sufficient. Perhaps it is using a different PCI ID that the
driver doesn't recognise. The driver assumes a vendor ID of 0x8086 and a
device ID of either 0x1030, 0x1229 or 0x1209. Do you know its PCI ID? You
can see everything on the PCI bus by running the pci1 eCos test.

You could also enable the CYGDBG_DEVS_ETH_INTEL_I82559_CHATTER CDL option
and rebuild redboot. That might give more info.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

Re: [ECOS] redboot problem

[flagship]

Thanks a lot.
But since it can't work yet, i think is it somewhat configuration problem?
Here's my redboot build process, are there any problems?
#ecosconfig new pc redboot
#ecosconfig import $ECOS_REPOSITORY/hal/i386/pc/current/misc/redboot_FLOOPY.ecm
#ecosconfig tree
#make
#dd conv=sync if=install/bin/redboot.bin of=/dev/fd0

Then, when i use the floopy to boot, it said "no network interfaces found"....... :( Are there any extra configurations should be done?

----- Original Message ----- 
From: "Gustav Kälvesten" <gustav.kalvesten@axis.com>
To: "'flagship'" <ecos-mu@263.net>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Tuesday, January 08, 2002 10:27 AM
Subject: RE: [ECOS] redboot problem


> Hi,
> 
> My guess is that this card is supported:
> http://www.intel.com/network/connectivity/products/pro100_dsktop.htm
> It specifically states 82559 controller on the front page.
> 
> But also the VE card says in the technical specifications that 82559 is used:
> http://www.intel.com/english/network/connectivity/products/pro100ve_adapter.htm
> 
> So you would think it should work as well.
> 
> - Gustav
> 
> > -----Original Message-----
> > From: flagship [mailto:ecos-mu@263.net]
> > Sent: den 8 januari 2002 11:06
> > To: Jonathan Larmour
> > Cc: ecos-discuss@sources.redhat.com
> > Subject: Re: [ECOS] redboot problem
> > 
> > 
> > 
> > ----- Original Message ----- 
> > From: "Jonathan Larmour" <jlarmour@redhat.com>
> > To: "flagship" <ecos-mu@263.net>
> > Cc: <ecos-discuss@sources.redhat.com>
> > Sent: Tuesday, January 08, 2002 4:30 AM
> > Subject: Re: [ECOS] redboot problem
> > 
> > 
> > > flagship wrote:
> > > > 
> > > > Hello,
> > > >    I'm building a redboot startup floopy for i386 pc. I 
> > followed the instructions in redboot user's guide and 
> > imported the redboot_FLOOPY.ecm(it comes from the ecos CVS 
> > server), then make without any errors. But, when i use the 
> > floopy to boot my pc, it said "no network interfaces found", 
> > why? There's a Intel Pro 100 VE on-board ethernet adapter in my box.
> > > 
> > > Assuming that card isn't based on the 82559 chipset, it's 
> > not a supported
> > > card as there is no driver (yet). What chipset does it have?
> > I'm not sure. HOWEVER,  I have included in the 
> > CYGPKG_DEVS_ETH_I386_PC_I82559 package, and in it's comment, 
> > it said it's for "Standard PC with EtherPro 10/100 ethernet 
> > device"(isn't it my card?). So I think that card should base 
> > on the 82559 chipset and could be supported.
> >

RE: [ECOS] redboot problem

[Gustav Kälvesten]

Hi,

My guess is that this card is supported:
http://www.intel.com/network/connectivity/products/pro100_dsktop.htm
It specifically states 82559 controller on the front page.

But also the VE card says in the technical specifications that 82559 is used:
http://www.intel.com/english/network/connectivity/products/pro100ve_adapter.htm

So you would think it should work as well.

- Gustav

> -----Original Message-----
> From: flagship [mailto:ecos-mu@263.net]
> Sent: den 8 januari 2002 11:06
> To: Jonathan Larmour
> Cc: ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] redboot problem
> 
> 
> 
> ----- Original Message ----- 
> From: "Jonathan Larmour" <jlarmour@redhat.com>
> To: "flagship" <ecos-mu@263.net>
> Cc: <ecos-discuss@sources.redhat.com>
> Sent: Tuesday, January 08, 2002 4:30 AM
> Subject: Re: [ECOS] redboot problem
> 
> 
> > flagship wrote:
> > > 
> > > Hello,
> > >    I'm building a redboot startup floopy for i386 pc. I 
> followed the instructions in redboot user's guide and 
> imported the redboot_FLOOPY.ecm(it comes from the ecos CVS 
> server), then make without any errors. But, when i use the 
> floopy to boot my pc, it said "no network interfaces found", 
> why? There's a Intel Pro 100 VE on-board ethernet adapter in my box.
> > 
> > Assuming that card isn't based on the 82559 chipset, it's 
> not a supported
> > card as there is no driver (yet). What chipset does it have?
> I'm not sure. HOWEVER,  I have included in the 
> CYGPKG_DEVS_ETH_I386_PC_I82559 package, and in it's comment, 
> it said it's for "Standard PC with EtherPro 10/100 ethernet 
> device"(isn't it my card?). So I think that card should base 
> on the 82559 chipset and could be supported.
> 

Re: [ECOS] redboot problem

[flagship]

----- Original Message ----- 
From: "Jonathan Larmour" <jlarmour@redhat.com>
To: "flagship" <ecos-mu@263.net>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Tuesday, January 08, 2002 4:30 AM
Subject: Re: [ECOS] redboot problem


> flagship wrote:
> > 
> > Hello,
> >    I'm building a redboot startup floopy for i386 pc. I followed the instructions in redboot user's guide and imported the redboot_FLOOPY.ecm(it comes from the ecos CVS server), then make without any errors. But, when i use the floopy to boot my pc, it said "no network interfaces found", why? There's a Intel Pro 100 VE on-board ethernet adapter in my box.
> 
> Assuming that card isn't based on the 82559 chipset, it's not a supported
> card as there is no driver (yet). What chipset does it have?
I'm not sure. HOWEVER,  I have included in the CYGPKG_DEVS_ETH_I386_PC_I82559 package, and in it's comment, it said it's for "Standard PC with EtherPro 10/100 ethernet device"(isn't it my card?). So I think that card should base on the 82559 chipset and could be supported.

Re: [ECOS] redboot problem

[Jonathan Larmour]

flagship wrote:
> 
> Hello,
>    I'm building a redboot startup floopy for i386 pc. I followed the instructions in redboot user's guide and imported the redboot_FLOOPY.ecm(it comes from the ecos CVS server), then make without any errors. But, when i use the floopy to boot my pc, it said "no network interfaces found", why? There's a Intel Pro 100 VE on-board ethernet adapter in my box.

Assuming that card isn't based on the 82559 chipset, it's not a supported
card as there is no driver (yet). What chipset does it have?

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

[ECOS] redboot problem

[flagship]

Hello,
   I'm building a redboot startup floopy for i386 pc. I followed the instructions in redboot user's guide and imported the redboot_FLOOPY.ecm(it comes from the ecos CVS server), then make without any errors. But, when i use the floopy to boot my pc, it said "no network interfaces found", why? There's a Intel Pro 100 VE on-board ethernet adapter in my box.

Thanks for any answer!