Wiki Coming - Please link worthy posts

[defragster]

{ reminder:: link instructive things you see or do on the forum here so when the WiKi gets rolling stuff can be pulled out and covered }

Teensy 3.2 Interrupts to Blink LED's at Different Rates :: systick_isr() timer interrupt
https://forum.pjrc.com/threads/36778...l=1#post114681

Link to the Newlib Library Documentation: Teensy uses:: Newlib is a C library intended for use on embedded systems.
https://sourceware.org/newlib/

Teensy-Internal-Reference-Voltage
Teensy-Internal-Reference-Voltage-Question?

[Frank B]

DAC:
https://forum.pjrc.com/threads/26036...ll=1#post49821

[Frank B]

resistors:

https://forum.pjrc.com/threads/38028...l=1#post118598

and

https://forum.pjrc.com/threads/38028...l=1#post118607

[Frank B]

Eagle-Libraries

https://forum.pjrc.com/threads/38096...l=1#post118731

[defragster]

Arduino Language Reference:: Primary Arduino as well as Standard C reference info - be alert for better 32 bit ARM Teensy math or other::
https://www.arduino.cc/en/Reference/HomePage

Arduino Libraries Summary - some may have ported or improved Teensy code::
Reference/Libraries

[Frank B]

Noise from SGTL-5000:

https://forum.pjrc.com/threads/27215...ll=1#post78831

[defragster]

Teensy 3.6 Analog Reference Card showing pin source:
K66-Beta-Test

Generate an assembler listing when compiling Teensy
How-can-I-generate-an-assembler-listing-when-compiling-Teensy

Tutorial on State machine usage - don't use delay() - watch the clock! Part 1 of 3
adafruit.com multi-tasking-the-arduino-part-1/all-together-now

Teensy Specific LED/DIGITAL FLASHER class sample with elapsedMicros and no delay()
Help-with-Coding-to-get-LED-s-Working-as-I-would-Like

Using a local DEF file to alter compile time settings [FrankB ]::
HOWTO-Store-Projects-settings-(like-F_CPU-USB-Keyboard-layout)

ARM MEMORY access cycles: for RAM / FLASH / EEPROM / PORTS
Teensy-3-6-8pin-16pin-and-32pin-simultaneous-writes

[tni]

Input capture / pulse measurements using FTM timers and DMA:
https://github.com/tni/teensy-sample...apture_dma.ino

[lownote]

From my post dealing with an issue getting interrupts to work:

Initial pin states are different between UNO and Teensy, where the Teensy is more or less configured by default as Inactive which saves power.
So try adding something like: pinMode(pin, INPUT_PULLUP); or just INPUT if you have external stuff doing pullup or pull down.

[gruvin]

I promise the Wiki is coming.

Don't ya just hate it when life gets in the way of the fun stuff? :-P (I'm brand new around here. No offense intended.)

[MichaelMeissner]

If this post gets answered, the answers should go in the wiki:

• https://forum.pjrc.com/threads/42408...026#post135026

[Frank B]

Teensy 3.6 startup problems with some power supplys - or - Teensy resets due to EMI on its reset line.

- Add a capacitor ~10nF..~22nF between RESET an GND.

[Frank B]

"Also to note that on my Windows 7 machine, it's recognized as "Teensy" while on my Windows 10 machine it's only recognized as "COM5".

At least that part is normal.

With Windows 10, Microsoft finally began shipping a system INF to cause their own USBSER.SYS driver to load for serial devices.

Before Windows 10, everyone using standard serial (technically usb communication class abstract control model - one of many standard officially published by the usb organization) had to provide their own INF. Usually this is called a "driver", even though it's merely an INF that tells Windows XP, Vista, 7, 8 to load their own USBSER.SYS driver. The INF PJRC provides has "Teensy" in its description, so when you see the device appear in the Windows Device Manager, it says Teensy.

On Windows 10, the name which appears is the generic name Microsoft put into their own INF. So it's perfectly normal to see this difference between Windows 10 and older versions of Windows.

https://forum.pjrc.com/threads/42576...l=1#post136209

[GremlinWrangler]

Off site series of blog posts on getting an emulated xbox controller (xinput) up and running as a new USB type
http://www.zlittell.com/2015/07/msf-...-controller-8/
Useful as is and as a case study in making a new USB type for Teensy

