61
NXPTM LPC2XXX and LPC17XX / Re: MOD-SMB380 I2C evaluation on LPC2378-STK
« on: February 18, 2010, 12:32:21 PM »
Things where going great, then I hit a mild hiccup and ran out of time to play with it this morning. I suspect my current ping hiccup isn't a huge deal.
It appears the express C++ version is around 100 to 200 megs. That downloaded just fine last night. I had originally thought I had to get the trail VS, which is a couple gigs. So I'm golden with VS now.
It took me a couple minutes to find preprocessor starting at pull down project --> uTasker properties --> configuration properties --> c/c++ --> preprocessor. I then saw this line "WIN32;_WINDOWS;_LPC23XX;ETHEREAL" which includes the _LPC23XX that I was looking to confirm. So I'm golden.
I changed the simulation IP to 10.10.10.3. Here's my ping attempt.
Also I set the simulation to look at my eth card that is used for my normal ether net activity. Here's my application.c.
I ran out of time, I might guess that that firewall is blocking traffic. I see the red an green lights on the simulation blink. Also I see it notes IP 10.10.10.3, so it appears it compiled in the new IP. Perhaps I have to assign a MAC to the simulation. Typically when my firewall has an issue, it will pop up a message inquiring if it should block or allow the traffic. I ran out of time this morning, so I'm a little blind about what the issue might be.
Any words of wisdom about this ping thing?
It appears the express C++ version is around 100 to 200 megs. That downloaded just fine last night. I had originally thought I had to get the trail VS, which is a couple gigs. So I'm golden with VS now.
It took me a couple minutes to find preprocessor starting at pull down project --> uTasker properties --> configuration properties --> c/c++ --> preprocessor. I then saw this line "WIN32;_WINDOWS;_LPC23XX;ETHEREAL" which includes the _LPC23XX that I was looking to confirm. So I'm golden.
I changed the simulation IP to 10.10.10.3. Here's my ping attempt.
Code: [Select]
C:\>ping 10.10.10.3
Pinging 10.10.10.3 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.10.10.3:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 10.10.10.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.111
Also I set the simulation to look at my eth card that is used for my normal ether net activity. Here's my application.c.
Code: [Select]
static const NETWORK_PARAMETERS network_default = {
(AUTO_NEGOTIATE /*| FULL_DUPLEX*/ | RX_FLOW_CONTROL), // {42} usNetworkOptions - see driver.h for other possibilities
{0x00, 0x00, 0x00, 0x00, 0x00, 0x00}, // ucOurMAC - when no other value can be read from parameters this will be used
{ 10, 10, 10, 3 }, // ucOurIP - our default IP address
{ 255, 255, 255, 0 }, // ucNetMask - Our default network mask
{ 10, 10, 10, 1 }, // ucDefGW - Our default gateway
{ 10, 10, 10, 111 }, // ucDNS_server - Our default DNS server
};
I ran out of time, I might guess that that firewall is blocking traffic. I see the red an green lights on the simulation blink. Also I see it notes IP 10.10.10.3, so it appears it compiled in the new IP. Perhaps I have to assign a MAC to the simulation. Typically when my firewall has an issue, it will pop up a message inquiring if it should block or allow the traffic. I ran out of time this morning, so I'm a little blind about what the issue might be.
Any words of wisdom about this ping thing?