1
µTasker general / Re: 1-Wire Protocol
« on: October 24, 2017, 09:02:05 PM »
Bit banging is one way to communicate. A UART/USART can also be used as a 1-wire master or there are 1-wire master ICs that communicate via I2C or SPI.
News:
Nov 2020: uTasker i.MX RT V1.4.12 is productive - with complete secure loading concept.
Follow uTasker updates at www.twitter.com/uTasker !!
Online Forum registration has now been disabled. Please send an email to an address at the bottom of the home page with your preferred user name and email address if you would like an account.
Return to uTasker main site: www.utasker.com
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
µTasker general / 1-Wire Protocol
« on: October 24, 2017, 04:39:44 PM »
Is there any out of the box support in uTasker for communicating with Maxim (Dallas Semiconductor) 1-Wire devices? If not, has anyone managed to successfully add this protocol to their uTasker based device (preferably Kinetis)?
3
NXPTM M522XX, KINETIS and i.MX RT / Re: K64F Ethernet
« on: June 07, 2017, 03:41:16 AM »
Erasing the entire flash solved the problem.
Is there an easy way to accomplish erasing the entire flash within Kinetis Design Studio? I ended up using manual OpenOCD commands through a GDB command line, which worked but had some other side effects that I had to deal with.
Is there an easy way to accomplish erasing the entire flash within Kinetis Design Studio? I ended up using manual OpenOCD commands through a GDB command line, which worked but had some other side effects that I had to deal with.
4
NXPTM M522XX, KINETIS and i.MX RT / K64F Ethernet
« on: May 30, 2017, 09:47:55 PM »
I enabled the Ethernet interface on my FRDM-K64F development board with uTasker 1.4.11 and I have not been able to successfully change the IP address, gateway, MAC address, etc.
I configure the default values in the network_default constant found in application.c, and disabled the SUPPORT_PROGRAM_ONCE and MAC_FROM_USER_REG defines in app_hw_kinetis.h but the development board starts with 255.255.255.255 as the IP address and gateway and a MAC address of FF:FF:FF:FF:FF:FF
This wouldn't be too bad as the IP, gateway, netmask and DNS can all be changed via menu; however, there is no command to change the MAC address.
The same behavior is seen in the Simulator too. Is there another location where uTasker gets the network configuration from?
I configure the default values in the network_default constant found in application.c, and disabled the SUPPORT_PROGRAM_ONCE and MAC_FROM_USER_REG defines in app_hw_kinetis.h but the development board starts with 255.255.255.255 as the IP address and gateway and a MAC address of FF:FF:FF:FF:FF:FF
This wouldn't be too bad as the IP, gateway, netmask and DNS can all be changed via menu; however, there is no command to change the MAC address.
The same behavior is seen in the Simulator too. Is there another location where uTasker gets the network configuration from?
Pages: [1]