Kinetis 2 bugs

[kennethtait]

Using Linux 64 bit with Latest KDS

2 annoying bugs here wasting my time:

1.     Go to help->search

     type in CPU_ to search for all the valid cpu defines

     hit GO,

     pulls up 77 items.

     Click on first item, KDS BLOWS UP and exits with no warning.

2.     Compile a project under debug, loads and runs fine with PE multilink.

          Compile release version of project, no errors

          Try to flash project, multilink will not connect to target, sees mulitlink it, but won't connect.

          I am ASSUMING it's because target is MK22FN1m0 and code is linked to MK22FN512.

          So if this is the issue why is there no error message telling me it actually DID find it but it'snot what was           expected.      Why is there no forced override?

Ken

[MarekTrmac]

Hi Ken,

the problem is in Java virtual machine. May be, update to newer JRE version could help.

Marek

[michalzan]

Hi Ken,

I am really sorry for your inconvenience. I reproduced the problem on clean Ubuntu 14.04. It is caused by segmentation fault in jvm. Are you able to upgrade to Ubuntu 16.04? Thank you.

Regards,

Michal

[kennethtait]

Michal,

I'm glad you see it too. No I can't upgrade at this time. 16.04 won't

run or fit on the machine it's on and I don't want to spend the time

messing with it. This is a total productivity time waster.

so what's causing the seg fault? Why is jvm broken here?

Again I must stress that any dev IDE built on java is garbage and not

maintainable long term. Once again eclipse has stuck it to me so I am

not going to continue to feed this monster.

thanks

Ken

[michalzan]

Hi Ken,

about the CPU_ search - what version and what derivate of linux are you using? I was not able to reproduce this on Ubuntu 16.04 64bit with oracle java 1.8

Michal

[kennethtait]

Well of course you can't reproduce it. KDS for linux CLEARLY states it

was tested on 14.04 LTS, so if this is true it should work on this out

of the box with no mods. Don't know what version of java it comes with

it..shouldn't really matter. It shouldn't use ANY java, just the native

desktop environment,

which in this case is python for extras.

Your version probably has some different or updated libs not in 14.04.

So I'm, supposed to keep upgrading my workstation every time NXP puts

out a new release. I don't think so...

What I see happening here in the industry is TOO much focus on glitz and

marketing and TOO LITTLE attention to the actual tools used to do work.

This is a dev environment, It's expected it should compile,link load

programs, nothing more. By rights it should not ever have a net

connection or rely on the net for anything since in many company

environments security dictates no possible outside access to code source.

This is not an iphone and I for one am getting sick of every dev

environment looking like one.

Whoever is doing the planning is failing miserably, no cohesive overall

strategy.

Do you want to sell chips or play games? choose 1.

just my 2 cents

Ken

[MarekTrmac]

Hi Ken,

about debugging release configuration - can you attach your project or describe, how the project was created?

Regards, Marek

[kennethtait]

Hi Marek,

2 projects actually.

1. a modified bootloader based on boot code 2.0

2. custom project created in CW and moved to Kinetis.

Project 2 compiles and runs fine in debugger. If I make a release

version, it compiles but PE multilink FX won't flash it..seems to

complain about wrong cpu, which can't be right since it debugs fine. The

only real difference between these CPUs is the flash size, all things

being equal.

Project 1 compiles, won't run or flash. This is probably due to the fact

I modified it for the MK22FN1M0 part which is NOT in the 2.0 release and

something the PE is picking up doesn't match the CPU signature, this is

a guess??? The bootloader defines a CPU_xxx type in the project. I

changed this to what I thought was correct, but not sure if it is the

right word/spelling..Can't find a reference to what is legal here..this

should be so simple.

As I mention in last post I tried to find this in help but help crashed

the IDE. A little more investigation seems to indicate it doesn't like

some java crap on my machine...The Linux version clearly has some

install or setup bugs not being addressed, so I'm hoping I can get this

to work adequately enough to do the project.

Kinetis did upgrade the PE firmware when first attached, so I would

think everything is up to date here...

Thanks for the interest

Ken