Teensy Micromod downloads

[jerryk]

Hello!

I just got one of these bad boys. A micromod Teensy card, and an "All ports brought out" micromod motherboard. Put the two boards together, plugged it into a USB C. OK, the micromod port came up in my Arduino IDE. Just to see if I could download something, I set the IDE to "Teensy MicroMod" and downloaded my current project. The download was apparently successful. The downloader was happy, and the blinking lights on the board changed.

What about another download? No luck, now the "Teensy MicroMod" port is gone from the USB listing. Not entirely unexpected; the traditional Teensy card has a boot processor that takes over the SWD/JTAG pins. This doesn't have that, so I'm guessing that a boot program was loaded into the IMXRT1062 itself during manufacture. So you get to download once.

I have a "Segger EDU Mini" on order. I expect and hope that downloads can be done through that. Really, the main advantage to me of the MicroMod ecosystem is that the SWD is available. I am so sick of debug printf()'s!

 

[jmarsh]

The micromod works the same as the regular Teensys, it still has the helper chip attached to the JTAG port.

 

[jerryk]

The plot sickens... Apparently it does have the boot chip. Says so right on the schematic. So have I bricked it? When I momentarily hit the "boot" switch, the "prog" light starts to blink on the Teensy card. But there is no USB device. If I press and hold the boot switch for say 10 seconds, then the prog light comes on solid. Still no USB device.

 

[jmarsh]

Which OS are you using?
The USB VID/PID is configurable and can vary between the default blink sketch, prog mode and regular sketches. If you're using a linux-based OS the default teensy udev rules file should include all of them, but maybe that setup step was skipped...

 

[PaulStoffregen]

When I momentarily hit the "boot" switch, the "prog" light starts to blink on the Teensy card.

Same as with Teensy 4.0 and Teensy 4.1 (the red LED near their USB connector), this LED blinks in different ways to indicate different problems.

A slow steady blink means no USB communication while in bootloader mode. This is by far the most common problem with manufactured boards. It almost always means a defective or not fully plugged USB cable. If make sure none of the software is running on your PC and then you power up MicroMod and there's no blinking on the boot LED (the normal condition) and then you press the Boot button on that carrier boards, the Boot LED is supposed to turn on steady (not blinking). Even without the software, your operating system will perform some communication to detect the USB device after you release the button. If MicroMod heads absolutely zero USB communication from your PC after going into bootloader mode, it blinks the slow steady pattern to tell you it's not hearing anything from your PC.

The LED can also blink in patterns of 2 to 13 quick blinks. Most of these happen with various hardware problems. They're meant for troubleshooting DIY circuit boards. A full list is on the T4 bootloader chip page. Scroll to the end for "Troubleshooting & Diagnostic Blink Codes".

 

[jerryk]

Ubuntu Linux. I did accomplish one download. Now lsusb shows nothing when I plug it in. In /etc/udev/rules.d, I see 00-teensy.rules,
dated March 19, 2023.

I have a Teensy 4.1 also on the desk. That one works fine.

This device shows up in lsusb:
Bus 001 Device 080: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial

OK - it's some sort of USB strangeness. I unplugged it from the USB hub, and plugged it directly into the computer - and we have our USB device,
and a successful upload.

 

[jmarsh]

Bus 001 Device 080: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial

That looks weird. USB device addresses are only 7 bits wide so 128 isn't a usable value. Unless linux just "works that way" by storing addresses internally by mashing the hub address and device address together.

 

[PaulStoffregen]

I unplugged it from the USB hub, and plugged it directly into the computer - and we have our USB device

Care to name & shame the problematic USB hub?

Can it still be purchased anywhere? And is it relatively new? Often manufacturers change the internal design but keep the model number and package identical, so if it's more than a couple years old odds of buying a new one coming with the same design are slim.

 

[PaulStoffregen]

One other possibility, which might fit the circumstances of it worked at least once, is this could be a rare USB hub with actually good over-current detection. And the carrier board plus other stuff connected might have too much capacitance, with an inrush current over the limit. Maybe. Really just a blind guess. But if you want to talk of the details of what might have gone wrong, looking at what's on that carrier board and any other stuff you have connected might be useful.

 

[jerryk]

It's a Unitek Y-3198 6-port USB-3.0 hub. I bought it in November of 2019. Works fine with my cell phone.

 

[KurtE]

I just got one of these bad boys. A micromod Teensy card, and an "All ports brought out" micromod motherboard

