Errors with the FRDM-K64F and KDS

cancel
Showing results for 
Search instead for 
Did you mean: 

Errors with the FRDM-K64F and KDS

1,923 Views
stevedigney
Contributor I

In my project Using the FRDM-K64F board and KDS I am getting the following 4 errors:

 

Description:

     Program "arm-none-eabi-gcc" not found in PATH         

Location:

     Project Properties, C++ Preprocessor Include.../Providers, [CDT GCC Built-in Compiler Settings Cross ARM] options

Type:

     C/C++ Scanner Discovery Problem

Description:

     Program "arm-none-eabi-g++" not found in PATH

Location:

     Project Properties, C++ Preprocessor Include.../Providers, [CDT GCC Built-in Compiler Settings Cross ARM] options

Type:

     C/C++ Scanner Discovery Problem

    

Description:

     Generator: FAILURE: Unexpected status of script: Drivers\Kinetis\TimerInt.drv, please contact Freescale support.       

Location:

     TI1

Type:

     Processor Expert Problem

    

Description:

  Generator: FAILURE: Unexpected status of script: Drivers\Kinetis\InitClockGate.prg, please contact Freescale support.

Location:

   TSS1

Type:

     Processor Expert Problem

I am using the latest processor expert values from:

  https://github.com/ErichStyger/mcuoneclipse/tree/master/PEupd

I am trying to duplicate Erich Styger's project Data Logger with the FRDM-K64F Board except that I am using Kinetis Design Studio

Tags (3)
0 Kudos
3 Replies

61 Views
BlackNight
NXP Employee
NXP Employee

Hello,

the first thing is a reported by the built-in Eclipse scanner. See KDS release notes (Kinetis Design Studio V1.0.1 Beta Release Notes) under 'Building'. You can ignore that error/warning (it will go away next time you build).

The second thing is the generator failure: it looks you have created a Kinetis SDK project? Unfortunately you cannot use the 'previous' components with the Kinetis SDK as they are not compatible. The non-beta version of KDS should filter out the components which are not compatible.

As solution for your project: that data logger project has been created as 'non-SDK' project. So create a project on your end with 'SDK' option *not* enabled, and then you will be able to build that data logger project.

I hope this helps,

Erich

0 Kudos

61 Views
stevedigney
Contributor I

Erich,

Thanks for your quick reply.

I have a request for your help on my project when I finally get the logger working :

I need to be able to get the data from the SD card using the Ethernet port.

Would it be possible for you to help me do this?

It might be a good addition for your DataLogger project, I have seen lots of people having problems getting the Ethernet to work.

Thanks,

Steve Digney

0 Kudos

61 Views
mjbcswitzerland
Specialist V

Steve

I have attached a binary for the FRDM-K64F which performs data logging to an SD card and allows the data to be read either via USB-MSD (connect the board via USB and it appears as a hard drive and the logged data can be copied to the PC) or over Ethernet by FTP (connecting via FTP on its IP address allows the SD card content to be worked with and so the logged data to be retrieved).

I don't know whether you are interested in the accelerometer data but this is being sampled by the SW at 50Hz and the output can be viewed on the Virtual COM UART connection (115kBaud) or via TELNET connection to the board's IP address (when connected, go to the USB menu and enable the output with the "acc_on" command).

The ADC input on pin 7 of J4 is being sampled at 8kHz and transferred to the DAC output on pin 11 of the same connector (after a 1s delay) and If you press the button SW3 once it will start saving the ADC data to the SD card in a file that is created called "FRDM_K64F.wav". If a microphone is connected to this ADC input it will be recording the sound and can record for as long as the SD card has place (4GByte card could record for about 9 days). Press the same button a second time to stop the recording. [Normally the green LED blinks at 2.5Hz but it flashes faster when the board is in the processor of recording to the file]. The data is saved as a WAV file (due to the audio type data) and the recording can be started and stopped, whereby the new data will each time be appended to the file that already exists.

To make Ethernet testing easier the board has two IP addresses. The first is fixed at 192.168.0.4 so if it suits the local network it can be contacted directly. The second IP address that the board uses is resolved using DHCP so it will also be contactable on whatever IP address it obtaines from the local network - a local network broadcast ping (eg. ping 192.168.0.255 on 255.255.255.0) can be used to find the device, or the ELZET80 discovery tool as described here: http://www.elzet80.com/network-device-discovery.html

There is also a web server running so if there is a directory called "dir1" on the SD card a start page called "index.htm" can be put inb it (the default start page) and then any additional web content that the server should serve too. The web server could be used to display logged data if the data is used together with some java script code, etc.

I build this application using KDS for the FRDM-K64F in the uTasker project [see New Freedom FRDM-K64F board]  which contains all resources to do such things very easily. This configuration will run on all K processors/boards (the Ethernet part limited to types with EMAC of course) and logging of multiple data sources can be easily added.

Regards

Mark

µTasker Kinetis support

P.S: WIth the mdeb loader installed on the FRDM-K64F the attached binary can be dragged to the board when it appears as a hard drive. Alternatively it can be loaded from KDS using its Flash utility.

0 Kudos