Teensy 4.0 First Beta Test

**PaulStoffregen** · 12-27-2018, 01:22 AM

We're going to begin beta testing for Teensy 4.0.

At this time, PJRC would like to offer free beta test boards to the following people:

Bill Greiman, brtaylor, christoph, defragster, dgarcia42, Donziboy2, duff, el_supremo, embedded-creations, Epyon, Frank B, GremlinWrangler, Headroom, JBeale, Jean-Marc, Koromix, kriegsman, KurtE, linuxgeek, luni, manitou, MichaelMeissner, MickMad, mjs513, mortonkopf, mxxx, Nantonos, nlecaude, oddson, Pedvide, Pensive, pictographer, nox711, sumotoy, TelephoneBill, Theremingenieur, tni, tonton81, WMXZ, whollender, Wozzy, xxxajk

We will be expanding this list in the coming weeks, with names of many more forum contributors and people who have written Teensy specific libraries. We're only offering the beta test hardware to the people on this list.

For the first round of betas, we have 31 boards with the 1052 chip. These are meant for beta testing only, because the final Teensy 4.0 will use the similar 1062 chip (more RAM, faster I/O, CAN FD). After beta, software support for 1052 will be dropped. These 1052 betas are meant to give you the earliest access. Please understand their software support will be only temporary.

To jump in now with the 1052 beta, please email Robin directly (actual email, not forum PM) with the magic words "I have free time to beta test" and your shipping address. There is no charge for these betas. PJRC will pay for shipping. If you're outside the USA and the carrier charges international tariff/vat/fees when the package arrives, you'll need to cover that cost. We can't pre-pay it from here.

If you're busy with work or life, waiting is perfectly fine. The longer you wait, the closer your board will be to the final release. If you don't have any time to do testing, that's fine too. We will still send you a free Teensy 4.0 as a special "thank you". If you don't get a beta board, just email Robin after release and we'll send you a free Teensy 4.0 from the first production batch.

During this beta, I'd like to ask everyone to follow a few simple rules.

No photos!
Keep all conversations & info on this forum thread
Don't mess with the OTP fuses

The first 2 allow us to share pretty much all technical info early, but still make an official release. Of course, after we announce Teensy 4.0 on the website and/or Kickstarter, photos will then be ok. Like with prior betas, this forum thread will get painfully long. Please bear with it. Having it all in 1 place before release helps us, and having all the info as text on a forum thread make it accessible for people who want technical details, but (probably) not "news" of a product release.

Wrong fuse settings can permanently brick your board. Final Teensy 4.0 will have critical fuse regions locked. For now, we're leaving all the betas unlocked for maximum flexibility. Overclocking is generally ok, but please use your best judgement if you edit any #define with the comment "Danger Will Robinson", or if you write directly to DCDC_REG3. NXP's datasheet rates the "absolute maximum" at 1.3 volts.

One final note - We're starting this beta very "early" with a ton of stuff not yet completed or fully working on the software side. Things will get better as we go. Messages #2 - #6 are placeholders for updates. I'd like to ask all our "plus" users to please edit these as needed.

**PaulStoffregen** · 12-27-2018, 01:22 AM

**PaulStoffregen** · 12-27-2018, 01:23 AM

Pinouts:

Code:

