- NXP Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- Wireless Connectivity
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- Vigiles
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
-
- Home
- :
- General Purpose Microcontrollers
- :
- Kinetis Microcontrollers
- :
- Re: Programming a Bare Chip
Programming a Bare Chip
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I want to start my design from a bare chip (I can provide a specific product number but I want to learn more about the general philosophy behind this) which is actually a Kinetis ARM-Based-Microcontroller. Do I need to analyze the related development board component-by-component or is there a list of minimum peripheral components I need for programming & operation? I am pretty much of a beginner on this topic and I am totally confused while browsing through the Datasheet & Reference Manual. I guess there should be a "clear" tutorial for obtaining a "serial" or "J-Tag" connection between a USB interface and the pins of the MCU unit.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Freescale used to publish schematics in their datasheets showing exactly that - the minimum recommended connections for in-circuit programming. It doesn't look like they do that anymore, and in fact if you don't happen to be using exactly one of the parts in the relatively few development boards, there aren't many example schematics to work with.
Looking at one of my own designs, I see that the only connections I have for programming are VCC, ground, reset, SWDIO, and SWDCLK. SWD is serial wire debug and basically provides the same functions as JTAG with fewer pins.
To talk to the SWD port, you need an interface - which might be USB but not always. My P&E Cyclone ACP (~$600) is out of commission right now because a driver update broke it and I'm using a P&E Multilink Universal (~$200) in the meantime, but there are cheaper (OpenSDA) options and all of the recent development boards I've used have had one of those built in. You can frequently use one of those boards to program your own chips.
For the physical connection, a 10-pin header is common for SWD and allows for easy hookup to any of those devices above, but for production boards I use a TC-2030-NL connector, which is basically zero cost on the board and takes up very little space.
As for minimum connections to run, you're going to need power and ground, with 0.1 uF decoupling caps near each power pin. If your part has a USB voltage regulator, pay attention to its requirements. USB probably won't work without that powered, and its output pin needs a largish cap for stability.
If you're not running from an internal clock source, you'll also need a crystal or external oscillator. I think that should be enough to get any of the Kinetis MCUs going.
Hope that helps,
Scott
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Freescale used to publish schematics in their datasheets showing exactly that - the minimum recommended connections for in-circuit programming. It doesn't look like they do that anymore, and in fact if you don't happen to be using exactly one of the parts in the relatively few development boards, there aren't many example schematics to work with.
Looking at one of my own designs, I see that the only connections I have for programming are VCC, ground, reset, SWDIO, and SWDCLK. SWD is serial wire debug and basically provides the same functions as JTAG with fewer pins.
To talk to the SWD port, you need an interface - which might be USB but not always. My P&E Cyclone ACP (~$600) is out of commission right now because a driver update broke it and I'm using a P&E Multilink Universal (~$200) in the meantime, but there are cheaper (OpenSDA) options and all of the recent development boards I've used have had one of those built in. You can frequently use one of those boards to program your own chips.
For the physical connection, a 10-pin header is common for SWD and allows for easy hookup to any of those devices above, but for production boards I use a TC-2030-NL connector, which is basically zero cost on the board and takes up very little space.
As for minimum connections to run, you're going to need power and ground, with 0.1 uF decoupling caps near each power pin. If your part has a USB voltage regulator, pay attention to its requirements. USB probably won't work without that powered, and its output pin needs a largish cap for stability.
If you're not running from an internal clock source, you'll also need a crystal or external oscillator. I think that should be enough to get any of the Kinetis MCUs going.
Hope that helps,
Scott
