[U-Boot-Users] u-boot bringup
Hello All,
I successfully ported u-boot on a PPC405EP processor, But I get the u-boot prompt only when I connect and execute it using the BDI2000, including all the serial outputs. But if I disconnect the BDI nothing comes up on the Serial COM.
Any clues please ??
Thanks, Raghu.
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
Hello all, I am porting u-boot and i am writing network driver.When uboot tries to send Arp request the packet size is 42 bytes and hence the other machines in network dont accept the request as the minimum size of ethernet frame should be 64bytes and hence ARP request packet is dropped. The problem is should the padding of packet to 64bytes should be done in driver code or there is other solution ???? Regards, Pradeep.
Most of the network device contains a bit to configure padding or not padding (it's why network stack doesn't do anything for that). Try to find inside Linux or BSD a reference implementation of your chipset, it's useful when you write a network driver for the first time.
--- pradeep sawlani pradep@gmail.com wrote:
Hello all, I am porting u-boot and i am writing network driver.When uboot tries to send Arp request the packet size is 42 bytes and hence the other machines in network dont accept the request as the minimum size of ethernet frame should be 64bytes and hence ARP request packet is dropped. The problem is should the padding of packet to 64bytes should be done in driver code or there is other solution ???? Regards, Pradeep.
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On 9/2/05, Raghu raghu_dk@yahoo.com wrote:
I successfully ported u-boot on a PPC405EP processor, But I get the u-boot prompt only when I connect and execute it using the BDI2000, including all the serial outputs. But if I disconnect the BDI nothing comes up on the Serial COM.
Any clues please ??
The BDI2000 might be doing some type of processor initialization that is not being done properly in your u-boot code. Another possibility might be a reset issue. Have you verified the basics like you are getting flash chip selects, etc?
Cliff
participants (4)
-
Cliff Brake -
Dominique bastien -
pradeep sawlani -
Raghu