---    ----       ----  ------    ---  ---     ---      ---   ----       ----    ------  ------
Pin    Name       GPIO  Serial    I2C  SPI     PWM      CAN   Audio      XBAR    FlexIO  Analog
---    ----       ----  ------    ---  ---     ---      ---   ----       ----    ------  ------
 0     AD_B0_03   1.3   UART6_RX       3:CS0   PWM1_X1  2_RX             IO-17
 1     AD_B0_02   1.2   UART6_TX       3:MISO  PWM1_X0  2_TX             IO-16
 2     EMC_04     4.4                          PWM4_A2        2:TX_DATA  IO-06   1:4
 3     EMC_05     4.5                          PWM4_B2        2:TX_SYNC  IO-07   1:5
 4     EMC_06     4.6                          PWM2_A0        2:TX_BCLK  IO-08   1:6
 5     EMC_07     4.7                          PWM2_B0        2:MCLK     IO-09   1:7
 6     B1_01      2.17  UART4_RX               PWM1_B3        1:TX_DATA  IO-15   2:17,3:17
 7     B1_00      2.16  UART4_TX               PWM1_A3        1:RX_DATA  IO-14   2:16,3:16
 8     B0_10      2.10                         PWM2_A2,QT4_1  1:TX3_RX1          2:10
 9     B0_11      2.11                         PWM2_B2,QT4_2  1:TX2_RX2          2:11
10     B0_00      2.0                  4:CS0   QT1_0          MQS_RIGHT          2:0     
11     B0_02      2.2                  4:MOSI  QT1_2    1_TX                     2:2
12     B0_01      2.1                  4:MISO  QT1_1          MQS_LEFT           2:1     
13     B0_03      2.3                  4:SCK   QT2_0    1_RX                     2:3
---    ----       ----  ------    ---  ---     ---      ---   ----       ----    ------  ------
Pin    Name       GPIO  Serial    I2C  SPI     PWM      CAN   Audio      XBAR    FlexIO  Analog
---    ----       ----  ------    ---  ---     ---      ---   ----       ----    ------  ------
14/A0  AD_B1_02   1.18  UART2_TX               QT3_2          SPDIF_OUT          3:2     A1:7,A2:7
15/A1  AD_B1_03   1.19  UART2_RX               QT3_3          SPDIF_IN           3:3     A1:8,A2:8
16/A2  AD_B1_07   1.23  UART3_RX  3_SCL                       SPDIF_EXTCLK       3:7     A1:12,A2:12
17/A3  AD_B1_06   1.22  UART3_TX  3_SDA                       SPDIF_LOCK         3:6     A1:11,A2:11
18/A4  AD_B1_01   1.17   2_cts    1_SDA        QT3_1                             3:1     A1:6,A2:6
19/A5  AD_B1_00   1.16            1_SCL        QT3_0                             3:0     A1:5,A2:5
20/A6  AD_B1_10   1.26  UART8_TX                              1:RX_SYNC          3:10    A1:15,A2:15
21/A7  AD_B1_11   1.27  UART8_RX                              1:RX_BCLK          3:11    A1:0,A2:0
22/A8  AD_B1_08   1.24                         PWM4_A0  1_TX                     3:8     A1:13,A2:13
23/A9  AD_B1_09   1.25                         PWM4_A1  1_RX  1:MCLK             3:9     A1:14,A2:14
---    ----       ----  ------    ---  ---     ---      ---   ----       ----    ------  ------
Pin    Name       GPIO  Serial    I2C  SPI     PWM      CAN   Audio      XBAR    FlexIO  Analog
---    ----       ----  ------    ---  ---     ---      ---   ----       ----    ------  ------
24/A10 AD_B0_12   1.12  UART1_TX  4_SCL        PWM1_X2                                   A1:1  
25/A11 AD_B0_13   1.13  UART1_RX  4_SDA        PWM1_X3,GPT1_CLK                          A1:2
26/A12 AD_B1_14   1.30                 3:MOSI                 1:TX_BCLK          3:14    A2:3  
27/A13 AD_B1_15   1.31                 3:SCK                  1:TX_SYNC          3:15    A2:4  
28     EMC_32     3.18  UART7_RX               PWM3_B1
29     EMC_31     4.31  UART7_TX       1:cs1   PWM3_A1
30     EMC_24     4.24  UART5_RX               PWM1_B0
31     EMC_23     4.23  UART5_TX               PWM1_A0
32     B0_12      2.12                                        1:TX1_RX3  IO-10   2:12
33     EMC_08     4.8                          PWM2_A1        2:RX_DATA  IO-17   1:8
---    ----       ----  ------    ---  ---     ---      ---   ----       ----    ------  ------
Pin    Name       GPIO  Serial    I2C  SPI     PWM      CAN   Audio      XBAR    FlexIO  Analog
---    ----       ----  ------    ---  ---     ---      ---   ----       ----    ------  ------

