Network DHCP Issues

Yocto related software discussions are here

Network DHCP Issues

Postby Wicked One 612 » Thu Jan 30, 2014 12:35 am

Hey,

I'm having some difficulties getting my Wandboard connecting to my PC so that I can SSH into it (upload an image from QT Creator). My Wandboard Dual is running Yocto 1.5 with QT5, as configured per the Wiki pages. I have the board plugged into my PC via an ethernet cable. I went into U-Boot and added "ip=dhcp" to the mmcargs environment variable so that it would attempt DHCP. Here is what my environment variables look like:

Code: Select all
baudrate=115200
boot_fdt=try
bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; else run netboot; fi; fi; else run netboot; fi
bootdelay=5
bootscript=echo Running bootscript from mmc ...; source
console=ttymxc0
ethact=FEC
ethaddr=00:1f:7b:b2:0a:16
ethprime=FEC
fdt_addr=0x11000000
fdt_file=imx6dl-wandboard.dtb
fdt_high=0xffffffff
initrd_high=0xffffffff
ip_dyn=yes
ipaddr=10.0.1.100
loadaddr=0x12000000
loadbootscript=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${script};
loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}
loaduimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${uimage}
mmcargs=setenv bootargs console=${console},${baudrate} root=${mmcroot} video=mxcfb0:dev=lcd,SEIKO-WVGA,if=RGB666,bpp=32 ip=dhcp
mmcboot=echo Booting from mmc ...; run mmcargs; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then bootm ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootm; else echo WARN: Cannot load the DT; fi; fi; else bootm; fi;
mmcdev=0
mmcpart=1
mmcroot=/dev/mmcblk0p2 rootwait rw
netargs=setenv bootargs console=${console},${baudrate} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; ${get_cmd} ${uimage}; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if ${get_cmd} ${fdt_addr} ${fdt_file}; then bootm ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootm; else echo WARN: Cannot load the DT; fi; fi; else bootm; fi;
script=boot.scr
splashpos=m,m
uimage=uImage
update_sd_firmware=if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; if mmc dev ${mmcdev}; then if ${get_cmd} ${update_sd_firmware_filename}; then setexpr fw_sz ${filesize} / 0x200; setexpr fw_sz ${fw_sz} + 1; mmc write ${loadaddr} 0x2 ${fw_sz}; fi; fi
update_sd_firmware_filename=u-boot.imx
videomode=video=mxcfb0:dev=lcd,SEIKO-WVGA,if=RGB666,bpp=32

Environment size: 2129/8188 bytes


When the board boots, it tries a couple times to do DHCP, but times out both times. You can see the failure at lines 6.917095 and 100.567106. Here is the boot log:
Code: Select all
U-Boot 2013.10 (Jan 20 2014 - 19:03:26)

CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
Reset cause: POR
Board: Wandboard
DRAM:  1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
In:    serial
Out:   serial
Err:   serial
Net:   FEC [PRIME]
Hit any key to stop autoboot:  0
mmc0 is current device
reading boot.scr
** Unable to read file boot.scr **
reading uImage
3449004 bytes read in 163 ms (20.2 MiB/s)
Booting from mmc ...
reading imx6dl-wandboard.dtb
** Unable to read file imx6dl-wandboard.dtb **
## Booting kernel from Legacy Image at 12000000 ...
   Image Name:   Linux-3.0.35-4.0.0-wandboard+gd3
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3448940 Bytes = 3.3 MiB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

[    0.000000] Linux version 3.0.35-4.0.0-wandboard+gd35902c (jay@ubuntron) (gcc version 4.8.1 (GCC) ) #1 SMP PREEMPT Mon Jan 20 18:20:27 EST 2014
[    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: Wandboard
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] CPU identified as i.MX6DL/SOLO, silicon rev 1.1
[    0.000000] PERCPU: Embedded 7 pages/cpu @cc008000 s5248 r8192 d15232 u32768
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 215040
[    0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p2 rootwait rw video=mxcfb0:dev=lcd,SEIKO-WVGA,if=RGB666,bpp=32 ip=dhcp
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 592MB 256MB = 848MB total
[    0.000000] Memory: 852236k/852236k available, 196340k reserved, 262144K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     DMA     : 0xf4600000 - 0xffe00000   ( 184 MB)
[    0.000000]     vmalloc : 0xea800000 - 0xf2000000   ( 120 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xea000000   ( 672 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .init : 0xc0008000 - 0xc0035000   ( 180 kB)
[    0.000000]       .text : 0xc0035000 - 0xc064c1ec   (6237 kB)
[    0.000000]       .data : 0xc064e000 - 0xc069d720   ( 318 kB)
[    0.000000]        .bss : 0xc069d744 - 0xc06dfafc   ( 265 kB)
[    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:624
[    0.000000] MXC GPIO hardware
[    0.000000] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
[    0.000000] Set periph_clk's parent to pll2_pfd_400M!
[    0.000000] arm_max_freq=1GHz
[    0.000000] MXC_Early serial console at MMIO 0x2020000 (options '115200')
[    0.000000] bootconsole [ttymxc0] enabled
[    0.000000] Console: colour dummy device 80x30
[    0.218500] Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
[    0.306805] pid_max: default: 32768 minimum: 301
[    0.311772] Mount-cache hash table entries: 512
[    0.317127] CPU: Testing write buffer coherency: ok
[    0.322286] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.422906] CPU1: Booted secondary processor
[    0.512320] Brought up 2 CPUs
[    0.519578] SMP: Total of 2 processors activated (3162.11 BogoMIPS).
[    0.526440] devtmpfs: initialized
[    0.547191] print_constraints: dummy:
[    0.551203] NET: Registered protocol family 16
[    0.559871] print_constraints: vddpu: 725 <--> 1300 mV at 1150 mV fast normal
[    0.567439] print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
[    0.575176] print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
[    0.582865] print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
[    0.590606] print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
[    0.598261] print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
[    0.686661] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[    0.693496] hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
[    0.700840] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.706731] L310 cache controller enabled
[    0.710759] l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x02050000, Cache size: 524288 B
[    0.791630] bio: create slab <bio-0> at 0
[    0.796514] print_constraints: VDDA: 2500 mV
[    0.801082] print_constraints: VDDIO: 3300 mV
[    0.805995] vgaarb: loaded
[    0.809418] SCSI subsystem initialized
[    0.813855] spi_imx imx6q-ecspi.0: probed
[    0.818114] spi_imx imx6q-ecspi.1: probed
[    0.823495] usbcore: registered new interface driver usbfs
[    0.829144] usbcore: registered new interface driver hub
[    0.834644] usbcore: registered new device driver usb
[    0.852317] imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
[    0.860455] mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed
[    0.866938] mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a
[    0.874663] MIPI CSI2 driver module loaded
[    0.878901] Advanced Linux Sound Architecture Driver Version 1.0.24.
[    0.886123] Bluetooth: Core ver 2.16
[    0.889828] NET: Registered protocol family 31
[    0.894297] Bluetooth: HCI device and connection manager initialized
[    0.900672] Bluetooth: HCI socket layer initialized
[    0.905569] Bluetooth: L2CAP socket layer initialized
[    0.910704] Bluetooth: SCO socket layer initialized
[    0.916036] cfg80211: Calling CRDA to update world regulatory domain
[    0.922483] Switching to clocksource mxc_timer1
[    0.941869] NET: Registered protocol family 2
[    0.946457] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.954254] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.963577] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
[    0.971224] TCP: Hash tables configured (established 131072 bind 65536)
[    0.977867] TCP reno registered
[    0.981027] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.986989] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.993792] NET: Registered protocol family 1
[    0.998476] RPC: Registered named UNIX socket transport module.
[    1.004416] RPC: Registered udp transport module.
[    1.009149] RPC: Registered tcp transport module.
[    1.013868] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.020519] _regulator_get: etb supply vcore not found, using dummy regulator
[    1.028151] _regulator_get: etm.0 supply vcore not found, using dummy regulator
[    1.035552] _regulator_get: etm.1 supply vcore not found, using dummy regulator
[    1.043233] Static Power Management for Freescale i.MX6
[    1.048511] wait mode is disabled for i.MX6
[    1.052880] cpaddr = ea820000 suspend_iram_base=ea8b0000
[    1.058303] PM driver module loaded
[    1.778270] link up failed, DB_R0:0x00ccf700, DB_R1:0x08200000!
[    1.784207] IMX PCIe port: link down!
[    1.788254] IMX usb wakeup probe
[    1.792091] IMX usb wakeup probe
[    1.795576] cpu regulator mode:ldo_enable
[    1.799782] i.MXC CPU frequency driver
[    1.813623] highmem bounce pool size: 64 pages
[    1.831823] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.838604] msgmni has been set to 1152
[    1.843942] alg: No test for stdrng (krng)
[    1.848219] io scheduler noop registered
[    1.852154] io scheduler deadline registered
[    1.856532] io scheduler cfq registered (default)
[    1.862038] mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver lcd
[    1.942418] Console: switching to colour frame buffer device 100x30
[    1.983643] mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver ldb
[    1.990068] _regulator_get: get() with no identifier
[    1.995080] mxc_sdc_fb mxc_sdc_fb.1: ipu0-di0 already in use
[    2.000772] mxc_sdc_fb: probe of mxc_sdc_fb.1 failed with error -16
[    2.007684] imx-sdma imx-sdma: loaded firmware 1.1
[    2.016695] imx-sdma imx-sdma: initialized
[    2.159424] Serial: IMX driver
[    2.162587] imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
[    2.169079] console [ttymxc0] enabled, bootconsole disabled
[    2.169079] console [ttymxc0] enabled, bootconsole disabled
[    2.180723] imx-uart.2: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX
[    2.191667] loop: module loaded
[    2.195442] FEC Ethernet Driver
[    2.200434] fec_enet_mii_bus: probed
[    2.204871] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.211531] add wake up source irq 75
[    2.217632] fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
[    2.224333] fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
[    2.257071] fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
[    2.277061] fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
[    2.283400] hub 1-0:1.0: USB hub found
[    2.287204] hub 1-0:1.0: 1 port detected
[    2.291338] add wake up source irq 72
[    2.295041] fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
[    2.301691] fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
[    2.337072] fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
[    2.357068] fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
[    2.363285] hub 2-0:1.0: USB hub found
[    2.367060] hub 2-0:1.0: 1 port detected
[    2.371326] Initializing USB Mass Storage driver...
[    2.376351] usbcore: registered new interface driver usb-storage
[    2.382375] USB Mass Storage support registered.
[    2.387264] ARC USBOTG Device Controller driver (1 August 2005)
[    2.393230] udc: request mem region for fsl-usb2-udc failed
[    2.398908] fsl-usb2-udc: probe of fsl-usb2-udc failed with error -16
[    2.405760] mousedev: PS/2 mouse device common for all mice
[    2.411625] prism: probe of 1-0010 failed with error -5
[    2.417096] i2c /dev entries driver
[    2.421371] Linux video capture interface: v2.00
[    2.426366] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16
[    2.434013] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17
[    2.441725] Bluetooth: HCI UART driver ver 2.2
[    2.446176] Bluetooth: HCI H4 protocol initialized
[    2.451110] sdhci: Secure Digital Host Controller Interface driver
[    2.457302] sdhci: Copyright(c) Pierre Ossman
[    2.461772] _regulator_get: sdhci-esdhc-imx.2 supply vmmc not found, using dummy regulator
[    2.470325] mmc0: SDHCI controller on platform [sdhci-esdhc-imx.2] using ADMA
[    2.478330] _regulator_get: sdhci-esdhc-imx.1 supply vmmc not found, using dummy regulator
[    2.491692] mmc1: SDHCI controller on platform [sdhci-esdhc-imx.1] using ADMA
[    2.498884] sdhci sdhci-esdhc-imx.0: no write-protect pin available!
[    2.506065] _regulator_get: sdhci-esdhc-imx.0 supply vmmc not found, using dummy regulator
[    2.529063] mmc2: SDHCI controller on platform [sdhci-esdhc-imx.0] using ADMA
[    2.536426] mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
[    2.549493] VPU initialized
[    2.554949] mxc_asrc registered
[    2.558277] Galcore version 4.6.9.6622
[    2.584425] Thermal calibration data is 0x59c5305f
[    2.589253] Thermal sensor with ratio = 186
[    2.617067] Anatop Thermal registered as thermal_zone0
[    2.622366] anatop_thermal_probe: default cooling device is cpufreq!
[    2.632613] usbcore: registered new interface driver usbhid
[    2.638236] usbhid: USB HID core driver
[    2.642621] usbcore: registered new interface driver snd-usb-audio
[    2.649396] mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
[    2.654784] mxc_spdif mxc_spdif.0: MXC SPDIF Audio
[    2.660887] imx-hdmi-soc-dai imx-hdmi-soc-dai.0: Failed: Load HDMI-video first.
[    2.668918] _regulator_get: 1-000a supply VDDD not found, using dummy regulator
[    2.676540] sgtl5000 1-000a: sgtl5000 revision 17
[    2.681497] print_constraints: 1-000a: 850 <--> 1600 mV at 1200 mV normal
[    2.712635] mmc0: new high speed SDHC card at address 1234
[    2.718511] mmcblk0: mmc0:1234 SA16G 14.8 GiB
[    2.728279]  mmcblk0: p1 p2
[    2.741356] asoc: sgtl5000 <-> imx-ssi.1 mapping ok
[    2.751631] asoc: mxc-spdif <-> imx-spdif-dai.0 mapping ok
[    2.758138] Initialize HDMI-audio failed. Load HDMI-video first!
[    2.764149] ALSA device list:
[    2.767141]   #0: sgtl5000-audio
[    2.770371]   #1: imx-spdif
[    2.776907] TCP cubic registered
[    2.780176] NET: Registered protocol family 17
[    2.791108] Bluetooth: RFCOMM socket layer initialized
[    2.797913] Bluetooth: RFCOMM ver 1.11
[    2.801701] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.807016] Bluetooth: BNEP filters: multicast
[    2.811503] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    2.819946] lib80211: common routines for IEEE802.11 drivers
[    2.825677] Registering the dns_resolver key type
[    2.830440] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    2.838174] ThumbEE CPU extension supported.
[    2.846057] Bus freq driver module loaded
[    2.853341] Bus freq driver Enabled
[    2.861897] mxc_dvfs_core_probe
[    2.868468] DVFS driver module loaded
[    2.877736] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    2.889824] eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, irq=-1)
[    3.062008] mmc1: queuing unknown CIS tuple 0x80 (50 bytes)
[    3.177416] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    3.209330] mmc1: queuing unknown CIS tuple 0x80 (4 bytes)
[    3.592981] mmc1: queuing unknown CIS tuple 0x02 (1 bytes)
[    3.633269] mmc1: new SDIO card at address 0001
[    6.887430] PHY: 1:01 - Link is Up - 1000/Full
[    6.917095] Sending DHCP requests ...... timed out!
[   96.534280] IP-Config: Reopening network devices...
[   96.543622] eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, irq=-1)
[  100.537373] PHY: 1:01 - Link is Up - 1000/Full
[  100.567106] Sending DHCP requests ...... timed out!
[  179.714174] IP-Config: Auto-configuration of network failed.
[  179.739734] EXT3-fs: barriers not enabled
[  181.886587] kjournald starting.  Commit interval 5 seconds
[  182.191967] EXT3-fs (mmcblk0p2): using internal journal
[  182.197243] EXT3-fs (mmcblk0p2): recovery complete
[  182.214968] EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
[  182.222109] VFS: Mounted root (ext3 filesystem) on device 179:2.
[  182.240438] devtmpfs: mounted
[  182.243457] Freeing init memory: 180K
INIT: version 2.88 booting
Starting udev
[  183.429738] udevd[1272]: starting version 182
Starting Bootlog daemon: bootlogd.
Populating dev cache
ALSA: Restoring mixer settings...
No state is present for card sgtl5000audio
Found hardware: "sgtl5000-audio" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card sgtl5000audio
No state is present for card imxspdif
Found hardware: "imx-spdif" "" "" "" ""
Hardware is initialized using a generic method
Configuring network interfaces... No state is present for card imxspdif
[  189.206163] eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, irq=-1)
udhcpc (v1.21.1) started
Sending discover...
Sending discover...
[  193.197447] PHY: 1:01 - Link is Up - 1000/Full
Sending discover...
No lease, failing
hwclock: can't open '/dev/misc/rtc': No such file or directory
Wed Jan 22 02:06:00 UTC 2014
hwclock: can't open '/dev/misc/rtc': No such file or directory
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Starting OpenBSD Secure Shell server: sshd
Could not load host key: /etc/ssh/ssh_host_dsa_key
done.
hwclock: can't open '/dev/misc/rtc': No such file or directory
Starting syslogd/klogd: done
Stopping Bootlog daemon: bootlogd.

