2008-11-03 10:45:40     TFTP doesn't work ok via Network Console

Document created by Aaronwu Employee on Sep 18, 2013
Version 1Show Document
  • View in full screen mode

2008-11-03 10:45:40     TFTP doesn't work ok via Network Console

Alexander Deurloo (NETHERLANDS)

Message: 64630   

 

Hello,

 

I have a BF527-ezkit and I would like to use the network console (nc) in stead of the serial console. First glance ok.

 

When I did "run update" via the network console, the board didn't boot anymore. So, back to the serial console and figure out what happens.

First, I simply tried to load a u-boot.ldr into SDRAM via the network console. I noticed a difference in text during loading. When I do this simple test via the serial console I see:

 

bf> tftp 1000000 u-boot.ldr

Using Blackfin EMAC device

TFTP from server 10.1.0.181; our IP address is 10.1.0.237

Filename 'u-boot.ldr'.

Load address: 0x1000000

Loading: ###############################

done

Bytes transferred = 156728 (26438 hex)

 

I viewed the memory and everything cool. Bytes were modified.

 

Then I switched over to network console (via ncip and stdin/out to nc,etc). Works fine.

 

Then I repeated the tftp test under the network console:

 

bf> tftp 1000000 u-boot.ldr

tftp 1000000 u-boot.ldr

Using Blackfin EMAC device

TFTP from server 10.1.0.181; our IP address is 10.1.0.237

Filename 'u-boot.ldr'.

Load address: 0x1000000

Loading: bf>

 

As you can see after "loading:" a lot of text is missing. Smells like nothing is happening.

Checking the memory shows me nothing was transferred. (I also tried address 2000000 and verified it before and after the tftp command. No bytes changed at all). No wonder why the board refuses to boot, since the "run update" command erases the flash, no matter if the tftp part fails.

 

But what am I doing wrong? Is it possible anyway to use TFTP via the nc?

 

Thanks in advance,

Alexander.

 

QuoteReplyEditDelete

 

 

2008-11-03 11:49:33     Re: TFTP doesn't work ok via Network Console

Mike Frysinger (UNITED STATES)

Message: 64636   

 

this is a known issue and there is a tracker open for it.  there is no known workaround atm.

Attachments

    Outcomes