I have what appears to be an odd problem when a Lauterbach (PowerTrace or
just the Debugger) is connected to my target board an AT91RM9200-EK.

Without the Lauterbach connected on power up UBOOT runs and I can then
TFTP an image into RAM.

With the Lauterbach connected on power UBOOT runs but when I try and TFTP,
UBOOT reports 
  PHY is not connected!! 
  MAC: Error during MII initialization.

I know TFTP'ing an app in might seem a little odd anyway whilst a debugger
is attached but it was a test to prove something else.
I had already noticed that if I loaded our QNX startup via the Lauterbach
and ran that, then the network driver failed to start properly. 

According to datasheets for the ATMEL AT91RM9200 and their Evaluation Kit
board none of the signals are shared between JTAG/TRACE and the Ethernet
peripherals.

Any thoughts?   Do you think its the ATMEL chip implementation, a
Lauterbach effect, or something i've not done in my Lauterbach
initialisation script?

Cheers for any suggestions.

Tony

On Jul 5, 12:54 pm, "Dodd" <a...@servomex.com> wrote:
> I have what appears to be an odd problem when a Lauterbach (PowerTrace or
> just the Debugger) is connected to my target board an AT91RM9200-EK.
>
> Without the Lauterbach connected on power up UBOOT runs and I can then
> TFTP an image into RAM.
>
> With the Lauterbach connected on power UBOOT runs but when I try and TFTP,
> UBOOT reports
>   PHY is not connected!!
>   MAC: Error during MII initialization.
>
> I know TFTP'ing an app in might seem a little odd anyway whilst a debugger
> is attached but it was a test to prove something else.
> I had already noticed that if I loaded our QNX startup via the Lauterbach
> and ran that, then the network driver failed to start properly.
>
> According to datasheets for the ATMEL AT91RM9200 and their Evaluation Kit
> board none of the signals are shared between JTAG/TRACE and the Ethernet
> peripherals.
>
> Any thoughts?   Do you think its the ATMEL chip implementation, a
> Lauterbach effect, or something i've not done in my Lauterbach
> initialisation script?
>
> Cheers for any suggestions.
>
> Tony

Have you tried Lauterbach customer support?
You problem doesn't sound like one would expected it to be common to
many Lauterbach users...

"Dodd" <a...@servomex.com> skrev i meddelandet 
news:N...@giganews.com...
>I have what appears to be an odd problem when a Lauterbach (PowerTrace or
> just the Debugger) is connected to my target board an AT91RM9200-EK.
>
> Without the Lauterbach connected on power up UBOOT runs and I can then
> TFTP an image into RAM.
>
> With the Lauterbach connected on power UBOOT runs but when I try and TFTP,
> UBOOT reports
>  PHY is not connected!!
>  MAC: Error during MII initialization.
>
> I know TFTP'ing an app in might seem a little odd anyway whilst a debugger
> is attached but it was a test to prove something else.
> I had already noticed that if I loaded our QNX startup via the Lauterbach
> and ran that, then the network driver failed to start properly.
>
> According to datasheets for the ATMEL AT91RM9200 and their Evaluation Kit
> board none of the signals are shared between JTAG/TRACE and the Ethernet
> peripherals.
>
> Any thoughts?   Do you think its the ATMEL chip implementation, a
> Lauterbach effect, or something i've not done in my Lauterbach
> initialisation script?
>
> Cheers for any suggestions.
>
> Tony


It is conceivable that your init script modifies a clock or changes the PIO 
configuration
for one of the pins used by the MII.

-- 
Best Regards,
Ulf Samuelsson
This is intended to be my personal opinion which may,
or may not be shared by my employer Atmel Nordic AB 

On Thu, 05 Jul 2007 11:48:26 -0700, tum_ <a...@mail.ru>
wrote:

>On Jul 5, 12:54 pm, "Dodd" <a...@servomex.com> wrote:
>> I have what appears to be an odd problem when a Lauterbach (PowerTrace or
>> just the Debugger) is connected to my target board an AT91RM9200-EK.
>>
>> Without the Lauterbach connected on power up UBOOT runs and I can then
>> TFTP an image into RAM.
>>
>> With the Lauterbach connected on power UBOOT runs but when I try and TFTP,
>> UBOOT reports
>>   PHY is not connected!!
>>   MAC: Error during MII initialization.

We saw similar behaviour with different JTAG tools. AFAIR the problem
was with the top PHY address line - In effect the PHY address/number
changed.

Stephen

-- 
Stephen Pelc, s...@mpeforth.com
MicroProcessor Engineering Ltd - More Real, Less Time
133 Hill Lane, Southampton SO15 5AF, England
tel: +44 (0)23 8063 1441, fax: +44 (0)23 8033 9691
web: http://www.mpeforth.com - free VFX Forth downloads