Dear all, I've made my own board of Cyclone IV EP4CGX110CF23C7. And i want to make a ethernet module with DP83848C which is surpported by the TSE core. However, when i have completed my SOPC system and downloaded the nios program, it seems that something wrong happened to my program and i am confused by this problem for several days. When i run my project as NIOSII hardware on NIOS SBT v12.1, the nios ii console displays as following: 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:16:36:fc:14:2d static ip address is 192.168.1.234 prepped 1 interface, initializing... netinit: calloc failed getting buffer 17 inet startup error: unable to initialize net panic: ip dtrap - needs breakpoint ip_exit: calling func 0x9e7a4 Here are some attachments of my program. PS: 1. I turned off the DHCP and set the board IP address 192.168.1.234. 2. I created the program from the template Simple Socket Server. 3. There is no NAND flash on my board and i set my board MAC address 00:16:36:fc:14:2d

From the calloc error message, it looks like you don't have enough memory for the embedded system. You can try and reduce the number of buffers in ipport.h, increase the size of your onchip_mem, or connect the Nios CPU to an external RAM (if you have one on board).

--- Quote Start --- From the calloc error message, it looks like you don't have enough memory for the embedded system. You can try and reduce the number of buffers in ipport.h, increase the size of your onchip_mem, or connect the Nios CPU to an external RAM (if you have one on board). --- Quote End --- Thanks a lot. I followed your advise and the result seems to be better. But when i ping the board with cmd or telnet, there seems to be no connection. The following shows the Nios II Console content: 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:16:36:fc:14:2d static ip address is 192.168.1.234 prepped 1 interface, initializing... [tse_mac_init] info : tse mac 0 found at address 0x00203000 info : phy national dp83848c found at phy address 0x1f 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 info : phy[0.0] - restart auto-negotiation, checking phy link... info : phy[0.0] - auto-negotiation passed info : phy[0.0] - checking link... info : phy[0.0] - link established info : phy[0.0] - speed = 100, duplex = full ok, x=0, cmd_config=0x01000000 mac post-initialization: cmd_config=0x05000203 [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) simple socket server starting up [sss_task] simple socket server listening on port 30 created "simple socket server" task (prio: 4)

There doesn't seem to be anything wrong from the terminal output. I suggest that you use a network sniffer (such as Wireshark) on the PC you are using to connect to the board, and signaltap on the FPGA to check if anything is coming in or out on the interface with the PHY chip.

I've tried the Wireshark to grab the packets but i failed. It seems no connection between the PC and the FPGA. The attachment is the output of the Wireshark.

From the terminal output is seems that the set IP address is 192.168.1.234, but you are trying to ping 192.168.0.202

Problems with Cyclone IV and DP83848C | Altera Community

27 Replies

Altera_Forum
Honored Contributor
12 years ago
From the calloc error message, it looks like you don't have enough memory for the embedded system. You can try and reduce the number of buffers in ipport.h, increase the size of your onchip_mem, or connect the Nios CPU to an external RAM (if you have one on board).
Altera_Forum
Honored Contributor
12 years ago
--- Quote Start ---
From the calloc error message, it looks like you don't have enough memory for the embedded system. You can try and reduce the number of buffers in ipport.h, increase the size of your onchip_mem, or connect the Nios CPU to an external RAM (if you have one on board).
--- Quote End ---

Thanks a lot. I followed your advise and the result seems to be better.
But when i ping the board with cmd or telnet, there seems to be no connection. The following shows the Nios II Console content:

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:16:36:fc:14:2d
static ip address is 192.168.1.234
prepped 1 interface, initializing...
[tse_mac_init]
info : tse mac 0 found at address 0x00203000
info : phy national dp83848c found at phy address 0x1f 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
info : phy[0.0] - restart auto-negotiation, checking phy link...
info : phy[0.0] - auto-negotiation passed
info : phy[0.0] - checking link...
info : phy[0.0] - link established
info : phy[0.0] - speed = 100, duplex = full
ok, x=0, cmd_config=0x01000000

mac post-initialization: cmd_config=0x05000203
[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)

simple socket server starting up
[sss_task] simple socket server listening on port 30
created "simple socket server" task (prio: 4)
Altera_Forum
Honored Contributor
12 years ago
There doesn't seem to be anything wrong from the terminal output. I suggest that you use a network sniffer (such as Wireshark) on the PC you are using to connect to the board, and signaltap on the FPGA to check if anything is coming in or out on the interface with the PHY chip.
Altera_Forum
Honored Contributor
12 years ago
I've tried the Wireshark to grab the packets but i failed. It seems no connection between the PC and the FPGA. The attachment is the output of the Wireshark.
Altera_Forum
Honored Contributor
12 years ago
From the terminal output is seems that the set IP address is 192.168.1.234, but you are trying to ping 192.168.0.202
Altera_Forum
Honored Contributor
12 years ago
No,no,no....I've just changed my ip address to 192.168.0.202 but no changed the terminal result to this thread.
multiple-attachments.zip228 KB
Altera_Forum
Honored Contributor
12 years ago
Okay. Your board isn't even answering the first ARP request, so you need to use signaltap to figure out if the ARP request gets on the PHY's rx interface, and if your system answers on the PHY's tx interface.
Altera_Forum
Honored Contributor
12 years ago
how did you connect the computer and the FPGA board? if you directly connected them by only one ethernet cable that maybe the problem. You may use a switch.
Altera_Forum
Honored Contributor
12 years ago
--- Quote Start ---
Okay. Your board isn't even answering the first ARP request, so you need to use signaltap to figure out if the ARP request gets on the PHY's rx interface, and if your system answers on the PHY's tx interface.
--- Quote End ---

Uhm..But can you introduce it more detailedly ? I'm a beginner in the field of network and i cannot recognize how the ARP request transmitted to the board.
Or may i have your email or msn/QQ in order to contact you conveniently.
The following is the signaltap screen shot when ping the board.
Altera_Forum
Honored Contributor
12 years ago
--- Quote Start ---
how did you connect the computer and the FPGA board? if you directly connected them by only one ethernet cable that maybe the problem. You may use a switch.
--- Quote End ---

I've tried to use a 10/100Mb switch but there is still no connect between the board and the host pc

Forum Discussion

Problems with Cyclone IV and DP83848C

27 Replies

Recent Discussions

JTAG_UART stuck in printf

Recommended Quartus Prime Standard Edition for Nios V Development on MAX 10 FPGA (10M25DAF4817G)

University Program IP for NiosV

NIOS SDK SBOM/FOSS info

NiosV µC/OS-II