Hello there. :smileyhappy:
I need some wisdom about minor(?) problem.
My company's new project is based on MK22FN51VLH12 chip. (Kinetis thing as you know,)
IDE is Keil uVision V5 for some reasons.
Dev tool is Segger J-link lite. (a bundle thing I guess,)
Of course, the board is custom made.
When I build a project, it's fine.
When I flash the target, there is the problem.
I assume flash writing fine because chip running as normal. (GPIO, UART, etc. works fine.)
But when chip verification, it prints out like this in build log
I already heard there is some region in Flash which cannot access.
But in my opinion, if I choose the right flash algorithm, verification also should be fine, isn't it?
Did I miss something? Are there any more options should I adjust?
I add some info.
Thx for your opinion!
Have nice day :smileyhappy:
Hi Lee,
This is a strange problem. It seems only KEIL has this problem. I guess this may caused by some wrong project config. I think you can get around it. There are many examples build in keil in SDK package, for example SDK_2.2_TWR-K22F120M\boards\twrk22f120m\demo_apps\hello_world\mdk. If this example works fine in your system, you can migrate your source code to the project.
Regards,
Jing
Hmm... Problem same. :smileysad:
I think project setting is not a problem.
In SDK, there are no keil project setting with J-link. they are all pemicro.
So I'm not sure that problem show up when I change debugger setting.
Now I just do it without flash verify.
PS. When I tried flash writing in J-flash lite with HEX file, it doesn't works. That strange. :smileysad: