AnsweredAssumed Answered

TWR-VF65GS10-KIT and networking out of the box

Question asked by Laszlo Oberlander on Nov 5, 2014
Latest reply on Apr 10, 2016 by a a

I have just received the TWR-VF65GS10-KIT that included the Vybrid board (Rev H) and the TWR-SER board (Rev G) and wondering if Ethernet should be fully functional right out of the box without changing any jumper settings. I am trying to use ping from within uboot first and then load using tftp but I am running into some difficulties.


Test case 1:

The kit came with U-Boot 2013.07-00004-gaae4ee8 (Jun 05 2014 - 16:00:42) and after configuring the MAC address to match the sticker on the back side of the TWR-SER board, I can see that the Ethernet LEDs come on but I am unable to ping out.


Test case 2:

After reading some other entries on this forum I configured my TWR-SER board to J2: 3-4, J3: 2-3, J12: 9-10 to enable RMII to match what I think the rev H Vybrid board is expecting. After this uboot produces no networking LEDs indicating that the configuration is probably worse than Test case 1.


After this I booted up the rootfs on the SD card (that came preset) and experienced the same from within the Linux kernel (Test Case 1 produces Ethernet LEDs, but not functioning, Test Case 2 produces no Ethernet LEDs).


So my question is this, is networking with the described mix of SW and HW revisions supported? If yes, what am I doing wrong? Where is it documented?


I have also tried using the Open SDA connection but found it unreliable and switched over to use the real serial port to connect to my terminal program on my PC.


The version of Linux that was present on the SD card:

Linux version 3.0.15-ts-armv7l (freescale@ubuntu) (gcc version 4.7.3 (Timesys 20140113) ) #2 Tue Jun 10 08:18:57 CEST 2014


the version of uboot:

U-Boot 2013.07-00004-gaae4ee8 (Jun 05 2014 - 16:00:42)


Here is my uboot environment:

=> printenv



bootargs=mem=128M console=ttymxc1,115200 root=/dev/mmcblk0p2 rw rootwait

bootcmd=run load_image2; run load_m4; run run_m4; run run_linux


bootscript=echo Running bootscript from mmc ...; source










load_image2= mmc rescan; fatload mmc 0:1 0x86000000 logo.bmp

load_m4=mmc rescan; fatload mmc 0:1 0x3f000000 accelerometer_example_twrvf65gs10_m4.bin


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}

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;



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;

run_linux=mmc rescan; fatload mmc 0:1 0x80010000 uImage-3.0-ts-armv7l; bootm 0x80010000

run_m4=mw.l 0x4006e028 0x3f000485; mw.l 0x4006b08c 0x00015a5a






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



Environment size: 2288/8188 bytes