好不容易买到几片PK60N512ZVLQ10，准备做系统板出来

range

LQFP144脚，做库真不容易呀，做了将近一天。
PCB画出来了，show一下

阅读全文

range

 
不知道怎么传图片

安

上传附件，jpg格式的，然后选择插入附件。

range

和安班主学了招，谢谢，传图片。

安

如果有问题，可以在论坛留贴，我们第一时间为您解答。

range

板子做好了，发张图吧，手机照的，效果不好(主要是俺的手机不好)。
先来个正面的

 
再来个背面的

今天就焊出来试试

kgszinfo

LZ的板子测试咋样啦！

range

这两天一直调板子，第一块K60就被锁了，用usbdm,jlink,ulink都不行，都是target is secured,提示方法都是earse mass flash。CW，MDK，IAR都用了，没有解决呀，还参考了IAR的解决方法：
Technical Note 77989
Permanent Device Lock/Secure of Freescale Kinetis K60Xxxx
EW targets: ARM
EW component: General issues
Keywords: .icf file, linking
Last update: April 1, 2011
Problem
When you create a new project from scratch for a Freescale Kinetis K60Xxxx device, using Target -> Core: "Cortex-M4", or Device -> "Freescale K60Xxxx", the default linker configuration file "generic_cortex.icf" will be selected.
This linker configuration file may cause a permanent device secure (i.e. the device is made impossible to re-program), when you download your code to the board.
Solution
Use the following linker configuration file for K60Xxxx devices:
$TOOLKIT_DIR$\examples\Freescale\K60\
TWR-K60\GettingStarted\config\K60X_Flash.icf
Background
The default linker configuration file for ARM Cortex in IAR Embedded Workbench IDE places code starting at location 0. The problem is that once the code grows to encompass address 0x40C, the NVFSEC register will be programmed.
There are two bits in the NVFSEC register that can permanently disable the mass erase functionality on the chip. These bits are called Mass Erase Enable Bits (MEEN). In this same register there are also two bits that controls the Flash security (SEC). When used in conjunction, they can permanently lock the device.
Note that when selecting Options -> Target -> Device: Freescale K60Xxxx, the option Linker -> Config -> "Linker configuration file" is set to "generic_cortex.icf" by default.
To change the settings, see the attached pictures on the right hand side of this page.
Note 1:
All example projects included in the IAR K60N512 kit overrides the default linker configuration file with either "K60X_ram.icf" or "K60X_Flash.icf", and the device lock problem does not occur.
Note 2:
The example projects provided with Freescale MQX includes a vector table in "vector.c" that is extended to cover the flash config area and sets the proper values.
Note 3:
If the device has been locked with the Flash security bits only, you can unlock the device using the J-Link Commander (jlink.exe) command:
J-Link> unlock Kinetis
都不好用，第一片K60就牺牲了，明天再换片吧。用过LPC111X,STM32,LM3S,都有锁片子的情况，FSL解决起来是最没数的，因为它没有ISP方式，

range

大功告成，跑起来了。以后调程序尽量在RAM下调，安全。下一步调TF卡。

range

Kinetis容易被锁住，死锁的几率比较大，在FSL的坛子里也有很多人遇到这个问题，都快把死锁看作kinetis 的bug了，看FSL的坛子：
http://forums.freescale.com/t5/Kinetis-ARM-Cortex-M4/K60-locked/td-p/73283