Bottom side (smt) and right side (through hole) pads:

Code:

          (bottom side view - ref note the VBAT/3V3/GND/PGM end pins are in same order as on T_3.x - With ON/OFF as the far end pin)

   ON/OFF - o    26 - o   o - 25     
  Program - o    24 - o   o - 27     
      GND - o    32 - o   o - 28
     3.3V - o    30 - o   o - 29
     VBAT - o    31 - o   o - 33

UARTn Serialx mapping pins [RX/TX]

Code:

        UART6 Serial1 [0/1]   UART4 Serial2 [6/7]
        UART2 Serial3 [15/14] UART3 Serial4 [16/17]
        UART8 Serial5 [21/20] UART1 Serial6 [25/24] 
        UART7 Serial7 [28/29] UART5 Serial8 [30/31]

FlexIO - FLEXIO3 only present in RT1062 - So all pins marked as 3:nn in pin table will only have flexIO capabilities on the later boards!

Placeholder here for Paul to Note expected pin changes on move to 1062::
… TBD ...

Reference:

**PaulStoffregen** · 12-27-2018, 01:23 AM

status / news / stuff confirmed working

Solved!	Issue	Reference	Comment
	AccelStepper
ADA LIB UPDATE	Adafruit_GFX	post #852	Teensyduino library version needs to be updated to latest from Adafruit
ADA LIB UPDATE	Adafruit_ILI9341	post #852	Teensyduino library version needs to be updated to latest from Adafruit
works	Adafruit_NeoPixel		tested with Simple example and 8 LED stick
	Adafruit_nRF8001
	Adafruit_RA8875
	Adafruit_SSD1306	post #478	working with fixed avr_emulation.h , post #757
	Adafruit_ST7735
	Adafruit_STMPE610
	Adafruit_VS1053
works	ADC
broken	AltSoftSerial	post	t4 porting needed
	Artnet
	Audio
works	Bounce/Bounce2
works	CapacitiveSensor	post #852
	CryptoAccel
	DmxSimple
	DogLcd
	DS1307RTC
works	EasyTransfer	post #852	see post #621
partial	EasyTransferI2C	post #852	needs I2C slave address, see post #621
	EEPROM
Works	Encoder
	Entropy
works	Ethernet		post #958
Works	FastCRC
	FastLED		needs platform optimization
	FlexCAN
	FlexiTimer2
	FreqCount		GPT1 pin 25 post #982 POC
works	FreqMeasure	post #464
	FreqMeasureMulti
	FrequencyTimer2
	i2c_t3
	ILI9341_t3
works	IRremote	post #441	LED def error
	Keypad
	ks0108
Works	LedControl
	LedDisplay
	LiquidCrystal
	LiquidCrystalFast
	Metro
	MFRC522
	MIDI
	MsTimer2
	NXPMotionSense		Needs EEPROM.h to compile
	OctoWS2811
works	OneWire		tested on DS18B20
	openGLCD
	OSC
	Ping
	PS2Keyboard
	PulsePosition
Works	PWMServo
	RA8875
	RadioHead
works w/update	ResponsiveAnalogRead	post #677	Teensyduino version needs to be updated
Works	SD	Post	https://github.com/PaulStoffregen/SD/pull/14
	SdFat
works	SerialFlash
Works	Servo
	ShiftPWM
	Snooze
	SoftPWM
broken	SoftwareSerial	Post	t4 porting needed
partial	SPI
	SPIFlash
	ssd1351
	ST7565
	ST7735_t3
	Talkie	post #677	Teensyduino version needs to be updated
	TeensyThreads
	TFT_ILI9163C
	Time
	TimeAlarms
