RE: [ECOS] RedBoot, Ethernet, MBX860

RE: [ECOS] RedBoot, Ethernet, MBX860

[Anthony Massa]

After adding the patches and then rebuilding my eCos image, the Ethernet
seems to be working properly.  I get through the quicc_eth_init routine and
then I see the output for the DHCP code that correctly receives an IP
address from my DHCP server.

However, the code always seems to fail at the cyg_libc_time_getzoneoffsets
routine in time.inl.  I get an Illegal Instruction dialog box that pops up
in Insight.  After I dismiss the dialog box the code is stopped and will not
continue to run.

Do you know where this is called from?

Do you know why it might be failing?  Do I need real-time clock support on
my MBX board?

I have seen the $ strings below as well when running from RedBoot.  I have
been using GDB/Insight to download and run my code.  I haven't been running
just using RedBoot.  It seems as though there is some confusion as to
whether the Ethernet port or serial port is to be used for debugging.

Thanks for the help.

--Anthony


>
>On 08-May-2001 Natarajan, Mekala (CTS) wrote:
>> I applied the patch which was sent yesterday.
>> Still i face the same problem.
>> 
>> Mr.Anthony, are you able to do ethernet debugging after 
>adding the patch.
>> 
>> 
>> RedBoot> go 20000
>> 
>$T04thread:00000000;40:00004e20;01:000055f4;#53$T04thread:00000
>000;40:00004e
>> 20;0
>> 
>1:000055f4;#53$T04thread:00000000;40:00004e20;01:000055f4;#53$T
>04thread:0000
>> 0000
>> ;40:00004e20;01:000055f4;#53
>> 
>
>Odd, this works fine for me (I just re-did it to make sure).
>
>Note: in order for the the patches to have an effect, you need 
>to update your
>configuration.
>  % ecosconfig tree
>  % make clean;make
>

RE: [ECOS] RedBoot, Ethernet, MBX860

[Gary Thomas]

On 08-May-2001 Anthony Massa wrote:
> 
> After adding the patches and then rebuilding my eCos image, the Ethernet
> seems to be working properly.  I get through the quicc_eth_init routine and
> then I see the output for the DHCP code that correctly receives an IP
> address from my DHCP server.
> 
> However, the code always seems to fail at the cyg_libc_time_getzoneoffsets
> routine in time.inl.  I get an Illegal Instruction dialog box that pops up
> in Insight.  After I dismiss the dialog box the code is stopped and will not
> continue to run.
> 
> Do you know where this is called from?
> 


At least you're making some progress here.  I'm not sure what the problem is
though.  Perhaps you could send me the executable (privately, not to the list!)
and I'll give it a glance.

> Do you know why it might be failing?  Do I need real-time clock support on
> my MBX board?
> 

No.

> I have seen the $ strings below as well when running from RedBoot.  I have
> been using GDB/Insight to download and run my code.  I haven't been running
> just using RedBoot.  It seems as though there is some confusion as to
> whether the Ethernet port or serial port is to be used for debugging.
> 

This was caused by confusion between the eCos program and the debug environment.
That's what the patches should have fixed.

> Thanks for the help.
> 
> --Anthony
> 
> 
>>
>>On 08-May-2001 Natarajan, Mekala (CTS) wrote:
>>> I applied the patch which was sent yesterday.
>>> Still i face the same problem.
>>> 
>>> Mr.Anthony, are you able to do ethernet debugging after 
>>adding the patch.
>>> 
>>> 
>>> RedBoot> go 20000
>>> 
>>$T04thread:00000000;40:00004e20;01:000055f4;#53$T04thread:00000
>>000;40:00004e
>>> 20;0
>>> 
>>1:000055f4;#53$T04thread:00000000;40:00004e20;01:000055f4;#53$T
>>04thread:0000
>>> 0000
>>> ;40:00004e20;01:000055f4;#53
>>> 
>>
>>Odd, this works fine for me (I just re-did it to make sure).
>>
>>Note: in order for the the patches to have an effect, you need 
>>to update your
>>configuration.
>>  % ecosconfig tree
>>  % make clean;make
>>

RE: [ECOS] RedBoot, Ethernet, MBX860

[Gary Thomas]

On 08-May-2001 Natarajan, Mekala (CTS) wrote:
> I applied the patch which was sent yesterday.
> Still i face the same problem.
> 
> Mr.Anthony, are you able to do ethernet debugging after adding the patch.
> 
> 
> RedBoot> go 20000
> $T04thread:00000000;40:00004e20;01:000055f4;#53$T04thread:00000000;40:00004e
> 20;0
> 1:000055f4;#53$T04thread:00000000;40:00004e20;01:000055f4;#53$T04thread:0000
> 0000
> ;40:00004e20;01:000055f4;#53
> 