[MichaelMeissner]

From https://forum.pjrc.com/threads/42625...-on-Tennsy-3-2:

You'll probably need to edit Firmata's Boards.h to disallow use of pins 0 and 1. If anything in Firmata tries to access them as GPIO, the pins are no longer controlled by Serial1.

[defragster]

Disassemble your binary
arm-none-eabi-objdump.exe -d --demangle ...

To get assembly code:
arm-none-eabi-objdump -d --demangle -C YOUR_COMPILED_SKETCH.elf > assembly.txt

arm-none-eabi-objdump is included with the toolchain, e.g. arduino/hardware/tools/arm/bin/arm-none-eabi-objdump.exe.

[WMXZ]

Out of curiosity, I checked the 'WIKI coming soon' saga
It started nearly 2 years ago and over 2 years ago defragster noted 'PJRC and Teensy(s) needs a Wiki' https://forum.pjrc.com/threads/28793...ll=1#post74446

Now, where is it?

Any update from PJRC?

[Robin]

It's on the to do list, unfortunately it keeps getting pushed lower down in priority as things like Teensy 3.5, Teensy 3.6, and USB Host development get pushed up in priority. We have been working on some IT infrastructure changes that will help facilitate the creation of the Wiki. I commit to any timeline for this, but I can assure you that it has not been forgotten about.

[defragster]

... I've seen notes that predate mine. What I've seen and noted about the WiKi is - they 'write themselves' - like this thread - and the forum - they just need an outlet.

Definition of wiki
:* a website that allows visitors to make changes, contributions, or corrections

[Spix]

Ability to debug is key to develop quality applications. I can't see how this is surpassed by other priority items.

[Spix]

because of the lack of proper debug support I jumped to

http://www.nxp.com/products/microcon...s:FRDM-KEAZ128

This comes ( if I understand it correctly) with full debug support inside a proper development env (Elclipse)


This is not to rub it in or something: this is the dilemma you have to face when choosing a certain development board/platform

[Frank B]

Polyfuse:
https://forum.pjrc.com/threads/28551...ll=1#post72465

[PaulStoffregen]

Here's some info about connecting more than 32 Teensy boards to a PC, shared by email from someone who wishes to remain anonymous.

Apparently the Linux /dev/ttyACM driver has a limit of "only" 32 simultaneous devices. Apple's driver on Sierra has a limit of only 16. So far, no info about whether Windows has a similar limit.

The info for Linux:

So I got 64 teensies to mount on opensuse 13.2
in /usr/src/linux/drivers/usb/class/cdc-acm.h
there is a
#define ACM_TTY_MINORS 32

set that to 64 or 128. I did 256

then borrowing heavily from
https://forums.opensuse.org/showthre...-kernel-module

cd /usr/src/linux
make clean
make oldconfig
cp /usr/src/linux-obj/HW/NAME/Module.symvers /usr/src/linux/
make scripts
make prepare
cd /usr/src/linux/drivers/usb/class
make -C /usr/src/linux SUBDIRS=$PWD modules
cp /usr/src/linux/drivers/usb/class/cdc-acm.ko /lib/modules/VERS/kernel/drivers/usb/class/
shutdown -r now

Edit: Windows 10 was tested and found to support only 16 simultaneous devices.

[MichaelMeissner]

It has been said before, but just to link this into the page for eventual inclusion into a wiki. The Teensy 3.5 and 3.6's bootloader has a mode to wipe out the memory. You have to press and keep pressed, the program button for 13-17 seconds:

The program wipe feature is not 20+ seconds. It's *exactly* 15 seconds. The bootloader actually looks for a press that lasts between 13 to 17 seconds, so you're allowed +/- 2 seconds. If you hold for 20 seconds or more, you'll miss that window.

Whether or not this program wipe will help is anyone's guess. Seems very likely the hardware may just be damaged. But to even try the program wipe, you really need to look at a stopwatch or clock with seconds when pressing the button, so you can hit that 13 to 17 second window.

This is from:

• https://forum.pjrc.com/threads/43642...626#post141626

[defragster]

Powering Teensy with external LiPo Charger:
Help-with-Connecting-Lipo-Battery-and-Charger-to-Teensy-3-2