Hmm, that seems odd that it does that. However, as long as others are seeing the same behavior then I guess I'm ok with it. Thanks for the help everybody.
-BJ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Narnakaje, Snehaprabha Sent: Wednesday, January 23, 2008 6:18 AM To: BJ Opp; Maupin, Chase Cc: [email protected] Subject: RE: Questions about DM355 DVEVM BJ, The "link down" message is normal, coming from the DM9000A Ethernet driver, before actually trying out the link negotiation. You should then see a "link up" message once the negotiation is complete. eth0: link down Sending DHCP requests ., OK IP-Config: Got DHCP answer from 255.255.255.255, my address is xxx.xxx.xxx.xxx IP-Config: Complete: ... eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Thanks Sneha -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of BJ Opp Sent: Tuesday, January 22, 2008 1:08 PM To: Maupin, Chase Cc: [email protected] Subject: RE: Questions about DM355 DVEVM Yes, here's a dump of the pertinent environment settings, as well as the dmesg output as promised. The weird thing is that after I get the 'link down' message the board seems to boot ok? What am i missing here? bootargs=mem=120M console=ttyS0,115200n8 ip=dhcp noinitrd rw ip=dhcp root=/dev/nfs nfsroot=111.111.110.155:/home/bj/workdir/filesys,nolock bootfile="uImage" bootcmd=nboot 0x80700000 0 0x400000; bootm serverip=111.111.110.155 /********* snip of dmesg ************/ eth0: link down Sending DHCP requests ., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 111.111.110.109 IP-Config: Complete: device=eth0, addr=111.111.110.109, mask=255.255.254.0, gw=111.111.111.100, host=111.111.110.109, domain=deepsea.com, nis-domain=(none), bootserver=0.0.0.0, rootserver=111.111.110.155, rootpath= Looking up port of RPC 100003/2 on 111.111.110.155 Looking up port of RPC 100005/1 on 111.111.110.155 VFS: Mounted root (nfs filesystem). /********* end snip ***************/ Thanks again.. -BJ -----Original Message----- From: Maupin, Chase [mailto:[EMAIL PROTECTED] Sent: Tue 1/22/2008 9:49 AM To: BJ Opp Cc: [email protected] Subject: RE: Questions about DM355 DVEVM BJ, Did you change the default bootargs variable in u-boot to use ip=dhcp rather than ip=off? Sincerely, Chase Maupin Software Applications Catalog DSP Products e-mail: [EMAIL PROTECTED] phone: (281) 274-3285 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of BJ Opp Sent: Tuesday, January 22, 2008 11:28 AM Cc: [email protected] Subject: RE: Questions about DM355 DVEVM On a somewhat different note regarding the DM355. Did you have to take any special steps to get the onboard Ethernet working properly? We have DM6446 boards that we used for development and have a project going with them (and our own custom boards). Both are functioning without any major issues however when we try to boot the kernel on the dm355 the Ethernet port always comes up with 'no link' I seem to recall just being able to plug in a cable and 'ping' the eval boards. Is there an initial step that we've missed? Thanks. I can attach a clip from our dmesg output when I get only my development box if it'll help at all. - BJ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fran Fadden Sent: Tuesday, January 22, 2008 3:56 AM To: Ilyssa Tzivia Cc: [email protected] Subject: Re: Questions about DM355 DVEVM Ilyssa Tzivia wrote: > On Jan 19, 2008 10:29 AM, Stephen Berry <[EMAIL PROTECTED]> wrote: > > Stephen, > > Thanks for your help. I have some follow up questions. > >> - the TI webpage says "On-board Ethernet controller with application notes and schematics". Does this mean the DM355 does not have an on-chip MAC and that it requires an external MAC/PHY chip? If I wanted to create a DM355 solution with two ethernet interfaces such as LAN and WAN, would I need to write special drivers or require major board changes? The MAC/PHY is external - it is attached to the AEMIF bus. To implement another ethernet interface you need to modify the CPLD code to add an additional chip select and modify drivers for the address space change. > > This seems more complex than I anticipated. I searched TI's website > for related application notes but did not find anything. You mentioned > CPLD code so I'm trying to figure out what this CPLD is. Another alternative, if the changes that Steve suggests are more than you want to do, would be to make a second network device available via the USB port. We've used a USB to ethernet dongle for debugging our 355 based board, and it works fine. A third option could be to use an ethernet card for the SDIO (SD/MMC) slot. I don't know if there are cards available for wired ethernet, but we are using a wireless (802.11a/b/g) card from CardAccess. _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