Poky (Yocto Project Reference Distro) 1.5.1 wandboard-dual /dev/ttymxc0

wandboard-dual login:


If I run an ifconfig on the Wandboard, here are the results:
Code: Select all
eth0      Link encap:Ethernet  HWaddr 00:1F:7B:B2:0A:16
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:30 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10380 (10.1 KiB)  TX bytes:7402 (7.2 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


And if I run an ifconfig on the PC it is connected to, here are the results:
Code: Select all
eth0      Link encap:Ethernet  HWaddr 00:10:18:19:7c:75 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:16

eth1      Link encap:Ethernet  HWaddr 00:18:8b:17:1e:d3 
          inet6 addr: fe80::218:8bff:fe17:1ed3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:444887 errors:0 dropped:0 overruns:0 frame:0
          TX packets:269335 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:585394462 (585.3 MB)  TX bytes:40567709 (40.5 MB)
          Interrupt:16

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:440357 errors:0 dropped:0 overruns:0 frame:0
          TX packets:440357 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:53027169 (53.0 MB)  TX bytes:53027169 (53.0 MB)


Finally here is what the file at /etc/network/interfaces looks like:
Code: Select all
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

# Wireless interfaces
iface wlan0 inet dhcp
        wireless_mode managed
        wireless_essid any
        wpa-driver wext
        wpa-conf /etc/wpa_supplicant.conf

iface atml0 inet dhcp

# Wired or wireless interfaces
auto eth0
iface eth0 inet dhcp
iface eth1 inet dhcp

# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
iface usb0 inet static
        address 192.168.7.2
        netmask 255.255.255.0
        network 192.168.7.0
        gateway 192.168.7.1

# Bluetooth networking
iface bnep0 inet dhcp


Does anyone have any idea what the issue is? I've tried it with multiple computers as well and just can't seem to connect to it.

Thank you!
Wicked One 612
 
Posts: 19
Joined: Fri Oct 11, 2013 2:54 am

Re: Network DHCP Issues

Postby wandboard » Thu Jan 30, 2014 5:05 am

Hi,

Do you have a DHCP server installed somewhere that serves an IP address to your wandboard?

As well. Do you connect over a hub/switch/AP/router or straight into your computer? (could be a UTP cable issue in that case).
wandboard
Site Admin
 
Posts: 24
Joined: Thu Aug 29, 2013 4:35 pm

Re: Network DHCP Issues

Postby Wicked One 612 » Thu Jan 30, 2014 10:27 pm

Hmmm, I suppose I don't have a DHCP server installed per-se on each machine. I was under the assumption that the network card takes care of that. I tried installing dhcpd on my Ubuntu, but it seemed to have some config issues. I'm really not that great with networking stuff.

All I'm really looking to do is connect from the PC to the Wandboard, I don't particularly care how I do it. Is there an easier way to do it? Maybe not using DHCP? How do people normally connect their Wandboard's using Yocto to the internet and other computers?

And I am connecting directly to the computer, not through a router or switch.

Thanks for all the help!
Wicked One 612
 
Posts: 19
Joined: Fri Oct 11, 2013 2:54 am

Re: Network DHCP Issues

Postby wandboard » Fri Jan 31, 2014 1:52 pm

If you connect to the internet you normally go over a access point/router that will have an DHCP server running that automatically provides an IP address to your computers, laptops, smartphones, tablets and Wandboard(s).

If you want to connect directly to another computer you can either do the following.
1. configure static IP's (google how-to do this in linux. There are many tutorials available).
2. install and configure a DHCP server on one computer that assigns IP's to the other.
wandboard
Site Admin
 
Posts: 24
Joined: Thu Aug 29, 2013 4:35 pm

Re: Network DHCP Issues

Postby thudson » Sat Feb 01, 2014 6:34 pm

Not sure what OS your running on your PC, but the Mac has a setting to "Share wireless connection of ethernet port." This will fire up a dhcp server to hand out addresses on the ethernet port to allow you to share your wireless connection with other computers. Windows should have something similar. I believe I've seen something similar in Ubuntu.
thudson
 
Posts: 16
Joined: Sat Aug 31, 2013 2:14 am

Re: Network DHCP Issues

Postby Wicked One 612 » Mon Feb 03, 2014 4:31 pm

Thanks for your help guys! I got it working by adding "ip=dhcp" to the end of the mmcargs environment variable. Then I plugged the Wandboard directly into the router, instead of my computer, which has a DHCP server on it. So that issued the Wandboard an IP and such no problem. And given that I was connected to the same router, I could connect to the Wandboard's IP after finding it using an ifconfig.

Now to figure out why this cross-compiler isn't working... Hmm, I'm sure I'll be posting about that shortly.
Wicked One 612
 
Posts: 19
Joined: Fri Oct 11, 2013 2:54 am

Re: Network DHCP Issues

Postby ariana2 » Thu Oct 09, 2014 9:20 am

FYI, after the bitbake I used the file "fsl-image-gui.sdcard". (the wiki page says "fsl-image-gui.img"... there is no .img image in the folder....
ariana2
 
Posts: 1
Joined: Thu Oct 09, 2014 9:15 am


Return to Software - Yocto

Who is online

Users browsing this forum: No registered users and 5 guests

cron