Messages

46

NXP^TM M522XX, KINETIS and i.MX RT / i.MX Processors

« on: October 02, 2017, 10:05:38 PM »

Any support for i.MX processors, Mark?

I'm thinking of using one of these processors for the HDMI output capabilities.

Thanks.

Phil

47

µTasker general / Re: Updating uTasker

« on: June 30, 2017, 02:29:24 PM »

Great suggestion, Mark.

Most appreciated!

48

µTasker general / Updating uTasker

« on: June 27, 2017, 06:05:33 PM »

Mark,

Is there any information in regards to updating uTaskerV1.4.10 to the latest?  (V1.4.12 in this case)

For example, save the config.h and app_hw_xxxx.h files, copy entire directory structure over current version, then overwrite config.h and app_hw_xxxx.h files that were previously saved.

Thank you.

Phil

49

NXP^TM M522XX, KINETIS and i.MX RT / uTasker Web Server PDF?

« on: February 27, 2017, 09:45:37 PM »

Mark,

Is there a document which explains how the uTasker web server works?

I'd like to learn more about how http.c is handling web service calls and the interaction between http.c routines and WebInterface's routines (such as fnHandleWeb).

Thanks.

Phil

50

NXP^TM M522XX, KINETIS and i.MX RT / Re: DHCP Host Name

« on: February 27, 2017, 08:21:32 PM »

Thank you, Mark.

I must admit another thing I found:  The Ethernet cable seems to be just fine. We tested, it turns out the cable is a cross over cable. I'm not sure how I got ahold of this special cable but it through me for a loop until it was tested. Later I found a small label on the cable saying it was indeed a cross over cable.

Just an FYI. It may explain certain behaviors.

Phil

51

NXP^TM M522XX, KINETIS and i.MX RT / Re: DHCP Host Name

« on: February 25, 2017, 09:35:39 PM »

Mark,

Problem resolved.

Your comment, "Ethernet is sending but not receiving", had me recheck the hardware looking for a problem with one of the Ethernet lines. Turns out the problem was not with the board at all. The problem was with the Ethernet cable. At some point, the cable got munched or somehow damaged. Replacing the cable corrected the problem. DHCP Listener is activated and after two hits the DHCP Successful flag happens and the IP is set just as it should.

Thanks, Mark.

Phil

52

NXP^TM M522XX, KINETIS and i.MX RT / Re: DHCP Host Name

« on: February 24, 2017, 09:18:28 PM »

Mark,

Last edit in the dhcp.c file is dated 15.10.2015.

Tried setting IP to 0.0.0.0 but didn't work. Had to modify your uMemset routine to:  uMemset(&network[DEFAULT_NETWORK].ucOurIP[0], 0, IPV4_LENGTH);
The uMemset command you suggested failed otherwise.

fnDHCPListener is actually called fnDCHPListner in my copy of dhcp.c. This routine is never called. I have put in debug stops and even put in a fnDebugMsg to verify and it isn't called. Maybe this is a key fact in which to diagnose the problem.

Thoughts?

Phil

53

NXP^TM M522XX, KINETIS and i.MX RT / Re: DHCP Host Name

« on: February 23, 2017, 06:33:38 PM »

Attached you will find the Wireshark capture file from the point of starting the MCU to the point where uTasker responds with a DHCP Missing Server failure.

Thank you.

Phil

54

NXP^TM M522XX, KINETIS and i.MX RT / DHCP Host Name

« on: February 23, 2017, 02:53:28 AM »

Mark,

I have a router connected to a router. Each router supports DHCP for the devices connected to each.
Router 1 has a base IP address of 192.168.0.1 and the second has a base address of 192.168.1.1.
Our device isn't able to get an appropriate IP address via DHCP. uTasker says the DHCP server is missing or not responding. I believe this is because
DHCP is using the DEFAULT_NETWORK which is 192.168.0.1. This is not the server to which I am connected and may be the reason.
It appears that there is a definition DHCP_HOST_NAME which signals to get the DHCP server address from cDeviceIDName. This appears
to be a string of 21 byte length. I assume this is the address of the DHCP Server which I would use a uStrcpy to set to "192.168.1.1".
However, I am still not able to get an IP address via DHCP. I know the DHCP service is available because I have other devices that regularly
connect via DHCP and get proper addresses. The MAC address is set to a proper address so this should not be an issue.

Any idea how I can resolve this problem getting a proper DHCP address?

Thank you.

Phil