Works	TimerOne
	TimerThree
works	TinyGPS
	Tlc5940
	TouchScreen
works	UBLOX, Bolderflight
works	UBLOX, Chris O
	USBHost_t36
	UTFT
	VirtualWire
	WS2812Serial
	X10
	XBee
partial	Wire		missing slave mode & setClock
	XPT2046_Touchscreen

works	digitalRead
works	digitalReadFast
works	digitalWrite
works	digitalWriteFast
works	pinMode
works	analogRead
works	analogReadResolution		implemented, confirmation needed
works	analogReadAveraging		implemented, confirmation needed
	analogReference		placeholder only, reference always 3.3V
works	analogWrite		pin 0 and 1 inverted?
works	analogWriteFrequency
works	analogWriteResolition
works	tone
works	noTone		implemented, confirmation needed
	pulseIn
	shiftIn
	shiftOut
works	delay
works	delayMicroseconds
works	delayNanoseconds
works	millis
works	micros		with 1us resolution
works	elaspedMillis
works	elapsedMicros		with 1us resolution
partial	IntervalTimer		missing priority()
works	EventResponder
works	MillisTimer
works	yield
works	attachInterrupt
	detatchInterrupt
works	random		is sequence same? yes
	randomSeed		no effect on T3.2 or T4?
	String
	AVR gpio register emulation
	AVR spi register emulation
works	ultoa, ltoa
works	dtostrf
	avr eeprom functions
works	arm_math.h
works	Server	#958	implemented, confirmation needed
works	Client	#958	implemented, confirmation needed
broken	IPAddress	needs IPAddress.cpp #941	implemented, confirmation needed
Works	DMAChannel
works	malloc / free
	new / delete		implemented, confirmation needed

works	PROGMEM
works	PSTR()
works	F()
works	FASTRUN
works	Serial1-8
	Serial transmitterEnable
	Serial RTS / CTS flow control
	serialEvent
missing	fault handler flushes USB
missing	fault handler serial1-8
missing	fault handler auto-reboot

partial	USB Serial
	USB Keyboard
	USB Touch Screen
	USB Mouse
	USB Joystick
	USB MIDI
	USB MIDIx4
	USB MIDIx16
	MIDIUSB compat
	USB Audio
	USB MTP Disk
	USB RawHID
	USB Flight Sim Controls
	non-US USB keyboards

	...
Solved!	Issue	Reference	Comment

**PaulStoffregen** · 12-27-2018, 01:23 AM

placeholder post: benchmarks & performance tests

some coremarkish numbers post #194 and post #235 MHz vs power
some floating point benchmarks and DSP post #204
pin tests post #264
SPI data rates post #826

This is beta hardware and software.

**PaulStoffregen** · 12-27-2018, 01:24 AM

Solved?	Issue	Who's working on it	Comment
	DSP vector math lib, #356		fix in beta7, testing needed
	DMA problems, #412
