We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
hi we are using mcbstm32c board. we used and tried every examples (we downloaded examples from keil ) on this board with keil . all examples worked succesfully except network examples . we could not communnicate board to pc . we used cross-over cable . and we did every stage on datasheet. but we could not make it . how can we fix it?
Hi, I just tested a few of our Ethernet examples on the MCBSTM32C board and they worked as expected. The easiest way to test these examples is to connect the MCBSTM32C board with a LAN which has a DHCP server. Directly after connecting the board you should see its IP address on the GLCD. Then you can access the board with this IP address or its NetBIOS name (mcbstm32c).
It is also possible to connect this board via cross-over cable directly to a PC, but there are some things to consider.
Automatic IP address assignment (AutoIP): Our examples support the automatic assigment of the IP address when no DHCP server is available. Please see the following links: www.keil.com/.../using_ethernet_interfaces.html en.wikipedia.org/.../Link-local_address Please note that it takes up to 2 minutes until your PC and also the application running on the MCBSTM32C board will negotiate an IP address in the same subnet. You will see an IP address starting with 169.254.x.x on the GLCD of the board and you can also check the IP address of your PC with the 'IPconfig' command.
Manual IP address assignment: You can assign a fixed IP address to the board and your PC. For the board, this is done in the configuration file Net_Config_ETH_0.h. On your PC you can assign a fixed IP addresss in the network settings of the Windows operating system. Both IP addresses need to be in the same subnet.
Hope this helps you.
Hans Schneebauer Technical Support Team Germany
I had a similar problem but by reviewing Wireshark logs I have found that the NIC connected to the board didn't resolve correctly the board address. I had to add the MAC address of the board into the ARP table of the PC for this network card in order to get both communicate together.
Check with the command "arp -a" in a command prommpt.
Maybe that could help you.
Did you have this NIC issue when doing a soft reset or a power cycle?
Sometimes, I had it when the external PHY is not done resetting when the ST32 is already started executing.
When this every now and then event happened, the board acted like it was communicating to the PHY, and sending messages, but the board would not transmit.
To check,run wireshark on the PC, and then compare against the debug messages from the debug variant of the TCP stack:
http://www.keil.com/support/man/docs/rlarm/rlarm_tn_debug_en.htm