Topics

1

NXP^TM M522XX, KINETIS and i.MX RT / Getting started with SPI devices

« on: November 10, 2014, 07:42:31 AM »

Hi Mark, I have not been working on this project enough lately, but I think at the moment it makes the most sense for me to try to get SPI devices working.  One is still the Wiznet W5100 in case I cannot figure out how to get the Micrel chips working in uTasker (highly likely), along with an RF module.

I started by looking through the code for SPI-related #defines, and I found #define SPI_INTERFACE.  I added that to my config.h, but the uTasker project doesn't build because it looks like the implementation of fnOpenSPI(SPITABLE *pars, unsigned char driver_mode) is missing.  Can you point me to any documents that you might already have available that will get me going in the right direction?  I looked at the document for the SPI EEPROM file system, but it specifically says to *not* use it with SPI_INTERFACE, so I figured that it would not be helpful to me.    Thank you!

2

µTasker general / General simulator problems

« on: September 25, 2014, 03:14:47 PM »

I'm going through the uTasker - Kinetis Tutorial and felt that it makes the most sense to familiarize myself with uTasker using the simulator first, and then move on to real hardware (FRDM-K64F).

I have made the necessary modifications to the Simulator project using VS2010.  I have set my simulation UART0 to COM9, and have set my network settings as described in the manual (only modified for my particular network).  The project compiles and runs just fine.

The problem I see is that *nothing* in the menus work.  I started by selecting LAN -> Select Working NIC, and nothing happens.  I then tried UARTs -> Simulate a receive message on UART0.  I created UART0.txt in my Debug folder, but nothing gets read from the file as far as I can tell.  So I tried *all* of the other menu commands, and nothing happens.  It's also strange that in my application window, the IP says x.x.x.x:yy-yy-yy-yy-yy-yy instead of having a real IP and MAC address.

Furthermore, the first three times I ran the application, the board was a green PCB, but now it looks like an actual FRDM-K64F.  I haven't changed *anything* other than what I have already described.

Does anyone know what I'm doing wrong here?

3

NXP^TM M522XX, KINETIS and i.MX RT / KDS / Eclipse newbie could use some help getting started

« on: September 24, 2014, 09:10:17 PM »

Hi Mark, I'm trying my best to get running with KDS and uTasker on my FRDM-K64F, but so far I am completely failing.

First of all, I am relying on two documents to get started: 1) the readme file and 2) the uTasker v1.4 User Guide - First Steps PDF.

Steps 1-3 in the readme are obviously very basic and I have all of the software downloaded and installed.
Step 4 I couldn't do because the software demo seems to be for the "tower board", which I do not have.
Once I got to step 5, I consulted the User Guide, but found the one specific to v1.4.

Here's where I got hung up.  After I made a copy of Applications/uTaskerV1.4 and configured the simulator in Visual Studio, the next step was to add a new task to my project.

Specific questions at this point:

• when you say "add a new source file to the project", by "project" are you talking about the renamed project I created in the Applications folder, or are you saying that it should be in the root extracted uTasker folder?  I've done it both ways -- when I look at the Project Explorer in KDS, should I have the Application, Hardware, stack, and uTasker folders, or should I just see Includes?  Please see the following image:
  
• If I put main.cpp into Applications/uTaskerDemo and then build, I just get a "Nothing to build for project uTasker" message
• If I put main.cpp into the other project that just shows Includes, then I get the error "fatal error: config.h: No such file or directory"

If you could help me fill in the details that I'm missing, I'd really appreciate it so I can start trying out uTasker.  I apologize for these questions if the answers seem obvious.  I'm just having a little trouble piecing the bits together.  Thank you!