When you are saying this, is it some new carrier board, or the old ATP board: https://www.sparkfun.com/sparkfun-micromod-atp-carrier-board.html

I have at least a couple of these and so far no problems. Although sometimes have some flaky issue, which I could resolve by unplugging the MMOD board, and then plug it back in, like maybe some contact was not making a good contact.

Note: one of the ATPs I use has a quick and dirty shield in it:

Which is setup for playing with Arducam cameras, also has the pins brought out showing Teensy pin numbers...

 

[jerryk]

It's the ATP board. Now I need to figure out what goes where. First of all, I need SPI for my display. And, I think an I2C for touch.

 

[KurtE]

Not sure if this one will help you: This is one of the pages in my Teensy 4.x excel document...

Pin

MM Pin

OV767X Shield

MM ATP

MM Func

Name

GPIO

Serial

I2C

SPI

PWM

CAN

Audio

XBAR

FlexIO

Analog

SD/CSI/LCD

00

19

UART_TX1

*

AD_B0_03

1.3

Serial1(6) RX

SPI1(3) CS0

PWM1_X1

2_RX

IO-17

01

17

UART_RX1

*

AD_B0_02

1.2

Serial1(6) TX

SPI1(3) MISO

PWM1_X0

2_TX

IO-16

02

47

TFT_RST

PWM1

*

EMC_04

4.4

PWM4_A2

2:TX_DATA

IO-06

1:4

03

32

TFT_BACKLIGHT

PWM0

*

EMC_05

4.5

PWM4_B2

2:TX_SYNC

IO-07

1:5

04

10

TFT_DC

D0

*

EMC_06

4.6

PWM2_A0

2:TX_BCLK

IO-08

1:6

05

18

TFT_CS

D1

*

EMC_08

4.8

PWM2_A1

2:RX_DATA

IO-17

1:8

06

71

CAMERA_D6

G6/BUS6

*

B0_10

2.10

PWM2_A2, QT4_1

1:TX3_RX1

2:10

LCD_DATA6

07

56

AUDIO

AUD_OUT

B1_01

2.17

Serial4(4) RX

PWM1_B3

1:TX_DATA

IO-15

2:17, 3:17

08

54

AUDIO

AUD_IN

B1_00

2.16

Serial4(4) TX

PWM1_A3

1:RX_DATA

IO-14

2:16, 3:16

09

69

CAMERA_D7

G7/BUS7

*

B0_11

2.11

PWM2_B2,QT4_2

1:TX2_RX2

2:11

LCD_DATA7

10

55

CAMERA_PCLK

SPI_CS

FNCS0

B0_00

2.0

SPI(4) CS0

QT1_0

MQS_RIGHT

2:0

LCD_CLK

11

59

SPI_MOSI

SPI_SCOPI

*

B0_02

2.2

SPI(4) MOSI

QT1_2

1_TX

2:2

LCD_HSYNC

12

61

SPI_MISO

SPI_CIPO

*

B0_01

2.1

SPI(4) MISO

QT1_1

MQS_LEFT

2:1

LCD_ENABLE

13

57

SPI_CLK

SPI_SCK

*

B0_03

2.3

SPI(4) SCK

QT2_0

1_RX

2:3

LCD_VSYNC

14/A0

34

A0

*

AD_B1_02

1.18

Serial3(2) TX

QT3_2

SPDIF_OUT

3:2

A1:7, A2:7

15/A1

38

TFT_ADA_CS_SD

A1

*

AD_B1_03

1.19

Serial3(2) RX

QT3_3

SPDIF_IN

3:3

A1:8, A2:8

16/A2

20

UART_RX2

*

AD_B1_07

1.23

Serial2(3) RX

Wire2(3) SCL

SPDIF_EXTCLK

3:7

A1:12, A2:12

USDHC2_DATA3

17/A3

22

UART_TX2

*

AD_B1_06

1.22

Serial2(3) TX

Wire2(3) SDA

SPDIF_LOCK

3:6

A1:11, A2:11

USDHC2_DATA2

18/A4

12

WIRE(CAM/AUD)

I2C_SDA

*

AD_B1_01

1.17

Serial3(2) RTS

Wire(1) SDA

QT3_1

3:1

A1:6, A2:6

19/A5

14

WIRE(CAM/AUD)

I2C_SCL

*

AD_B1_00

1.16

Serial3(2) CTS

Wire(1) SCL

QT3_0

