I really wish Paul would have provided a normal 2×5 SWD debug header or footprint (ideally on the top side): that would make his boards even more useful. And because the board does not allow the standard SWD debug header, I have to create a custom cable. Because the DE (Debug Enable) signal does not work, it requires removal of the KL02Z microprocessor from the board. To use normal SWD debugging tools with the Teensy 3.5 and 3.6 it requires a hardware change, as for the Teensy 3.1 (see ).
#HOW TO WRITE C CODE TO TEENSY 3.6 HOW TO#
But I really don’t understand why he makes it so hard to use his boards for debugging? Maybe others are used to printf() style debugging as a hobby, but to me this is not the adequate way how to develop for an ARM Cortex-M. The Teensy is a great board, and Paul Stoffregen does a really great job. This pulls reset to about 1.85V which seems to be enough to disable the KL02Z. Other users report that it is possible to add a 10k Pull-Up on the reset line of the KL02Z. As anyway the KL02Z on the board is not of any use for me, the decision was to remove it from the board. Pulling the reset line LOW to keep the KL02Z in reset does not work, as the reset line is shared between the KL02Z and the MK66F/MK64F.
WARNING: This modifies the Teensy board, and without a doubt you loose any warranty doing that board change! Modifying the Teensy 3.5/3.6 for SWD Debugging So what now? Wait again maybe a year or forever? Luckily, I have found a way, but it is the ‘hard’ way. Why a year late? Work on Teensy 3.5 & 3.6 (released October 2016) and the USB host library for 3.6 (first release March 2017) pushed that and many other project goals well into 2017. It turned out that pulling down the DE signal is still not supported, from from 04-24-2017: Just disconnect or drive the pin high to return the Teensy to its normal functionality.”īelow is the schematics of the Teensy 3.5/3.6 from : The idea is you pull it low to tell the MKL02 chip to tri-state the debug pins, so you can control them with whatever debug adaptor you use. You might also notice the “DE” pin, for Debug Enable. There’s not a lot of room on the bottom side, so had to abbreviate. Look for the pads labeled “DD” and “DC”, for Debug Data and Debug Clock. “You’ll be happy to hear those test point are on the bottom side. Drive that pin high or just disconnect (it has a weak pullup) to return to Teensy’s normal mode.” There’s a pin you pull low to tell the bootloader chip to tri-state those signals. See the comments and bottom-side photo on the Kickstarter page. “For these new Teensy boards, I added a provision to use the debug signals. Now it seemed that Paul finally has added an easier way to to SWD debugging (several asked for that in the forums/community). But that wiring was not really easy, so we better used the tinyK20 as boards. For the Teensy 3.1 I have found a way to do this (see “ Hacking the Teensy V3.1 for SWD Debugging“) and we used that for several Teensy boards. Instead, I want to use normal debugging tools like a J-Link. The Teensy boards are great (thanks Paul!), but only if using Arduino libraries and the Arduino IDE which never has been an option for me. Maybe Paul had the same idea, and Hackaday produced an article ( ) back in August 2016 about two new boards: the Teensy 3.5 and 3.6. The tinyK20 has the option of an micro SD card on the bottom side.
0 kommentar(er)
