KBOOT V1.2

[a8Chcx]

Hi,

I am testing KBOOT V1.2 on my FREEDOM K64F platform. I am using KDS 3.0.0 and KSDK 1.2.0 environment.

1) I open the existing bootloader project for K64F without copying option. Then, I generated the *.elf file and works fine.

2) I am using P&E multilink USB to write *.elf to my target board and is running properly.

3) I am using PTB16&17(UART0) as my communication channel.

4) I am running blhost on PC, and using the command "blhost -p COM1,19200". There is no any reply from bootloader on K64F.

5) I am using fixed baud(19200) instead of auto baud detection, and connect to Hyper Terminal, I can't see the data on Hyper terminal.

6) Then, I try to use blhost, and no reply as well...

7) Another question. There are the following calls in bootloader. Could you tell me what the function will be called because I can't find the entrance?

s_scuart_byte_receive_callback(kFramingPacketStartByte);

s_scuart_byte_receive_callback(kFramingPacketType_Ping);

Could anyone tell me where I did wrong, and how to use blhost to talk to bootloader on K64F?

Thanks,

Christie

[mjbcswitzerland]

Christie

Check your board's operation by using a pre-built Kboot software from µTasker Kinetis FRDM-K64F support

This uses the same UART pins as you specify but has the Baud rate set to 57600.

I would expect the Kboot V1.2 package to include working K64 code but if you do have difficulties you can also get a Kboot compatible solution at the link which includes also USB-MSD and Ethernet loading (which the Kboot package itself can't do). It will also work on all K, KE, KEA, KV and KL parts and with most IDEs so doesn't need porting/developing when not working with a part that the Kboot V1.2 package doesn't include, or if using a different IDE to it.

To solve problems or learn the operation it can be completely simulated in real-time (to check Kboot protocol or Flash saving, or to see the clocks and pins that are actually being configured) and so it recommended for professional developments where time needs to be invested in the application rather than in configuring and solving Kboot complications or deficiencies in its processor support. It works with all application types (bare-metal, KSDK, MQX, etc.) and so can be used with any project source (or used with the uTasker project for fastest solutions).

Regards

Mark

Kinetis: µTasker Kinetis support

K64: µTasker Kinetis FRDM-K64F support  / µTasker Kinetis TWR-K64F120M support  / µTasker Kinetis TWR-K65F180M support

Boot loader: http://www.utasker.com/docs/uTasker/uTaskerSerialLoader.PDF

For the complete "out-of-the-box" Kinetis experience and faster time to market

[a8Chcx]

Hi,

The LED demo application is built on KDS 3.0.0 as well?

How to load it by using bootloader and start running on K64F?

Thanks,

Christie

[mjbcswitzerland]

Hi

The Kboot user's manual explains how to load applications.

Regards

Mark

Kinetis: µTasker Kinetis support

K64: µTasker Kinetis FRDM-K64F support  / µTasker Kinetis TWR-K64F120M support  / µTasker Kinetis TWR-K65F180M support

Boot loader: http://www.utasker.com/docs/uTasker/uTaskerSerialLoader.PDF

For the complete "out-of-the-box" Kinetis experience and faster time to market

[a8Chcx]

Sorry. Some mistake on earlier one.

When I use the fixed baud rate(19200), I can see the data on my hyper Terminal when I send some data. So, I confirmed that my UART0 hardware is working fine...

[Carlos_Mendoza · Accepted solution]

Hi Christie,

Please make sure that the COM port number used in the command is the correct one, also notice that the baud rate is automatically determined by the bootloader when processing the initial ping. Thus, subsequent blhost invocations must specify the same baud rate as was used for the initial invocation unless the bootloader is reset. If the baud rate is not specified using the -p COMx,<baudrate> option, the UART baud rate is set to 57600.

I have done some tests using the same bootloader project and it is working correctly:

My FRDM-K64F has the COM port 40 assigned:

In the command prompt I type the command blhost -p COM40,19200 get-property 1:

Hope it helps!

Best Regards,

Carlos Mendoza

Technical Support Engineer

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

[a8Chcx]

Hi Carlos,

It works on my side as well. I have to input the full command, not only "-p COM1".

Now, my problem is how to build led demo application in KDS 3.0.0 to generate *.bin file.

I tried the one that comes with BOOT V1.2, but I think it is based on IAR, not KDS 3.0.0.

Could you tell me how to use KDS 3.0.0 to generate the same led demo application to download to bootloader by using blhost?

Thanks,

Christie

[Carlos_Mendoza]

Hi Christie,

Yes, the led demo project is based on IAR but you can find the generated binaries of the led demo in the following path:

<install_dir>\apps\led_demo\binaries

Hope it helps!

Best Regards,

Carlos Mendoza

Technical Support Engineer

[a8Chcx]

Hi Karlos,

The led demo file(*.bin) is working fine.

I am trying to generate the *.bin file under KDS 3.0.0 by changing the memory section.

I can see the code is starting at 0xA000, but it didn't work.

I am using KDS 3.0.0 and KSDK 1.2.0 and use PE to generate my project...

Could you send me some sample project to tell me how to set memory section for KDS 3.0.0 in order to use this bootloader?

Thanks,

Christie

[gionny]

Hi Christie,

have you found a led demo project developed under KDS 3.0.0 working with KBOOT?

Thanks

Gionatha

[Jorge_Gonzalez]

Hello Ferriari Gionatha:

You may find useful the next document I just posted:

Adapting KDS project for KBOOT flash resident bootloader

Regards!

Jorge Gonzalez

[gionny]

Hi Jorge.

I have tried bur it doesn't work.

I've created a simple MQX-PE-KDS 3.0 project (FRDM-K64F) but I can't download it by bootloader.

Have you got a K64 example for KDS at address 0xA000?

Thanks very much

Gionatha

[Jorge_Gonzalez]

Hi Ferrari:

It's strange, I loaded your project's binary without any modifications using KBOOT and it works as expected. Can you extend on the issue:

What do you mean with "I can't download it"?

What interface are you using? I used USB HID.

Are you trying with the Kinetis Updater GUI or with blhost command line tool?

Regards!

Jorge Gonzalez