solved	DMAChannel triggerAtHardwareEvent, #466		wrong usage
	SPI example crashes if infinite loop after result, #125		can't reproduce
	board detection issue, #535
	SAI2 clock issue, #519
	Bounce lib with pin 1, #1402, #1436,
	random() wrong output, #566
	teensy_ports issues with 3+ boards, #1330, #1398,
	write back cache & DMA problems, #485, #482
	closing serial monitor stalls program, #321
	IPAddress, #941
	padconfig register defines #906
	IntervalTimers called twice, low performance, #830, #880 #884, #1164, #1180, #1182, #1183,
	digitalWriteFast performance issue, #1181,
	T4 blocks sketch execution when Serial.print is used and no SerMon #182		Sketch post #368
	malloc & free		in beta2, testing needed
	arm errata 838869, #1191,
	CAN startup/init issue, #405, #402
	PROGMEM & FASTRUN working for functions in both C & C++
	IntervalTimer priority() not implemented, #261
	TRNG config, #1074, #642,
	Tempsense register fix, #411		fix in beta7
	power off program requires 13 sec recovery, #370
	15 recovery restores flash with broken RawHID, #1336,
	audio programs sometimes block auto-reboot, #1394, #1433,
	Arduino IDE unresponsive at times, #1376, #1377, #1379, #1385, #1417, #1432,
	PC unable to boot with BIOS post "partial" while Teensy4 connected, #409
	slow USB enumeration with Amazon Basics hub, #1426, #866, ,
	USB doesn't work at low clocks, #913, #916, #1070
	pin 0,1 not working for quadrature encoder, #1056,
	DMA & cache trouble, #1061-1062,
	NIC-301 settings? #1065,
	Arduino's memory usage summary has inaccurate info, #1087,		Fix: https://forum.pjrc.com/threads/54711...l=1#post194902
	F() and PSTR() in both C & C++
	PROGMEM issue with ILI9341_t4, #1158,
	CPU speed set may not be switching IPG safely, but how?
	cache clean & invalidate needed		in beta6, will know after new USB & Audio
	15 sec restore: Windows doesn't like the USB descriptors of restored image	Sample User Sketch?
	bootloader is slow, mem_write_block() mostly
	bootloader to use low power modes
	bootloader RTC time set
	USB Serial receive, not yet implemented
	USB Serial efficient transmit
	Arduino serial monitor doesn't freeze when autoscroll turned off, #1154,
	Arduino serial monitor can't copy remaining text to clipboard after device disconnects & window is disabled, #1154,
	HardwareSerial to use interrupts	KurtE	WIP - Testing needed
	HardwareSerial RTS/CTS
	HardwareSerial transmitterEnable	KurtE	WIP
	USB MIDI
example	RTC rtc_get, rtc_set, rtc_compensate? teensy3_clock_class Teensy3Clock	manitou	RTC ticking and VBAT test, post #656
	DMAChannel		edma works, tested with only one channel so far (frank b) - it needs attention with cache!!
Tested	arm_math.h	manitou	see post #85 and post #204
	USB keyboard
	USB mouse
	USB joystick
	USB flightsim
	USB MTP
	USB MIDI name override
	USB Touchscreen
	USB Audio
Done	USB RawHID - actually working
	AudioStream
	new & delete		in beta2, testing needed
	C++ stdlib functions?
	SPIFIFO - is anything really using this?
Pls test	pulseIn	Frank B	depends on exact micros() ** micros() exact now
Pls test	shiftIn	Frank B
Pls test	shiftOut	Frank B
Done	random	manitou	is sequence same for same seed vals?
	analogWrite gracefully handles 0, 255, 256, negative & other illegal values		testing needed (most cases look ok)
	Wire - recovery from hung bus
	Wire - slave mode
minimal code works	SPI		minimal code in beta3
	SPISettings not used, clock fixed at 12.5 MHz, #428		some support in beta7 (thanks Manitou)
	EEPROM --- how to use ipcommand for access to flexspi?
	AVR EEPROM functions
	AVR GPIO register emulation
	AVR SPI register emulation
	AVR TWBR register emulation
	Adafruit ILI3941 doesn't compile, AVR emulation needed, #537
	Sparkfun Teensyview not compiling, #545
	Ethernet		needs IPAddress.cpp
	Bounce2		working? #1003,
	SoftwareSerial
	SD
	Audio
	OctoWS2811
	ILI9341_t3
	WS2812Serial
	USBHost_t36
	AltSoftSerial		not ported, #999,
	CapacitiveSensor		in beta6, testing needed
	DmxSimple
	RadioHead		needs SPI.end, #1009, #1032, #1040, #1174, #1175,
	FreqCount
	FreqMeasureMulti
	PulsePosition
	MIDI
	ShiftPWM
	Snooze
	Talkie, not working, expects DAC, #561 #548
	TeensyThreads ? not working, #496
	TimerThree
	Tlc5940
	fault after coremark using 50000, msg #117	Prevent Fault Edit Post #651
	Shutdown when temperature is "critical" (?) (added by Frank B)
	Add events for temperature is "hot" + "cold" again (?) (added by Frank B)
	Tools > Optimize "Fastest + pure-code" fails, maybe gcc bug?
	analog.c functions to set resolution, average, vref		fix in beta7
	VGA library
