AM335X EMAC BOOT

yi li2

Other Parts Discussed in Thread: AM3359

hi,

I'm using AM335X for EMAC BOOT mode. as the spec says, when we receive a BOOTP request, we send the expects response in 26.1.8.4.2( AM335x ARM Cortex-A8 Microprocessors (MPUs) Technical Reference Manual )

but the board still trys 5 BOOTP requests, It seems the am3359 does not accecpt the BOOTP reply.

here are the packet we captured:

Fullscreen 6471.boot request_summary.txt Download

No.     Time        Source                Destination           Protocol Info
   1802 1254.000000 0.0.0.0               255.255.255.255       BOOTP    Boot Request from 00:17:ea:aa:f7:8a (TexasIns_aa:f7:8a)

Frame 1802 (406 bytes on wire, 406 bytes captured)
Ethernet II, Src: TexasIns_aa:f7:8a (00:17:ea:aa:f7:8a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
    Message type: Boot Request (1)
    Hardware type: Ethernet
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x00000001
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: TexasIns_aa:f7:8a (00:17:ea:aa:f7:8a)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: (OK)
    Option: (t=60,l=15) Vendor class identifier = "DM814x ROM v1.0"
    Option: (t=61,l=81) Client identifier
    End Option
    Padding

Fullscreen 7635.boot reply_summary.txt Download

No.     Time        Source                Destination           Protocol Info
   1803 1254.000000 192.168.0.1           255.255.255.255       BOOTP    Boot Reply

Frame 1803 (342 bytes on wire, 342 bytes captured)
Ethernet II, Src: c8:9c:dc:74:10:e7 (c8:9c:dc:74:10:e7), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol, Src: 192.168.0.1 (192.168.0.1), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68)
Bootstrap Protocol
    Message type: Boot Reply (2)
    Hardware type: Ethernet
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x00000001
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 192.168.0.126 (192.168.0.126)
    Next server IP address: 192.168.0.1 (192.168.0.1)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: TexasIns_aa:f7:8a (00:17:ea:aa:f7:8a)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name: u-boot-spl.bin
    Magic cookie: (OK)
    Option: (t=1,l=4) Subnet Mask = 255.255.255.0
    Option: (t=2,l=4) Time Offset = 0 time
    Option: (t=3,l=4) Router = 192.168.0.1
    Option: (t=17,l=22) Root Path = "C:\Program Files\dhcp"
    End Option
    Padding

Fullscreen 0647.boot request_bytes.txt Download

char pkt1807[] = {
0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0x00, 0x17, 
0xea, 0xaa, 0xf7, 0x8a, 0x08, 0x00, 0x45, 0x00, 
0x01, 0x88, 0x05, 0x00, 0x00, 0x00, 0x40, 0x11, 
0x74, 0x66, 0x00, 0x00, 0x00, 0x00, 0xff, 0xff, 
0xff, 0xff, 0x00, 0x44, 0x00, 0x43, 0x01, 0x74, 
0x5b, 0x5e, 0x01, 0x01, 0x06, 0x00, 0x00, 0x00, 
0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x17, 
0xea, 0xaa, 0xf7, 0x8a, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x63, 0x82, 
0x53, 0x63, 0x3c, 0x0f, 0x44, 0x4d, 0x38, 0x31, 
0x34, 0x78, 0x20, 0x52, 0x4f, 0x4d, 0x20, 0x76, 
0x31, 0x2e, 0x30, 0x3d, 0x51, 0x05, 0x01, 0x05, 
0x01, 0x81, 0x40, 0x07, 0x02, 0x13, 0x02, 0x01, 
0x00, 0x12, 0x15, 0x01, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x14, 0x21, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x15, 0x09, 0x01, 0xf9, 0xb1, 
0x5e, 0xc2, 0x00, 0x00, 0x00, 0x00, 0xff, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00 };

Fullscreen 8306.boot reply_bytes.txt Download

char pkt1808[] = {
0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xc8, 0x9c, 
0xdc, 0x74, 0x10, 0xe7, 0x08, 0x00, 0x45, 0x00, 
0x01, 0x48, 0x0b, 0x9a, 0x00, 0x00, 0x40, 0x11, 
0xad, 0x62, 0xc0, 0xa8, 0x00, 0x01, 0xff, 0xff, 
0xff, 0xff, 0x00, 0x43, 0x00, 0x44, 0x01, 0x34, 
0xc1, 0xee, 0x02, 0x01, 0x06, 0x00, 0x00, 0x00, 
0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0xc0, 0xa8, 0x00, 0x7e, 0xc0, 0xa8, 
0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x17, 
0xea, 0xaa, 0xf7, 0x8a, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x75, 0x2d, 
0x62, 0x6f, 0x6f, 0x74, 0x2d, 0x73, 0x70, 0x6c, 
0x2e, 0x62, 0x69, 0x6e, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x63, 0x82, 
0x53, 0x63, 0x01, 0x04, 0xff, 0xff, 0xff, 0x00, 
0x02, 0x04, 0x00, 0x00, 0x00, 0x00, 0x03, 0x04, 
0xc0, 0xa8, 0x00, 0x01, 0x11, 0x16, 0x43, 0x3a, 
0x5c, 0x50, 0x72, 0x6f, 0x67, 0x72, 0x61, 0x6d, 
0x20, 0x46, 0x69, 0x6c, 0x65, 0x73, 0x5c, 0x64, 
0x68, 0x63, 0x70, 0x00, 0xff, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
0x00, 0x00, 0x00, 0x00, 0x00, 0x00 };

Is there any error in the BOOTP packet we response? or is there any tools we can use directly?

over 12 years ago

0 Biser Gatchev-XID over 12 years ago

TI__Guru**** 393215 points

Hi Yu Li,

Is your board directly connected to a PC? If it is, try connecting through an Ethernet switch.

0 yi li2 over 12 years ago in reply to Biser Gatchev-XID

Intellectual 615 points

appreciate for your reply,

yes, our board is directly connected to a PC, now we connected the board to a router. but the board still trys 5 BOOTP requests,

Is it correct what the BOOTP packet we response? or any other problems?

0 Biser Gatchev-XID over 12 years ago in reply to yi li2

TI__Guru**** 393215 points

Yu Li,

Could you give some more information about your board? Is this a custom board, what PHY are you using, how is it connected to the AM335X?

0 yi li2 over 12 years ago in reply to Biser Gatchev-XID

Intellectual 615 points

appreciate for your help

yes, the board we use is our custom board, with Ethernet PHY device(IP101A) through MII interface. on hardware side, we use the AM335x BeagleBone schematic as reference to connect AM335x with Ethernet PHY.

The pin connect as folowing(AM335X<--------->IP101A)

MDIO_CLK <--------->MDC, MDIO_DATA<--------->MDIO, GMII1_TXD0<--------->TXD0, GMII1_TXD1<--------->TXD1, GMII1_TXD2<--------->TXD2, GMII1_TXD3<--------->TXD3, GMII1_TXEN<--------->TXEN, GMII1_TXCLK<--------->TX_CLK, GMII1_RXDV<--------->RX_DV, GMII1_RXD0<--------->RXD0, GMII1_RXD1<--------->RXD1, GMII1_RXD2<--------->RXD2, GMII1_RXD3<--------->RXD3, GMII1_RXCLK<--------->RX_CLK, GMII1_COL<--------->COL, GMII1_CRS<--------->CRS, GMII1_RXERR<--------->RX_ERR

the schematic is