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.


Messages - Ian

Pages: [1]
1
Thanks.  I have the TWR-K60 demo going.  The problem was the .htm files were installed in the root directory and the server expected them in "dir1".  So that is fixed.

Last problem - Simple one:

When I load the uTaskerKinetisV1.4.5  project into CW10.6, I get this message at startup:
    References to ${workspace_loc:<resource>} macro were found in project settings.
    Using this macro could cause unexpected errors when the resource is not open or available.. 
    Using the ${ProjDirPath}  macro is preferable.

Then the following errors in the problems window-
    Program "g++" not found in path
    Program "gcc" not found in path 

Program "g++" not found in PATH   Project Properties, C++ Preprocessor Include.../Providers, [CDT GCC Built-in Compiler Settings Cross ARM] options        C/C++ Scanner Discovery Problem


I have compared the v_1.4.4 and the v1.4.5 projects and can't find any difference.

Ian

2
HI Mark, thanks for your help with this.  The problem appears to be the I2C isn't enabled somewhere (IIC_INTERFACE  *IS* defined in config.h) Menu item 7 from the debug uart only has "up" and "quit" as options.  It's not critical that I get this working if it is only a config problem.

I have have moved on to the TWR-K60 demo.  I can get it to build, and it runs properly on the simulator ( which is quite impressive), but the htm pages don't show in the browser. I get "uTasker - Error 404".  They do work when running the simulator.  "dir" show that all the files are there on the SDCARD.  Something simple missing...?

Ian

3
Hi Mark - I'm nearly there.  It is compiling, downloading, running and enumerating as a mouse. The green LED flashes and the LCD shows USb.  It just doesn't work as a mouse - no cursor movement and no effect from the buttons.  I followed the directions in the video twice and each time have the same result. 

Can you suggest how the debug? Using CW10.6.

Ian

4
Thanks Mark! Lots of detail made it quick and simple.  Now I am stuck just after #3.  The P&E Connection Assistant window pops up showing:

OpenSDA on USB1 (Name=...) (Autodetected)

but also the message

"An error occurred while connecting to the interface hardware or target specified in the Launch Configuration Dialog."

I really expected it to just work!  I think I must be missing something in the configuration of the debug connection.  Any more thoughts on this issue?

Ian

5
Hello,
I am having three problems with the demo for the FRDM-KL46 board described here:
µTasker Quick Start Video Guide for Kinetis and Codewarrior 10.5.

All problems are related to the tools or OS, not the code.
1) I can't find the linker file described in the video: "KL_256_32.ld"  I found all the other ones including "KL_128_16.ld" for the smaller part.  Does this exist somewhere else in the installed projects?

2) The .bin and .srec files are not generated because the "generate.bat" has no path set to the compiler tools.
arm-none-eabi-objcopy  --output-target=binary uTaskerV1_4.elf uTasker_V1.4.bin
arm-none-eabi-objcopy  --output-target=srec uTaskerV1_4.elf uTasker_V1.4.srec

I am using a fresh install of Win 8.1.  What is the best way resolve this?

3) CW doesn't recognize the USB interface on the FRDM-KL46 board as an openSDA interface so I can't run the debugger (and probably the flash programmer if I could generate the .bin file). It does innumerate as an MSD device.  I expect there is something obvious I am missing...  Anybody have any idea's or best way to approach?

Thanks in advance,
Ian

Pages: [1]