kboot import

[kennethtait]

Setup is KDS on linux 64 bit,

trying to set up a kboot project.

If I set up a new workspace and import with copy of the desired target, it sets it up but does not copy all the source files , only I2C driver??? and complains about paths being wrong, but does make an elf file..

If I switch to the bootloader folder as the workspace and select a project, it trashes stuff.

There is no way to directly open the workspace under \kds folder.

so WHAT is the EXACT procedure for setting up a bootloader project that does not modify the original sources...

Reference manual only shows an IAR setup..which I don't care about...

Ken

[Alice_Yang]

Hello Kenneth,

Which version of KBOOT do you used ?

I recommend you use the latest version KBOOT v2.0 ,  KDSv3.2 .

And when i used it on  Wind7, the bootloader project on be import well .'

While when you use it , if the image outside of the memory size , there is two method to fix,you can refer to this DOC: Using KBOOT v2 on KDS in Debug Mode 

Hope it helps

Alice

[kennethtait]

Thanks Alice,

I am using the 2.0 version. the problems here are many...

Overall, the bootloader itself is pretty good, addresses most everything

needed, except in my case...

The Docs only address an IAR port, which is a serious omission since we

are being told Kinetis is the future...

First of all, there are no header,linker or startup files for the part

I'm using, MK22FN1m0, so using the 512k which should be close.

Second, if you import the bootloader, what you get are virtual links to

all the files. It compiles, you can change minor things and get a build,

but if you try and generate any new files to link in, such as needing to

run a simple display, this fails. You can't make any new files, since

essentially there is NO main folder. Importing with copy fails too.

There should be no reason for this.... Having to use the the actual

disti makes it very difficult to archive projects correctly....

trying to copy over all the relevant pieces into a new project should be

the cleanest way to go, but it won't build since the file links are broken.

All pathways are blocked here...Why can't this this just be a simple set

of files that customers can modify. If we screw it up it's our

issue..not yours.

I haven't used Eclipse in some time and I'm now remembering what a

crappy IDE it really is :smileysad:

Ken

[Alice_Yang]

Hi Kenneth,

Oh , you want porting the bootlaoder to MK22fn1m0 chip .

If you think it is hard to port the KBOOT v2.0 , i  recommend you another simple bootlaoder.

Kinetis Bootloader to Update Multiple Devices in a Network for Cortex-M4

This is simple of KBOOT, it is for FRDM-K22(the chip is k22fn512), it include KDS v3.0 version , keil, IAR.

And  thay all of independent files , not have the virtual file .

Also there is the Reference manual to introduce it , the process is the same as KBOOT.

I think after you check , you can porting it to K22FN1M0 chip , only need change some flash address and size place.

And i know clearly about this bootlaoder , so when you porting , if there is some problem you can contact me without

any hesitate.

Hope it helps

Alice

[kennethtait]

Thank you Alice!

I was not aware of this and I will definitely look it over. We only need

a simple bootloader for this project that does not need all the KBOOT

features

Ken

[Alice_Yang]

Hello Ken,

Yes, it is simple than KBOOT, it only use the UART to update .

Hope it helps

Alice