Solved?	Issue	Who's working on it	Comment

**manitou** · 12-27-2018, 01:37 AM

I'll email Robin ... let the games begin.

cross-link to pre-beta test NXP 1052 EVKB eval board

**defragster** · 12-27-2018, 06:49 AM

The other thread leading into this with 10 pages of posts … Teensy-4-0-(hypothetical)-pin-assignments

Paul : if you could put links to YOUR versions of the Ref Manuals it would make sure feedback/details come from the 'same page' - though of course some of your early code notes may be from prior RM version. And of course that will also be fun when it comes to 1052 .vs. 1062. Not sure if there is a placeholder post appropriate for that? Maybe post #2 with latest Software

Post #181 Pins :: first round of betas will have the pins in msg #181

Originally Posted by PaulStoffregen

I can tell you the first round of betas will have the pins in msg #181, including pins 24-33 brought to pads on the bottom side.

The pinout definitely will change, at least so we have access to the CAN FD pins on the RT1062 chip. The changes are expected to be fairly minor, between 2 to 5 pins altered. If you have any concerned or input about which pins, *NOW* is the time to read the many messages in this thread and start pouring over the info in NXP's RT1050 & RT1060 reference manuals.

...

**Frank B** · 12-27-2018, 07:15 AM

Audio

filters	done
effects	done
output_i2s	done
output_i2s2	done
i2s slave
i2s2 slave
input_i2s	done
input_i2s2	done
output_tdm	done
output_tdm2	done
input_tdm
input_tdm2
input_i2s_quad
input_i2s2_quad
output S/PDIF SAI1 emulated	done
output S/PDIF SAI2 emulated	done
input S/PDIF (hardware)
Output S/PDIF (hardware)
output MQS	done
output pt8211	done
output pt8211_2	done
...

TODO: Temporary removed DMAMEM from in/outputs. Good fix needed.
Attention, TDM and MQS need different PLL settings than I2s - so using the three mixed together is not possible, currently.

**manitou** · 12-27-2018, 10:59 AM

The distinguishing macro symbol is __IMXRT1052__ Yes? Should we worry about 1062 symbol? or a KINETISK equivalent?

**defragster** · 12-27-2018, 11:05 AM

Originally Posted by manitou

The distinguishing macro symbol is __IMXRT1052__ Yes? Should we worry about 1062 symbol? or a KINETISK equivalent?

That is the only one I see > #if defined(__IMXRT1052__)
Not used much yet [3 matches across 2 files] - would be nice if that went to #if defined(__IMXRT1062__) sooner rather than later/never given those were the chips ordered for release.

<edit>:Frank follows with a good point - 1052 has to allow those items to be found/dropped/changed as pins move etc.

**Frank B** · 12-27-2018, 11:32 AM

Would be handy if both were defined - even if 1062 is wrong now. But it makes things easier during development.

**PaulStoffregen** · 12-27-2018, 04:53 PM

Robin has 12 of the 31 betas ready to ship. I believe so far 7 are claimed, so up to 5 more can ship today if anyone else (on the list) wants to jump in now. I still want to do more tests on the inductors this weekend, which is the reason I'm still holding many of the boards. My hope it to make most or all of the remaining 19 boards available early next week. We're also going to add more names to the list.

