I/O with Host via OpenSDA

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

I/O with Host via OpenSDA

894 Views
shauldorf
Contributor V

Hello all;

 

I’m newer to Kinetis and KDS.

I use KDS3.0 & KSDK1.2 with FRDM-K64F and FRDM-KL25Z.

 

This is my KDS Installation

46268_46268.jpgInstall Details.jpg

 

I try to reproduce I/O demos based on two Erich Styger posts:

  • printf() and scanf() with GNU ARM Libraries, using ConsoleIO component.
  • Using a Terminal Input and Output; *without* printf() and scanf(), using Term component

 

The posts are old, Erich have used different tools chain.

Maybe not everything there is relevant, but they are excellent reference for beginners like me.

 

I’m looking for some reasonable explanation for:

 

 

FRDM-KL25Z

Project build:

  1. Device page: processor to be used Board,
    FRDM-KL25Z
  2. Rapid Application Page: KSDK-none,
    PE-selected

Generates following error:

46269_46269.jpgKL25 Error.jpg

 

 

FRDM-K64F

 

Project build:

  1. Device page: processor to be used Board, FRDM-K64F
  2. Rapid Application Page: KSDK-none, PE-selected

 

I ran into two problems without logical explanation

 

 

1.   "ConsoleIO" - post

        “printf/scanf” post I/O is working. The only unexplained obstacle is speed limit to 1200 baud.

 

        If in “Component Inspector” for IO1:Serial_LDD:

          Select folder “CPU clock/configuration selection”

          Change the “Clock configuration 3” to disabled

          There is no speed limit (tested in 115200 baud)

 

(String and Char) - post

          SendStr method work but no response to ReadChar or ReadLine methods.

          In both cases the UART pin configuration is the same.

 

          But if during project build I use MK64FN1M0VLQ12  processor (instead FRDM-K64F board),

          everything is working fine for the same configuration.

 

For the Project that is build:

  1. Device page: processor to be used Board, FRDM-K64F
  2. Rapid Application Page: KSDK and PE-selected
  3. Using fsl_debug_console  component

 

Every thing is working fine (strings, chars, put/get)

Labels (1)
4 Replies

521 Views
BlackNight
NXP Employee
NXP Employee

Hi Shaul,

the error message "Target processor is not selected" is a bug of the wizard if you select a non-SDK project with Processor Expert, and if you select a board (e.g. FRDM-KL25Z) instead of the microcontroller (KL25Z128M). This should have been fixed with an update, or simple create the project with the microcontroller on it selected, instead of the board name.

Erich

0 Kudos
Reply

521 Views
shauldorf
Contributor V

Hi Erich;

Thanks;

If you take a look on my “Installation details” you can see that there is “Processor Expert Patch 1”.

This patch doesn’t solve the wizard bug.

Yes I create the project with the microcontroller instead the board and it is working.

My question is  if it is equivalent to board installation?

I thought that board installation is supporting all the board hardware and processor is supporting only the controller.

0 Kudos
Reply

521 Views
BlackNight
NXP Employee
NXP Employee

Hi Shaul,

yes, indeed, I have that patch installed too, but still have that issue. I thought it had been fixed, but it looks I was wrong about that.

The difference between the 'microcontroller' or the 'board' version: in the board version the pin muxing in the PinSettings component of the project is already set up to wire up the components of the board (e.g. LED, etc). So the pins already have the correct names. Apart of that, no difference.

Erich

521 Views
shauldorf
Contributor V

Hello Erich;

Thanks, at least KL25Z I understand my problem.  Let’s hope that Freescale will solve it
sometime before the merge with NXP.

Related to second part FRDM-K64F, I think it belongs to KSDK
forum or it doesn’t matter where it has posted.

Shaul

0 Kudos
Reply