Author Topic: STM3210C NetWork & USB...  (Read 5810 times)

Offline jminet

  • Newbie
  • *
  • Posts: 2
    • View Profile
STM3210C NetWork & USB...
« on: December 09, 2010, 03:47:24 PM »
Hello,
 
 I have just put uTasker_STM32_Target.zip on STM3210C dev board.

 A lot of things works very well: sdcard, graphic display, console on RS232....

 But i have two problems :

 1- the network doesn"t work: with ipstat on the STM3210C board, i have Rx packet for UDP, TCP, ICMP & ARP, But the board never answer when the PC do a ping, a telnet or http request.... ???? (IP address is ok (192.168.0.3), MAC address is 00-11-22-33-44-55, firewall is OFF on windows)

 2- USB doesn't work. When i plug the USB nothing happens on the PC ???? (LED D6 goes green)

 Any ideas ???
 

Offline mark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2962
    • View Profile
    • uTasker
Re: STM3210C NetWork & USB...
« Reply #1 on: December 09, 2010, 05:30:29 PM »
Hi

1) Does the IP address match your network. Check whether the counters are counts of its address or for foreign addresses. Are there any Tx counts?

2) There is no USB suppport in the code so USB will not do anything.

Regards

Mark

Offline jminet

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: STM3210C NetWork & USB...
« Reply #2 on: December 10, 2010, 09:42:29 AM »
Ok for USB....

For the network, STM3210C works with ST orginal firmware (ping & http request).

So i think, it's not a hardware problem.
With uTasker it seems that STM3210C never answer.... first i saw that the PC can't know the MAC address. I added manualy the MAC address with arp -s 192.168.0.3 00-11-22-33-44-55 and them make some test, here is the result :

PC ping 4 times to 192.168.0.8 (no device with this IP adress)
Statistiques Ping pour 192.168.0.8:
    Paquets : envoyés = 4, reçus = 0, perdus = 4 (perte 100%)


uTasker Ethernet Statistics

Total Rx frames = 4
Rx overruns = 0
Rx ARP = 0
Rx ICMP = 0
Rx UDP = 0
Rx TCP = 0
Rx checksum errors = 0
Rx other protocols = 0
Foreign Rx ARP = 4
Foreign Rx ICMP = 0
Foreign Rx UDP = 0
Foreign Rx TCP = 0
 otal Tx frames = 0

-------------------------------------------------------------
PC ping 4 times to 192.168.0.3 (STM3210C board)
Statistiques Ping pour 192.168.0.3:
    Paquets : envoyés = 4, reçus = 0, perdus = 4 (perte 100%)

uTasker Ethernet Statistics

Total Rx frames = 8
Rx overruns = 0
Rx ARP = 0
Rx ICMP = 4
Rx UDP = 0
Rx TCP = 0
Rx checksum errors = 0
Rx other protocols = 0
Foreign Rx ARP = 4
Foreign Rx ICMP = 0
Foreign Rx UDP = 0
Foreign Rx TCP = 0
 Otal Tx frames = 4

-------------------------------------------------------------
telnet 192.168.0.3
Connexion à 192.168.0.3...Impossible d'ouvrir une connexion à l'hôte, sur le por
t 23: Échec lors de la connexion


uTasker Ethernet Statistics

Total Rx frames = 11
Rx overruns = 0
Rx ARP = 0
Rx ICMP = 4
Rx UDP = 0
Rx TCP = 3
Rx checksum errors = 0
Rx other protocols = 0
Foreign Rx ARP = 4
Foreign Rx ICMP = 0
Foreign Rx UDP = 0
Foreign Rx TCP = 0
otal Tx frames = 7

???


Offline mark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2962
    • View Profile
    • uTasker
Re: STM3210C NetWork & USB...
« Reply #3 on: December 10, 2010, 10:43:24 PM »
Hi

From the statistics it is clear that the RX is OK:

1) Foreign Rx ARP = 4 (when sending ping to 192.168.0.8 - foreign address). The PC will send 4 ARP broadcasts and these are received but they are for a foreign IP address. Therefore the Rx ARP count is correct.

2) When you ping the IP address the rx counter indicates: Rx ICMP = 4. That means that the pings were counted.
The tx indicates 4 and these are probably the ping answers. However I can't explain why you don't receive them.

3) The TELNET attempt has counted TCP reception for the IP address (Rx TCP = 3). Also the tx count indicates that these were answreed. Again I can't explain why the transmissions are not received.

Have you checked whether the transmissions are seen on the Etherent with Wireshark? If there is something, check the IP checksum since the chip can perform check sum offfloading - maybe this is not working correctly on transmission, however I didn't have any problem swith it?

4) Since it seems that the rx can identify ICMP and TCP receptions for its own IP address I would expect that without the ARP entry it would also indicate Rx ARP = x, when it receives these.

Regards

Mark