做了K60 LQFP144的小板，带SD卡

雪藏的企鹅

发出去做了，再等2天就来了，先发个PCB 秀一下。
复位键，4个LED灯，1个电源指示灯，MicroSD卡，RTC后备电池，模拟电源数字电源全部隔离，10脚JTAG调试口，全部引脚引出。

雪藏的企鹅

有源晶振，过流保护，板载3.3V系统

zjh3123629

不错 挺小的

雪藏的企鹅

今天收到板子了，秀一下，手机照的，效果不好。
先来个正面的


再来个背面的的


焊出来试试，再向大家汇报

春暖花开

大神，有kineties相关的给力资料吗，如详细教程之类的

雪藏的企鹅

这两天一直调板子，第一块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方式.

雪藏的企鹅

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

雪藏的企鹅

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

xjtuzhanghongji

如果只是用来做智能车，还是建议不要引出所有引脚，这样能做的更小走线更漂亮

雪藏的企鹅

做智能车，用100脚都浪费。做一次小系统板，考虑不到将来能用到什么，哪些用不着，所以把所有引脚引出是为了以后用时选择的多些，