Need help with development willing to pay

cancel
Showing results for 
Search instead for 
Did you mean: 

Need help with development willing to pay

Jump to solution
2,194 Views
andreas_anderss
Contributor I

I’m looking for an experienced embedded developer familiar with the FRDM K64F board, with its SDK and MCUXpresso who could help me to complete some tasks.

The primary problem is to load a C/C++-project  to the K64F board. Obviously there are several setup steps and initializations that we haven’t got right but we are in a hurry to get this problem solved.

We are willing to pay for your assistance.

Additional functions that we need:

Bootloader – We need to be able to upload an application to the board.

Console – We need to be able to connect to a console via USB and perform some functions like:

Instance the bootloader and transfer the new version of the application to the board.

Get version number of running application.

Transfer a log file from the board to a PC.

Enter connection information for an external device.

File handler – We need to be able to move files over USB and store it on an internal SD memory.

 

If you are interested in helping us with this project please send me your contact information so we can explain the functionality in more detail and also your payment.

0 Kudos
1 Solution
546 Views
mjbcswitzerland
Specialist V

Hi Andreas

As noted from your other thread about SD card / memory stick transfers this functionality (plus USB boot loader, USB console operation and control) are readily available in the uTasker project for your processor. This is immediately usable even in its free open source version on GitHub.

For $485 there is a professional version which includes 3 months of project support to secure mission critical projects.

If you need to further develop the NXP libraries to do the same it is something that can be done (I have been involved with many industrial Kinetis developments, including around 10 x K64 based ones and have around 5'000 hours experience on most Kinetis parts, and charge $65.- an hour for contract developments/training/consulting). Contact and details are on the uTasker web page. However it is certainly a much more time consuming and subsequently more expensive process that the already prepared solutions.

Note that the uTasker project can also be used together with, or alongside other libraries or with FreeRTOS and so can be used to simply compliment already invested development efforts.

Regards

Mark

Off-the-shelf loaders for K64 (FRDM-K64F):
http://www.utasker.com/docs/uTasker/uTaskerSerialLoader.pdf

View solution in original post

0 Kudos
6 Replies
546 Views
miduo
NXP Employee
NXP Employee

Hello,

NXP® Professional Support can provide help with your specific platform and software environment. We can help with everything from board design to production, including driver porting and integration. After purchasing a professional support package(100 hour minimum), you will need to supply NXP with the necessary hardware and tools to get started. If you have additional questions or want to learn more, contact us at: PROSUPPORT@nxp.com

See more detail here: Professional Support for Processors and Microcontrollers|NXP 

0 Kudos
546 Views
miduo
NXP Employee
NXP Employee

Hello,

The KDS is declining and we do not update it any more. We recommend the SDK which had a new release. You may download it and including the Software Components as below:

pastedImage_1.png

0 Kudos
547 Views
mjbcswitzerland
Specialist V

Hi Andreas

As noted from your other thread about SD card / memory stick transfers this functionality (plus USB boot loader, USB console operation and control) are readily available in the uTasker project for your processor. This is immediately usable even in its free open source version on GitHub.

For $485 there is a professional version which includes 3 months of project support to secure mission critical projects.

If you need to further develop the NXP libraries to do the same it is something that can be done (I have been involved with many industrial Kinetis developments, including around 10 x K64 based ones and have around 5'000 hours experience on most Kinetis parts, and charge $65.- an hour for contract developments/training/consulting). Contact and details are on the uTasker web page. However it is certainly a much more time consuming and subsequently more expensive process that the already prepared solutions.

Note that the uTasker project can also be used together with, or alongside other libraries or with FreeRTOS and so can be used to simply compliment already invested development efforts.

Regards

Mark

Off-the-shelf loaders for K64 (FRDM-K64F):
http://www.utasker.com/docs/uTasker/uTaskerSerialLoader.pdf

0 Kudos
546 Views
andreas_anderss
Contributor I

Thanks for your reply Mark.

I have now downloaded the project from github just to see if i could get uTasker to work before we buy it and followed the video on how to set it up. Im using MCUXpresso and the video shows how to get it to work in KDS and when i build i get this error:

/Hardware/Kinetis/kinetis.c:1414:31: error: 'PA_6_CLKOUT' undeclared (first use in this function); did you mean 'PC_3_CLKOUT'?

In the configuration i have chosen #define FRDM_K64F.

And im trying to build the application uTaskerSerialBoot.

Any suggestions?

0 Kudos
546 Views
mjbcswitzerland
Specialist V

Hi Andreas

MCUXpresso and KDS are almost the same with respect to importing the project. The following guide explains any minor differences to be respected (the most important being to copy the MCUXpresso project to the root): http://www.utasker.com/kinetis/compilers.html#MCUXpresso

I just checked out the OS version and built for the FRDM-K64F (this is the default) without the error. The line failing is

    #elif defined KINETIS_K64 && (PIN_COUNT == PIN_COUNT_144_PIN)
    _CONFIG_PERIPHERAL(A, 6, (PA_6_CLKOUT | PORT_SRE_FAST | PORT_DSE_HIGH)); // configure the CLKOUT pin
    #else
    _CONFIG_PERIPHERAL(C, 3, (PC_3_CLKOUT | PORT_SRE_FAST | PORT_DSE_HIGH)); // configure the CLKOUT pin
    #endif

whereby the FRDM-K64F has a 100 pin K64 (and doesn't have PTA6) and so it sets its CLKOUT pin on PTC3 instead. Have you adjusted the define for PIN_COUNT to the 144 pin chip?

To work around it in case it can't be explained, either remove the #elif option for CLKOUT on PTA6 or add
#define PA_6_CLKOUT              PORT_MUX_ALT5
so that it selects the (unused) pin anyway.

In case you built for TWR_K64F120M (instead of FRDM_K64F) this was really a missing define on GIT Hub. I just checked in a new kinetis.h which includes the PA_6_CLKOUT definition.

Regards

Mark

0 Kudos
546 Views
andreas_anderss
Contributor I

No i have not changed the pincount. This is what i found:

#elif defined FRDM_K64F
  //#define KINETIS_FLEX                                                 // X part with flex memory rather than N part with program Flash only
    #define PIN_COUNT           PIN_COUNT_100_PIN                        // 100 LQFP pin package
  //#define PIN_COUNT           PIN_COUNT_121_PIN                        // 121 XFBGA
  //#define PIN_COUNT           PIN_COUNT_144_PIN                        // 144 LQFP/MAPBGA pin package
    #define PACKAGE_TYPE        PACKAGE_LQFP
  //#define PACKAGE_TYPE        PACKAGE_MAPBGA
    #define SIZE_OF_FLASH       (1024 * 1024)                            // 1M FLASH
    #define SIZE_OF_RAM         (256 * 1024)                             // 256k SRAM

I will try your workaround.

I have also sent an email to uTasker regarding a support session.

BR

Andreas

0 Kudos