If all or most of the 31 are claimed next week, we might schedule one more soldering session on Jan 4th, which would likely yield another 10-12 boards. These will be the last of the 1052 boards. These 31 or ~40 will be the only boards for the next several weeks, until we get the 1062 chips and I can get around to making a board rev for the CAN FD pins.

When you get your board, you should see a number written on the bottom. They're numbered 2 to 33. For anyone counting, 9 didn't work for reasons unknown, and 1 is the beta I've been using, and so far the only board that's been abused with over-voltage overclocking. The boards also have a serial number in the mac address field in the fuse memory, where the number is 1000XX where XX is the number written on your board.

The bootloader makes the first 1536K of the flash available for uploading. The last 512K is "reserved", never programmed nor erased by the bootloader. The top 4K has a copy of a small program which gets copied to the beginning of the flash during the full erase after you've held the button for 15 seconds. Some portion of the top memory will become used by the EEPROM emulation. I'm still undecided what will be done with the rest of that 512K. Maybe a small filesystem like ESP uses? Or maybe we'll expand the bootloader's usage to allow larger programs? So many things left to do...

Tonight and tomorrow I'm going to put in a couple long sessions to fix up more of the core library and convert C code I wrote weeks ago to SPI & Wire libs and then package up installers. If your board arrives and I still haven't put installers on msg #2, please ping me and I'll quickly wrap things up whereever they're at and make a set of installers.

**PaulStoffregen** · 12-27-2018, 05:03 PM

The bootloader now has a red LED to show you status. There is a known timing bug which causes it to flicker. I'll fix that in a couple weeks, after first working on much-needed stuff in the libraries, so please try to ignore the flickering. It's a known bug.

Here are the LED status signals:

Dim blinking = bootloader is waiting for USB enumeration (eg, external power without a USB cable, or a charge-only cable)
Dim steady = bootloader is running, USB communication is good, waiting for data/commands from Teensy Loader
Bright = writing to flash memory
Brief dim flash after holding button for ~13 seconds = visual cue to release your finger *now* if you want to initiate full erase. (and of course if you release in time, the LED will be bright for many seconds while doing the full erase)

**KurtE** · 12-27-2018, 05:20 PM

Hi Paul,

I may start a little slow with some other distractions going on...

Will probably start on some on some of the components and libraries I have done stuff on, like serial, SPI, Wire, and maybe play with ili9341 code. But wondering approach for libraries like ili9341_t3, where a lot of the speed gains was due to the spi fifo queue, which Idont believe these chips support. Are you thinking we should integrate in DMA support? Or just make it work?

**manitou** · 12-27-2018, 05:25 PM

Re: stuff that needs work
a few functions in analog.c need to be implemented. should I just add that to post #6 ?

**manitou** · 12-27-2018, 05:30 PM

Originally Posted by KurtE

Hi Paul,

I may start a little slow with some other distractions going on...

Will probably start on some on some of the components and libraries I have done stuff on, like serial, SPI, Wire, and maybe play with ili9341 code. But wondering approach for libraries like ili9341_t3, where a lot of the speed gains was due to the spi fifo queue, which Idont believe these chips support. Are you thinking we should integrate in DMA support? Or just make it work?

my EVKB SDK SPI experiments used a SPI FIFO and messed with frame size to get data rates very close to SPI CLK.
https://forum.pjrc.com/threads/54265...l=1#post192387

**manitou** · 12-27-2018, 05:47 PM

Re: post #6 bug analogWrite doesn't work on pin 1 (maybe others?)

problem in core_pins.h
#define CORE_PIN0_CONFIG IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B0_02
#define CORE_PIN1_CONFIG IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B0_03

FIX:
#define CORE_PIN0_CONFIG IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B0_03
#define CORE_PIN1_CONFIG IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B0_02

untested

**Frank B** · 12-27-2018, 06:54 PM

