Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
21332 Discussions

Getting Started - Simple Socket Server, Board Test System, Cyclone III

Altera_Forum
Honored Contributor II
1,007 Views

I am trying to run the Simple Socket Server using the Board Test System for a Cyclone III Dev Board. In the Terminal Emulator everything seems to be working. It prints this information: 

 

 

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 

Please start Command Prompt 

Start->Run->cmd or type cmd in "Search programs and files" field in Wndows 7 

then type 

"telnet 10.32.201.4 30"  

to connect 

 

 

Window 7 users may need to activate telnet first. 

Control Panel->Programs->Turn Windows features on or off-> enable telnet 

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 

 

 

 

 

I have activated telnet but my computer cannot connect. I'm trying to determine if this issue is being caused by my FPGA board, my computer, my network, or my software. I am using a Linksys Ethernet switch to link my Cyclone III, Computer, and Internet. I've been told that the problem might be due to an extra VLAN tag that is automatically inserted into the work TCP/IP (apparently there is a way to turn this off but the protocol is hardwired into some machines and can't always be disabled). If this is the case then I'm not sure I have many options.  

 

 

I'm pretty new to this stuff and I'm not sure what the socket server is actually doing. Should I be able to run the server without internet access? I tried connecting the FPGA to the computer, while disconnecting the internet cable, and it doesn't work at all (it doesn't get to the point where it tells me to use command prompt). Additionally, it's already communicating with the computer at some basic level because it's able to create the simple socket server and tells me which port it's listening on. If the tag is in the Ethernet protocol, would it still be able to get that far? It seems like it is communicating and functioning to some degree, but I can't figure out why it doesn't work. 

 

 

Here's the full print out. Any help is much appreciated: 

 

 

=============== Software License Reminder ================ 

This software project uses an unlicensed version of the NicheStack TCP/IP 

Network Stack - Nios II Edition. If you want to ship resulting object 

code in your product, you must purchase a license for this software from 

Altera. For information go to: "http://www.altera.com/nichestack

===================================================== 

InterNiche Portable TCP/IP, v3.1  

 

 

Copyright 1996-2008 by InterNiche Technologies. All rights reserved.  

prep_tse_mac 0 

Your Ethernet MAC address is 00:07:ed:11:41:a6 

prepped 1 interface, initializing... 

[tse_mac_init] 

INFO : TSE MAC 0 found at address 0x20003000 

INFO : PHY Marvell 88E1111 found at PHY address 0x12 of MAC Group[0] 

INFO : PHY[0.0] - Automatically mapped to tse_mac_device[0] 

INFO : PHY[0.0] - Restart Auto-Negotiation, checking PHY link... 

INFO : PHY[0.0] - Auto-Negotiation PASSED 

MARVELL : Mode changed to RGMII/Modified MII to Copper mode 

MARVELL : Enable RGMII Timing Control 

MARVELL : PHY reset 

INFO : PHY[0.0] - Checking link... 

INFO : PHY[0.0] - Link not yet established, restart auto-negotiation... 

INFO : PHY[0.0] - Restart Auto-Negotiation, checking PHY link... 

INFO : PHY[0.0] - Auto-Negotiation PASSED 

INFO : PHY[0.0] - Link established 

INFO : PHY[0.0] - Speed = 100, Duplex = Full 

OK, x=0, CMD_CONFIG=0x00000000 

 

 

MAC post-initialization: CMD_CONFIG=0x04000203 

[tse_sgdma_read_init] RX descriptor chain desc (1 depth) created 

mctest init called 

IP address of et1 : 192.168.1.234 

Created "Inet main" task (Prio: 2) 

Created "clock tick" task (Prio: 3) 

Acquired IP address via DHCP client for interface: et1 

IP address : 10.32.201.4 

Subnet Mask: 255.255.255.0 

Gateway : 10.32.201.1 

 

 

Simple Socket Server starting up 

[sss_task] Simple Socket Server listening on port 30 

Created "simple socket server" task (Prio: 4) 

 

 

 

 

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 

Please start Command Prompt 

Start->Run->cmd or type cmd in "Search programs and files" field in Wndows 7 

then type 

"telnet 10.32.201.4 30"  

to connect 

 

 

Window 7 users may need to activate telnet first. 

Control Panel->Programs->Turn Windows features on or off-> enable telnet 

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 

 

UPDATE: 

 

This issue has been resolved. Turns out the FPGA Ethernet MAC address needed to be added to the network before it was allowed to communicate. NO VLAN TAG!
0 Kudos
0 Replies
Reply