3:0

A1:5, A2:5

20/A6

52

AUDIO

AUD_LRCLK

AD_B1_10

1.26

Serial5(8) TX

1:RX_SYNC

3:10

A1:15, A2:15

21/A7

50

AUDIO

AUD_BCLK

AD_B1_11

1.27

Serial5(8) RX

1:RX_BCLK

3:11

A1:0, A2:0

22/A8

49

<NO EDGE PIN>

BATT_VIN3

*

AD_B1_08

1.24

PWM4_A0

1_TX

3:8

A1:13, A2:13

USDHC2_CMD

23/A9

58

AUDIO

AUD_MCLK

AD_B1_09

1.25

PWM4_A1

1_RX

1:MCLK

3:9

A1:14, A2:14

USDHC2_CLK

24/A10

53

I2C_SCL1

AD_B0_12

1.12

Serial6(1) TX

Wire1(4) SCL

PWM1_X2

A1:1

25/A11

51

I2C_SDA1

AD_B0_13

1.13

Serial6(1) RX

Wire1(4) SDA

PWM1_X3

GPT1_CLK

A1:2

26/A12

67

TOUCH_CS

G8

AD_B1_14

1.30

SPI1(3) MOSI

1:TX_BCLK

3:14

A2:3

27/A13

8

TOUCH_IRQ

G11

AD_B1_15

1.31

SPI1(3) SCK

1:TX_SYNC

3:15

A2:4

28

4

<NO EDGE PIN>

3.3V_EN(no edge pin)

EMC_32

3.18

Serial7(7) RX

PWM3_B1

29

16

CAMERA_MCLK

I2C_INT#

*

EMC_31

4.31

Serial7(7) TX

SPI2(1) CS1

PWM3_A1

30

41

CAMERA_PDN

CAN_RX

*0

EMC_37

3.23

GPT1_3

3_RX

3:MCLK

IO-23

31

43

CAMERA_PEN

CAN_TX

*0

EMC_36

3.22

GPT1_2

3_TX

3:TX_DATA

IO-22

32

65

CAMERA_HSYNC

G9

B0_12

2.12

1:TX1_RX3

IO-10

2:12

LCD_DATA8

33

63

CAMERA_VSYNC

G10

EMC_07

4.7

PWM2_B0

2:MCLK

IO-09

1:7

34

66

SDIO

SDIO_DATA1

FPE1

SD_B0_03

3.15

Serial5(8) RTS

SPI2(1) MISO

PWM1_B1

IO-07

DATA1

35

64

SDIO

SDIO_DATA1

SD_B0_02

3.14

Serial5(8) CTS

SPI2(1) MOSI

PWM1_A1

IO-06

DATA0

36

60

SDIO

SDIO_SCK

*

SD_B0_01

3.13

Wire2(3) SDA

SPI2(1) CS0

PWM1_B0

IO-05

CLK

37

62

SDIO

SDIO_CMD

*

SD_B0_00

3.12

Wire2(3) SCL

SPI2(1) SCK

PWM1_A0

IO-04

CMD

38

68

SDIO

SDIO_DATA3

FPE0

SD_B0_04

3.16

Serial5(8) TX

FLEXSPI B_SSO_B

PWM1_A2

IO-08

DATA2

39

70

SDIO

SDIO_DATA2

FNCS1

SD_B0_05

3.17

Serial5(8) RX

FLEXSPI B_DQS

PWM1_B2

IO-09

DATA3

40

40

CAMERA_D0

G0/BUS0

*

B0_04

2:04

Wire3(2) SCL

QT2_1

2:4

LCD_DATA0

41

42

CAMERA_D1

G1/BUS1

*

B0_05

2:05

Wire3(2) SDA

QT2_2

2:5

LCD_DATA1

42

44

CAMERA_D2

G2/BUS2

*

B0_06

2:06

QT3_0

2:6

LCD_DATA2

43

46

CAMERA_D3

G3/BUS3

*

B0_07

2:07

QT3_1

2:7

LCD_DATA3

44

48

CAMERA_D4

G4/BUS4

*

B0_08

2:08

QT3_2

2:8

LCD_DATA4

45

73

CAMERA_D5

G5/BUS5

*

B0_09

2:09

QT4_0

2:9

LCD_DATA5

HUSB D-

37

USBHOST_D-

*0

HUSB D+

35

USBHOST_D+

*0

USB D-

5

USB_D-

USB D+

3

USB_D+