Odd, this works fine for me (I just re-did it to make sure).

Note: in order for the the patches to have an effect, you need to update your
configuration.
  % ecosconfig tree
  % make clean;make

[ECOS] RedBoot, Ethernet, MBX860

[Anthony Massa]

I am using the MBX860 platform with the net package.  I have RedBoot running
on my target, and seems to be operating properly.  I then connect
GDB/Insight via the Ethernet port and can download the code properly.  I am
finding that the code always dies in the quicc_eth_init routine in
if_quicc.c.  I want to eventually be able to run the GoAhead webserver
running on my board, which I have compiled in and ready to go - I hope.  Has
anyone been able to get the MBX860 platform up and running using the net
package and the Ethernet port for debugging.

Here are some of the things I have tried to get the quicc_eth_init routine
running...

- Moving the creation of the interrupt in quicc_eth_init to the end of the
routine.  This failed with the same outcome as before.

- I removed a line (shown below) in the quicc_eth_init because of the
comment of shutting down the Ethernet.  I thought this would have been the
problem since I was debugging using the Ethernet port, and obviously,
shutting it down would be very bad.  This failed with the same outcome as
before, too.

    // Shut down ethernet, in case it is already running
    scc->scc_gsmr_l &= ~(QUICC_SCC_GSML_ENR | QUICC_SCC_GSML_ENT);


- I disabled interrupts at the beginning of the quicc_eth_init routine using
HAL_DISABLE_INTERRUPTS and re-enabled them at the end using
HAL_RESTORE_INTERRUPTS.  This failed and hung the board the same way as
before.

- I also tried using a static IP address.  I didn't think this would work
since the failure occurs way before the IP address is used.  This failed as
well.


It seemed as though the failure was occurring when the code tried to access
the volatile struct ethernet_pram *enet_pram variable in quicc_eth_init.  It
was hard to be absolutely certain because there were some failures that
occurred at different points in the routine, but it seemed that the code
that used this variable caused the most immediate failures.  I don't know if
there is some sort of contention problem with accessing the Ethernet
registers while RedBoot/GDB is running or what.

I did try to run while stepping through the quicc_eth_init routine and also
just running without any breakpoints, however, the hung board result was the
same in both running cases.

RE: [ECOS] RedBoot, Ethernet, MBX860

[Gary Thomas]

I just fixed a number of little things that, added up, kept the MBX from working
well when using ethernet and RedBoot.  See the recent email (send today) for
the patches.

With these in place, everything _except_ ^C over an ethernet debug channel
seems to work for me.  Please let us know if this is not your experience.

On 03-May-2001 Anthony Massa wrote:
> 
> I am using the MBX860 platform with the net package.  I have RedBoot running
> on my target, and seems to be operating properly.  I then connect
> GDB/Insight via the Ethernet port and can download the code properly.  I am
> finding that the code always dies in the quicc_eth_init routine in
> if_quicc.c.  I want to eventually be able to run the GoAhead webserver
> running on my board, which I have compiled in and ready to go - I hope.  Has
> anyone been able to get the MBX860 platform up and running using the net
> package and the Ethernet port for debugging.
> 
> Here are some of the things I have tried to get the quicc_eth_init routine
> running...
> 
> - Moving the creation of the interrupt in quicc_eth_init to the end of the
> routine.  This failed with the same outcome as before.
> 
> - I removed a line (shown below) in the quicc_eth_init because of the
> comment of shutting down the Ethernet.  I thought this would have been the
> problem since I was debugging using the Ethernet port, and obviously,
> shutting it down would be very bad.  This failed with the same outcome as
> before, too.
> 
>     // Shut down ethernet, in case it is already running
>     scc->scc_gsmr_l &= ~(QUICC_SCC_GSML_ENR | QUICC_SCC_GSML_ENT);
> 
> 
> - I disabled interrupts at the beginning of the quicc_eth_init routine using
> HAL_DISABLE_INTERRUPTS and re-enabled them at the end using
> HAL_RESTORE_INTERRUPTS.  This failed and hung the board the same way as
> before.
> 
> - I also tried using a static IP address.  I didn't think this would work
> since the failure occurs way before the IP address is used.  This failed as
> well.
> 
> 
> It seemed as though the failure was occurring when the code tried to access
> the volatile struct ethernet_pram *enet_pram variable in quicc_eth_init.  It
> was hard to be absolutely certain because there were some failures that
> occurred at different points in the routine, but it seemed that the code
> that used this variable caused the most immediate failures.  I don't know if
> there is some sort of contention problem with accessing the Ethernet
> registers while RedBoot/GDB is running or what.
> 
> I did try to run while stepping through the quicc_eth_init routine and also
> just running without any breakpoints, however, the hung board result was the
> same in both running cases.