I formatted the list in Post #6 as a table.
At the last beta test there were some confusions, because several people worked on the same topic ( - for example make a lib compatible - ) without knowing about each other (happened to me sevreal times...). It would be great if you put your name there as soon as you start working on a topic, so that we don't do the same things.

**Theremingenieur** · 12-27-2018, 07:12 PM

I wrote to Robin today that I was ready to give my list position to another person since I won't be able to do much testing/developing until earliest mid February. But I will naturally read and follow here how it goes.

**Frank B** · 12-27-2018, 07:17 PM

Originally Posted by PaulStoffregen

I'm still undecided what will be done with the rest of that 512K. Maybe a small filesystem like ESP uses? Or maybe we'll expand the bootloader's usage to allow larger programs?

If it was more than 512k, I'd say a filesystem would be good. With 512k only, I'd say use 256k for a giant eeprom, and add the remaining 256k to the programs..
Or..512k for eeprom.. this way it can be used for a filesystem - by the user.

**Robin** · 12-27-2018, 08:04 PM

Originally Posted by PaulStoffregen

At this time, PJRC would like to offer free beta test boards to the following people:

defragster, dgarcia42, duff, el_supremo, embedded-creations, Frank B, GremlinWrangler, JBeale, Koromix, KurtE, luni, manitou, MichaelMeissner, mjs513, oddson, Pedvide, Pensive, pictographer, nox711, sumotoy, Theremingenieur, tni, tonton81, WMXZ, Wozzy, xxxajk

To jump in now with the 1052 beta, please email Robin directly (actual email, not forum PM) with the magic words "I have free time to beta test" and your shipping address. There is no charge for these betas. PJRC will pay for shipping. If you're outside the USA and the carrier charges international tariff/vat/fees when the package arrives, you'll need to cover that cost. We can't pre-pay it from here.

If you are outside the US can you also include your phone number when you give me your address. We need to include it for customs.

**mjs513** · 12-27-2018, 08:40 PM

Shutdown when temperature is "critical" (?) (added by Frank B)
Add events for temperature is "hot" + "cold" again (?) (added by Frank B)

Yeah - I already started looking at what's needed to get this implemented. To get the throttle back functions implemented need to look at throttling back the system clock. According to the manual 10.4.2.2 Thermal-aware power management - you can "implement temperature aware DVFS... as well temperature aware frequency scaling for other system components....". The example in the SDK just scales back the AHB_clk frequency until the lower temperature is reached then boosts it back up. With DVFS (still have to figure out how that works) you can change the modes to WAIT State or SUSPEND state. Looking through the sdk example now. Need a few things added to imrtx.h file to get it working though see post https://forum.pjrc.com/threads/54265...l=1#post193773.

Really not sure about the octop registers - only needs one so maybe we can hardcode that one.

**Frank B** · 12-27-2018, 08:42 PM

I would'nt do throttling. For "critical", just a reset (that resets the chip, and disables pins) - on startup check the reset-reason and HALT. For "hot", just the event and leave the reaction to the user/program.. any other action could be unexpected and lead to questions or unwanted behaviour (if the T4 does something important or dangerous..this knows the user only)

Edit: with "eventresponder"
Maybe we can add some examplecode how to throttle for the case that the event "fires"... ?

**mjs513** · 12-27-2018, 09:11 PM

Was actually looking at implementing both ways eventually. The SDK code is rather convoluted if you get into it and was planning on taking this incrementally especially since I never played around with this at this level

. Plan was going to get the throttling done first then do the DVFS piece. Was thinking you could also use the temp monitor to get some temperature profiles just as a test. Any help would be appreciated.

EDIT: Actually, have a good sdk example could use for ideas and guidance - the power-mode-switcher application that @manitou mentioned. Relatively straight forward. Getting good at going through the SDK.

Thread: Teensy 4.0 First Beta Test

Thread Tools

Search Thread

Display

Teensy 4.0 First Beta Test

Stuff in need of testing or fixing

Posting Permissions