RECESSIM - User contributions [en]

Catalia Health Mabu 2AK8Y-M0208

2024-12-10T02:50:37Z

-.-6eau:

* [https://web.archive.org/web/20170911170124/https://www.cataliahealth.com/ 2017 Website Snapshot]

* [https://web.archive.org/web/20240329003431/https://cataliahealth.com/ 2024 Website Snapshot]

* [https://device.report/catalia-health Device Report]

* [https://fccid.io/2AK8Y-M0208 FCC IO]
** [https://fccid.io/2AK8Y-M0208/Internal-Photos/Internal-Photos-4818696.pdf Internal Photos]
** [https://fccid.io/2AK8Y-M0208/External-Photos/External-Photos-4818687.pdf External Photos]

* RockChip RK3228
* 2.4 GHz Wifi/Bluetooth Antenna
* LTE Main & Diversity Antenna
* Speaker with Amplifier
* Camera & Sensor, light/range?
* I2C, UART, OTG
* 602030P 7.4v 300mAh (2 cell lipo)
* 30-pin (2x15) 0.1" Header
* Screen active area ~9x16cm ~7 inch diagonal
* Overall frame ~20x13cm

=== Press ===

* https://news.mit.edu/2019/catalia-health-mabu-robot-1011
* https://www.fastcompany.com/90297836/this-little-robot-helps-care-for-people-with-chronic-conditions
* https://robotsguide.com/robots/mabu/

User:-.-6eau

2024-12-10T02:31:47Z

-.-6eau: /* Projects */

hellorld!

contact via signal: _6eau.10

=== Projects ===
*[[Ohmni Telepresence Robot]]
*[[Catalia Health Mabu 2AK8Y-M0208]]
*[[Roti_making_robot_rotimatic]]
*[[Rechargeable_Disposable_Vape_Teardown]]
*[[Whirlybird]]
*[[Instant_Omni_Pro_18_Toaster_Oven_and_Air_Fryer]]
*[[Vaisala RS41 Radiosonde Weather Balloon Sensor Payload]]

==== Previous (externally hosted) ====
*https://labitat.dk/wiki/SOUNDBOKS
*https://labitat.dk/wiki/Flasher
*https://labitat.dk/wiki/Shipmate_RS_4000_CC_Radio_Navigation_System

Ohmni Telepresence Robot

2024-12-10T02:30:07Z

-.-6eau: more bots

https://ohmnilabs.com/products/ohmni-telepresence-robot/

Telepresence Robot Reimagined: Enhanced Remote Communication with Ohmni

A fully mobile telepresence robot that combines high-def video with crystal-clear audio for seamless and engaging remote collaboration. With obstacle avoidance and easy access from anywhere, Ohmni is setting a new standard for communication.

''The Ohmni Telepresence robot is discontinued as of August 2024 and has been replaced with OhmniCare, our enhanced telepresence robot designed specifically for healthcare use cases. Support, warranties, and cloud service for existing Ohmni Telepresence robots will continue unchanged.''

Catalia Health Mabu 2AK8Y-M0208

2024-12-10T02:26:24Z

-.-6eau: space babies from Berkeley incoming

* [https://web.archive.org/web/20170911170124/https://www.cataliahealth.com/ 2017 Website Snapshot]

* [https://web.archive.org/web/20240329003431/https://cataliahealth.com/ 2024 Website Snapshot]

* [https://device.report/catalia-health Device Report]

* [https://fccid.io/2AK8Y-M0208 FCC IO]
** [https://fccid.io/2AK8Y-M0208/Internal-Photos/Internal-Photos-4818696.pdf Internal Photos]
** [https://fccid.io/2AK8Y-M0208/External-Photos/External-Photos-4818687.pdf External Photos]

=== Press ===

* https://news.mit.edu/2019/catalia-health-mabu-robot-1011
* https://www.fastcompany.com/90297836/this-little-robot-helps-care-for-people-with-chronic-conditions
* https://robotsguide.com/robots/mabu/

Videri

2024-12-02T20:48:34Z

-.-6eau: /* WiFi / BlueTooth */

<big>'''Introducing Videri Digital Canvas.'''</big>

''"The world’s thinnest, lightest and smartest Digital Canvas."''

== VQ ==

=== Images ===

<gallery>
File:Videri VQ Montreal Button BD SW1 Pinhole Assembly PCB Reverse.jpg
File:Videri VQ eDP Flat Flex to CHRONTEL PCB.jpg
File:Videri VQ BlueTooth Enabled Graphic.jpg
File:Videri VQ DPC460 DPC-450T PCB Reverse.jpg
File:Videri VQ DIP Switches.jpg
File:Videri VQ TI TPS54427 Buck Regulator.jpg
File:Videri VQ Mount Dog Reverse Engineer Target.jpg
File:Videri VQ Green Red LED.jpg
File:Videri VQ WiFi BlueTooth Module J10 Header.jpg
File:Videri VQ WNC NFC A01 Flat Flex Antenna Assembly Reverse.jpg
File:Videri VQ WNC NFC A01 Flat Flex Antenna Assembly.jpg
File:Videri VQ 2.4 GHz Antenna Black Wire.jpg
File:Videri VQ Edge Pin Hole Push Button Access.jpg
File:Videri VQ Edge Pin Hole Push Button Assembly Back PCB.jpg
File:Videri VQ 2.4 GHz Antenna White Wire.jpg
File:Videri VQ Flat Flex Connector Module.jpg
File:Videri VQ DPC-450T PCB CPU eMMC SD WiFi BlueTooth Connectors.jpg
File:Videri VQ Qualcomm PM8994 Power Management IC.jpg
File:Videri VQ Samsung 64GB eMMC KLMCG2KCTA B041.jpg
File:Videri VQ Micron KRLC 7K644 D9TGF POP-TOP CPU DPC-450T.jpg
File:Videri VQ Heatsink Phillips Screw.jpg
File:Videri VQ PPD-QCNFA324 WiFi BlueTooth Module.jpg
File:Videri VQ SW2 SW3 DPC-450T.jpg
File:Videri VQ CHRONTEL CH7515A TF.jpg
File:Videri VQ 2QVBB PCB CHRONTEL eDP LVDSS.jpg
File:Videri VQ Power Connection.jpg
File:Videri VQ S'mores Field Trip.jpg
</gallery>

=== Specifications ===

https://videri.com/wp-content/uploads/2023/06/Videri-Best-Practices-Guide_v2.0.pdf

*DISPLAY
**Active Display Area 475.8mm x 475.8mm [18.73in x 18.73in]
**Resolution 1920 x 1920
**Brightness 450 NITS
**PPI 78
**Surface Treatment 20% Haze
**Color Gamut 92% NTSC
*TECHNOLOGY
**Processor DPC450 - 64GB onboard storage
**WiFi 802.11 g/n/ac @ 2.4/5GHz
**BlueTooth BT 4.0
**NFC Yes (@13.56MHz)
**Mech Outline 500 x 500 x 14mm
*OS Android 6
*POWER
**Input 100-240 VAC
**Consumption (typ) 52W
*ENVIRONMENT
**Operating Temp. 0C to 40C
**Operating Humidity 0-90% RH (non-condensing)
*CERTIFICATION & COMPLIANCE
**Safety UL, CSA, CB
*EMI/EMC FCC Class B, IC, CE
*SIZING
**Bezel Width 11.1mm (0.44in) 34 pixels
**Thickness 14.0mm (0.55in))
**Weight 4.4kg (9.8lbs)

=== Power ===

24 volt, 3.75 amp (90 watt). Custom cable with extension to barrel connector and mutli-country power brick.

=== WiFi / BlueTooth ===

QCNFA324

https://fccid.io/PPD-QCNFA324

Videri

2024-12-02T20:48:24Z

-.-6eau: /* Images */

Videri

2024-12-02T20:47:35Z

-.-6eau: /* VQ */ Images

<big>'''Introducing Videri Digital Canvas.'''</big>

''"The world’s thinnest, lightest and smartest Digital Canvas."''

== VQ ==

=== Images ===

<gallery>
File:Videri VQ Montreal Button BD SW1 Pinhole Assembly PCB Reverse.jpg
File:Videri VQ eDP Flat Flex to CHRONTEL PCB.jpg
File:Videri VQ BlueTooth Enabled Graphic.jpg
File:Videri VQ DPC460 DPC-450T PCB Reverse.jpg
File:Videri VQ DIP Switches.jpg
File:Videri VQ TI TPS54427 Buck Regulator.jpg
File:Videri VQ Mount Dog Reverse Engineer Target.jpg
File:Videri VQ Green Red LED.jpg
File:Videri VQ WiFi BlueTooth Module J10 Header.jpg
File:Videri VQ WiFi BlueTooth Module J10 Header.jpg
File:Videri VQ WNC NFC A01 Flat Flex Antenna Assembly Reverse.jpg
File:Videri VQ WNC NFC A01 Flat Flex Antenna Assembly.jpg
File:Videri VQ 2.4 GHz Antenna Black Wire.jpg
File:Videri VQ Edge Pin Hole Push Button Access.jpg
File:Videri VQ Edge Pin Hole Push Button Assembly Back PCB.jpg
File:Videri VQ 2.4 GHz Antenna White Wire.jpg
File:Videri VQ Flat Flex Connector Module.jpg
File:Videri VQ DPC-450T PCB CPU eMMC SD WiFi BlueTooth Connectors.jpg
File:Videri VQ Qualcomm PM8994 Power Management IC.jpg
File:Videri VQ Samsung 64GB eMMC KLMCG2KCTA B041.jpg
File:Videri VQ Micron KRLC 7K644 D9TGF POP-TOP CPU DPC-450T.jpg
File:Videri VQ Heatsink Phillips Screw.jpg
File:Videri VQ PPD-QCNFA324 WiFi BlueTooth Module.jpg (https://fccid.io/PPD-QCNFA324)
File:Videri VQ SW2 SW3 DPC-450T.jpg
File:Videri VQ CHRONTEL CH7515A TF.jpg
File:Videri VQ 2QVBB PCB CHRONTEL eDP LVDSS.jpg
File:Videri VQ Power Connection.jpg
File:Videri VQ S'mores Field Trip.jpg
</gallery>

=== Specifications ===

https://videri.com/wp-content/uploads/2023/06/Videri-Best-Practices-Guide_v2.0.pdf

*DISPLAY
**Active Display Area 475.8mm x 475.8mm [18.73in x 18.73in]
**Resolution 1920 x 1920
**Brightness 450 NITS
**PPI 78
**Surface Treatment 20% Haze
**Color Gamut 92% NTSC
*TECHNOLOGY
**Processor DPC450 - 64GB onboard storage
**WiFi 802.11 g/n/ac @ 2.4/5GHz
**BlueTooth BT 4.0
**NFC Yes (@13.56MHz)
**Mech Outline 500 x 500 x 14mm
*OS Android 6
*POWER
**Input 100-240 VAC
**Consumption (typ) 52W
*ENVIRONMENT
**Operating Temp. 0C to 40C
**Operating Humidity 0-90% RH (non-condensing)
*CERTIFICATION & COMPLIANCE
**Safety UL, CSA, CB
*EMI/EMC FCC Class B, IC, CE
*SIZING
**Bezel Width 11.1mm (0.44in) 34 pixels
**Thickness 14.0mm (0.55in))
**Weight 4.4kg (9.8lbs)

=== Power ===

24 volt, 3.75 amp (90 watt). Custom cable with extension to barrel connector and mutli-country power brick.

=== WiFi / BlueTooth ===

QCNFA324

File:Videri VQ Montreal Button BD SW1 Pinhole Assembly PCB Reverse.jpg

2024-12-02T20:42:27Z

-.-6eau:

File:Videri VQ eDP Flat Flex to CHRONTEL PCB.jpg

2024-12-02T20:41:31Z

-.-6eau:

File:Videri VQ BlueTooth Enabled Graphic.jpg

2024-12-02T20:40:00Z

-.-6eau:

File:Videri VQ DPC460 DPC-450T PCB Reverse.jpg

2024-12-02T20:39:01Z

-.-6eau:

File:Videri VQ DIP Switches.jpg

2024-12-02T20:38:05Z

-.-6eau:

File:Videri VQ TI TPS54427 Buck Regulator.jpg

2024-12-02T20:37:35Z

-.-6eau:

File:Videri VQ Mount Dog Reverse Engineer Target.jpg

2024-12-02T20:34:26Z

-.-6eau:

File:Videri VQ Green Red LED.jpg

2024-12-02T20:33:29Z

-.-6eau:

File:Videri VQ WiFi BlueTooth Module J10 Header.jpg

2024-12-02T20:32:47Z

-.-6eau: -.-6eau uploaded a new version of File:Videri VQ WiFi BlueTooth Module J10 Header.jpg

File:Videri VQ WiFi BlueTooth Module J10 Header.jpg

2024-12-02T20:31:58Z

-.-6eau:

File:Videri VQ WNC NFC A01 Flat Flex Antenna Assembly Reverse.jpg

2024-12-02T20:31:20Z

-.-6eau:

File:Videri VQ WNC NFC A01 Flat Flex Antenna Assembly.jpg

2024-12-02T20:28:21Z

-.-6eau:

File:Videri VQ 2.4 GHz Antenna Black Wire.jpg

2024-12-02T20:27:21Z

-.-6eau:

File:Videri VQ Edge Pin Hole Push Button Access.jpg

2024-12-02T20:26:47Z

-.-6eau:

File:Videri VQ Edge Pin Hole Push Button Assembly Back PCB.jpg

2024-12-02T20:26:01Z

-.-6eau:

File:Videri VQ 2.4 GHz Antenna White Wire.jpg

2024-12-02T20:25:22Z

-.-6eau:

File:Videri VQ Flat Flex Connector Module.jpg

2024-12-02T20:24:35Z

-.-6eau:

File:Videri VQ DPC-450T PCB CPU eMMC SD WiFi BlueTooth Connectors.jpg

2024-12-02T20:23:48Z

-.-6eau:

File:Videri VQ Qualcomm PM8994 Power Management IC.jpg

2024-12-02T20:22:27Z

-.-6eau:

File:Videri VQ Samsung 64GB eMMC KLMCG2KCTA B041.jpg

2024-12-02T20:21:23Z

-.-6eau:

File:Videri VQ Micron KRLC 7K644 D9TGF POP-TOP CPU DPC-450T.jpg

2024-12-02T20:20:21Z

-.-6eau:

File:Videri VQ Heatsink Phillips Screw.jpg

2024-12-02T20:18:47Z

-.-6eau:

File:Videri VQ PPD-QCNFA324 WiFi BlueTooth Module.jpg

2024-12-02T20:18:10Z

-.-6eau: https://fccid.io/PPD-QCNFA324

== Summary ==
https://fccid.io/PPD-QCNFA324

File:Videri VQ SW2 SW3 DPC-450T.jpg

2024-12-02T20:16:53Z

-.-6eau:

File:Videri VQ CHRONTEL CH7515A TF.jpg

2024-12-02T20:15:58Z

-.-6eau:

File:Videri VQ 2QVBB PCB CHRONTEL eDP LVDSS.jpg

2024-12-02T20:14:50Z

-.-6eau:

File:Videri VQ Power Connection.jpg

2024-12-02T20:08:49Z

-.-6eau:

File:Videri VQ S'mores Field Trip.jpg

2024-12-02T20:06:10Z

-.-6eau:

Videri

2024-12-02T19:50:30Z

-.-6eau: Digital Canvas

<big>'''Introducing Videri Digital Canvas.'''</big>

''"The world’s thinnest, lightest and smartest Digital Canvas."''

== VQ ==

https://videri.com/wp-content/uploads/2023/06/Videri-Best-Practices-Guide_v2.0.pdf

=== Specifications ===

*DISPLAY
**Active Display Area 475.8mm x 475.8mm [18.73in x 18.73in]
**Resolution 1920 x 1920
**Brightness 450 NITS
**PPI 78
**Surface Treatment 20% Haze
**Color Gamut 92% NTSC
*TECHNOLOGY
**Processor DPC450 - 64GB onboard storage
**WiFi 802.11 g/n/ac @ 2.4/5GHz
**BlueTooth BT 4.0
**NFC Yes (@13.56MHz)
**Mech Outline 500 x 500 x 14mm
*OS Android 6
*POWER
**Input 100-240 VAC
**Consumption (typ) 52W
*ENVIRONMENT
**Operating Temp. 0C to 40C
**Operating Humidity 0-90% RH (non-condensing)
*CERTIFICATION & COMPLIANCE
**Safety UL, CSA, CB
*EMI/EMC FCC Class B, IC, CE
*SIZING
**Bezel Width 11.1mm (0.44in) 34 pixels
**Thickness 14.0mm (0.55in))
**Weight 4.4kg (9.8lbs)

=== Power ===

24 volt, 3.75 amp (90 watt). Custom cable with extension to barrel connector and mutli-country power brick.

=== WiFi / BlueTooth ===

QCNFA324

Masimo Neo SpO2 Sensor Single Pastient Use Disposable

2024-10-21T17:57:10Z

-.-6eau: -.-6eau moved page Masimo Neo SpO2 Sensor Single Pastient Use Disposable to Masimo Neo SpO2 Sensor Single Patient Use Disposable: Title typo

#REDIRECT [[Masimo Neo SpO2 Sensor Single Patient Use Disposable]]

Masimo Neo SpO2 Sensor Single Patient Use Disposable

2024-10-21T17:57:10Z

-.-6eau: -.-6eau moved page Masimo Neo SpO2 Sensor Single Pastient Use Disposable to Masimo Neo SpO2 Sensor Single Patient Use Disposable: Title typo

Masimo SpO2 Sensor, Pulse Oximetry, medical device. These are used as "single use" and can be worn for several days after initially being attached to a finger with elastic adhesive band. There is a 18 inch cable terminating at a 9 pin connector.

https://professional.masimo.com/products/sensors/lncs/single-use/
<gallery>
Masimo SpO2 Sensor LED Side.jpeg
Masimo SpO2 Sensor Fingernail Side.jpeg
Masimo SpO2 Sensor Flex Finger LED.jpg
Masimo SpO2 Sensor Connector.jpg
</gallery>

Masimo Neo SpO2 Sensor Single Patient Use Disposable

2024-10-21T17:56:42Z

-.-6eau: Created page with "Masimo SpO2 Sensor, Pulse Oximetry, medical device. These are used as "single use" and can be worn for several days after initially being attached to a finger with elastic adh..."

File:Masimo SpO2 Sensor LED Side.jpeg

2024-10-21T17:52:25Z

-.-6eau:

File:Masimo SpO2 Sensor Fingernail Side.jpeg

2024-10-21T17:51:31Z

-.-6eau:

File:Masimo SpO2 Sensor Flex Finger LED.jpg

2024-10-21T17:50:37Z

-.-6eau: LED and Optical Sensor on left, striped pattern over copper pad on right.

== Summary ==
LED and Optical Sensor on left, striped pattern over copper pad on right.

File:Masimo SpO2 Sensor Connector.jpg

2024-10-21T17:48:34Z

-.-6eau: 4x5 pin 0.1" pitch gold plated connectors attached to 18 inch cord and sensor.

== Summary ==
4x5 pin 0.1" pitch gold plated connectors attached to 18 inch cord and sensor.

Whirlybird

2024-10-12T23:00:13Z

-.-6eau: Image with test cases

[EXPERIMENTAL]
Direction Finding (DF)

This is an exercise that started with up-cycling some e-waste that contains 32 RGBW LEDs and an ESP32-S3-WROOM2. There is a myriad of other components presumably intended to interface with other control circuits.

The primary objective here is not to reverse engineer its previously intended purpose, rather invent a new purpose. The objective is to utilize the outer ring of 24 blinkies as a 360 degree direction indicator. The ESP32 module, which appears to never have been flashed with functioning firmware, is erased and flashed with a current Octal SPI build of Micropython.

For the most part the components on the PCB are not directly connected to the ESP32. Rather there is a number of connectors they are wired to for an alternative "main" processor. This includes the addressable RGBWs that are some variant of [https://cdn-shop.adafruit.com/product-files/2757/p2757_SK6812RGBW_REV01.pdf SK6812RGBW]. Additionally for some reason even though these are individually addressable in series of over a hundred, they are broken in to two independent chains of 24 spaced in an outer circular pattern and 8 more arranged inside that circle.

The board is likely designed as some sort of prototype of an evolution of a production product. It is unknown if it was intended to be a technical evaluation of various features, in ongoing development or a one off experiment. I have ended up with several dozen of these, there are many unknown and some number of issues. The majority of them have thus far had an issue with enabling "Boot Mode" and power on only to continually restart themselves.

Also used for [[Instant_Omni_Pro_18_Toaster_Oven_and_Air_Fryer|Singing "QSV" Toaster]]

Customized peripherals [[Whirlybird/IMU|IMU]] and [[Whirlybird/RS41|RS41]]

[[File:Whirlybird 3D Printed Enclosure Tests.jpeg|800px]]

= Components =

== TPS54202DDCR Buck Converter (3v3) ==

* Voltage In: 4.5-28 (12-28v typical)
* Voltage Out: Variable (5v typical)
* 2 Amp continuous, ~3 Amp current limit
* Over 90% Efficency 12v to 5v buck
* Package: SOT-6, Marking: "4202"
* [https://www.lcsc.com/datasheet/lcsc_datasheet_2410010331_Texas-Instruments-TPS54202DDCR_C191884.pdf Data Sheet]

Voltage In is provided from the first 4 pins of <code>J1</code> and this component is placed at <code>U9</code> with output voltage set point resistors <code>R25/R26</code> with values 100K and 22.1K respectively. Given the equation <code>(100/22.1 + 1) * 0.596 = 3.29</code>, the voltage output provided thru inductor <code>L2</code> in this configuration is set for 3.3 volts and provides the power to the ESP32 and related components. The 3v3 rail is also accessible at [TP](8) and voltage feedback at (TP13).

== LMR51440SDRRR Buck Converter (5v) ==
* Voltage In: 4-36
* Voltage Out: 0.8-28
* Max Current: 4 Amp
* Package: 12 Pin WSON 0.8mm Height
* [https://www.lcsc.com/datasheet/lcsc_datasheet_2309221225_Texas-Instruments-LMR51450FNDRRR_C5782413.pdf Datasheet]

The component is placed at <code>U7</code> and there is a bodge jumping the voltage set point pin via <code>R19/R20</code> with a 1K resistor to correct for an in initial routing error of <code>R21/R18</code> ~18K and 100K respectively. This all results in a designed output voltage of 5 volts thru inductor <code>L1</code> and accessible at [TP](3) along with the voltage feedback at (TP10).

== M.2 (NGFF) Key E ==
* Part #: [https://www.digikey.com/en/products/detail/amphenol-cs-fci/MDT420E03001/5810340 MDT420E03001]
* [https://www.amphenol-cs.com/product/mdt420e03001.html Amphenol Product Page]
* [https://cdn.amphenol-cs.com/media/wysiwyg/files/documentation/datasheet/ssio/ssio_pcie_m2.pdf Brochure]
* PCIe M.2 Connectors, Storage and Server Connector, P=0.5mm, H=4.2mm, Key E,Gold Plating

'''WARNING''' Pin out is not compatible with typical specifications!

Top is odd, bottom is even
* Ground Pins: 3,5,11,18,33,39,45,51,57,71,73
* 3v3 Pins: 2 & 4
* D+/D- Pins: 7 & 9 (via D6) to J7
* Tx/Rx Pins: 62 & 64 (via R37/R35)
* U16:P0_5 Pin: 54 (TP72)
* U16:P0_4 Pin: 67 (via Q1) to ground
* TP85-92 Pins: 38,46,48,50,52,56,58,60

== PI4IOE5V6416 I2C GPIO Expander ==
*I2C Address: 0x20 (32)
*Part Number: [https://www.diodes.com/datasheet/download/PI4IOE5V6416.pdf PI4IOE5V6416ZDEX] (TQFN)
*Size: 4mm x 4mm
*Pins: 24

{| class="wikitable"
|-
! Pin # !! Name !! Description|Function
|-
| 1 || P0_0 || I/O M3 via R51
|-
| 2 || P0_1 || I/O U6 & U8 Pin 3 (TP12,TP70)
|-
| 3 || P0_2 || I/O U56
|-
| 4 || P0_3 || I/O M5 Pin 67
|-
| 5 || P0_4 || GND M5 Pin 54
|-
| 6 || P0_5 || U15 Pin 4 via R44 (TP67)
|-
| 7 || P0_6 || P3 Pin 6 (TP68)
|-
| 8 || P0_7 || (TP62)
|-
| 9 || Vss || Ground
|-
| 10 || P1_0 || U54 Pin 4 via R80 (TP73), R34 O Ohm GPIO 16 & U10 Pin 4
|-
| 11 || P1_1 || J8 Pin 10 & R74 to GND (TP74)
|-
| 12 || P1_2 || U10 Pin 6 (TP75)
|-
| 13 || P1_3 || Select Input U11, HIGH for MicroSD SPI
|-
| 14 || P1_4 || U18 Pin 17 via R48 0 Ohm (TP77)
|-
| 15 || P1_5 || U17 Pin 1 (TOUT) & J9 & Pull-up via R7
|-
| 16 || P1_6 || U1 Pin 4 (TP2,TP81)
|-
| 17 || P1_7 || J9 (TP80)
|-
| 18 || ADDR || Address input, to Vdd or ground
|-
| 19 || SCL || Clock to Vdd via pull-up resistor
|-
| 20 || SDA || Data to Vdd via pull-up resistor
|-
| 21 || Vdd(P) || Power for Port P
|-
| 22 || INT || ESP32 GPIO8. Interrupt output, connect to Vdd via pull-up resistor
|-
| 23 || Vdd(I2C) || Power from I2C-bus, provides voltage-level translation
|-
| 24 || RESET || Active LOW reset (TP78), to Vdd via pull-up R45 10k
|}

== LEDs ==

=== RGBW 5050 ===
* Inner Chain
** U46,47,48,49,50,51,44,45
** Data in via R69 471 Ohm from U43 Pin 3 (TP118)
* Outer Chain
** U24,23,22,21,20,19,30,29,28,27,26,25,36,35,34,33,32,31,42,41,40,39,38,37
** Data in via R68 471 Ohm from U43 Pin 2 (TP63)
* ~5 volt via R17, L1, U7, J1 and USB/Header
* [https://cdn-shop.adafruit.com/product-files/2757/p2757_SK6812RGBW_REV01.pdf SK6812RGBW Datasheet (pdf)]
Note: May not be exact specification match for actual components used

Connected to ESP32 via U43 (muxer?)

=== Green 0603 ===
*Part Number: [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/1168/LTST-C193TGKT-5A.pdf LTST-C193TGKT-5A]
*Digi-Key #: [https://www.digikey.com/en/products/detail/liteon/LTST-C193TGKT-5A/2356246 160-1832-1-ND]
*Description: LED GREEN CLEAR CHIP SMD
*Size: 0603, 1.6mm x 0.8mm x 0.45mm
*Wavelength: 528nm

These are used for testing and some have been populated at D8-D16. Depending on how many are used they are 0-3 in parallel connected to the PCA9632 driver. Do to the lack of current limiting resistor and the high supply voltage, they tolerated a good level of abuse working out the appropriate PWM control for less than the rated 20mA.

=== PCA9632 I2C driver ===
4-bit Fm+ I2C-bus low power LED driver

*I2C Address: 0x62 (98)
*Type: PCA9632TK
*Marking: 9632
*Package: HVSON8
**plastic thermal enhanced very thin small outline package
**no leads
**8 terminals
**body 3 × 3 × 0.85 mm with 0.5 mm pitch
*Version: SOT908-1

This component is placed at <code>U55</code> with <code>LED0, LED1 & LED2</code> connected in groups of up to 3 LEDs in parallel providing a path to ground with the positive side of each LED going directly to >4 volts '''without''' a current limiting resistor. Using a PWM power value of <code>0xF0</code> or less seems to be quite reasonable and it is still quite visible with <code>0x01-0x05</code> as well, at least with the tested [[#Green 0603]] singularly or in a parallel pair.

Note: Datasheet claims that <code>LEDOUT</code> register supports LEDs are on, off, individual dimming or individual dimming and group dimming/blink. The individual dimming and group control states were only exclusively selectable in testing with bits <code>10, 11</code> for individual vs group control respectively.

{| class="wikitable"
|-
! Name !! Pin !! Type !! Description
|-
| LED0 || 1 || Out || LED driver 0
|-
| LED1 || 2 || Out || LED driver 1
|-
| LED2 || 3 || Out || LED driver 2
|-
| LED3 || 4 || Out || LED driver 3
|-
| GND || 5 || - || Ground
|-
| SCL || 6 || In || I2C Clock
|-
| SDA || 7 || In/Out || I2C Data
|-
| VDD || 8 || + || Power Supply
|}

*https://www.nxp.com/docs/en/data-sheet/PCA9632.pdf

Minimal test code, demonstrates individual channel dimming and group blink. Green LEDs were added to D8, D11, & D12.
<pre>
# PCA9632 I2C 4-Bit LED Driver by DEFAULT
from machine import Pin, SoftI2C, Timer
from time import sleep_ms
# I2C Address for LED Driver for D8-D16
ADDR = 0x62
# Register Addresses
MODE1 = 0x00 # 0x10=on,0x00=sleep
MODE2 = 0x01 # 0x00=dim,0x20=blink(group)
# 8-bit individual brightness
PWM0 = 0x02 # D11,D8,D14
PWM1 = 0x03 # D9,D10,D12
PWM2 = 0x04 # D16,D15,D13
PWM3 = 0x05 # not connected
# Group control
GRPPWM = 0x06 # 7-bit
GRPFREQ = 0x07 # 7-bit
# 0[1:0],1[3:2],2[5:4],3[7:6]
# 00=Off,01=On,10=PWMx,11=GRPPWM
LEDOUT = 0x08

# Whirlybird I2C (4+ devices connected)
i2c = SoftI2C(scl=4, sda=5, freq=100_000)

blinking = True

def write(reg,val):
i2c.writeto_mem(ADDR, reg, bytearray([val]))

def dim():
write(PWM0, 0x05) # D8 & D11
write(PWM1, 0x03) # D12
write(LEDOUT, 0x0A) # Enable PWM0 & PWM1
write(MODE2, 0x00)

def blink():
write(GRPPWM,0x0F) # Group brightness
write(GRPFREQ,0x0F) # Group blink rate
write(LEDOUT, 0x0F) # Enable DMBLNK
write(MODE2, 0x20)

def toggleMode(t):
global blinking
if blinking:
dim()
else:
blink()
blinking = not blinking

write(MODE1,0x00) # Power on Driver
toggleMode(None) # Start in Dimming
</pre>
[[User:-.-6eau|-.-6eau]] ([[User talk:-.-6eau|talk]]) 00:05, 4 October 2024 (UTC)

=== PI5L200 MUX ===

U11 connected to GPIO 6, 7 & 15 SPI. Normally open logic path to MicroSD J5.

Default connection is routed to M2 via U15, ''"scatch and sniff"'' for the routing RE win!

# Select Input U16 P1_3 grounded via 155K
# 1A0 Out to U15 Pin 1
# 1A1 Out to MicroSD MISO
# YA In from GPIO 15
# 1B0 Out to U15 Pin 16
# 1B1 Out to MicroSD Clock
# YB In from GPIO 7
# GND
# YC In from ?
# YC1 Out to ?
# YC0 Out to ?
# YD In from GPIO 6
# YD1 Out to MicroSD MOSI
# YD0 Out to U15 Pin 14
# Enable grounded (LOW enabled)
# Vcc

*https://www.digikey.com/en/products/detail/diodes-incorporated/PI5L200LE/1142607
*https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/2380/PI5L200.pdf

== LCD ==
*40 Pin Flat Flex connector at J8, backlight 18 volt boost from U54 enabled by GPIO Expand P1_0 or ESP32 GPIO 16.
*A number of pins are mux'd thru U18 and shared with camera.
*Looks to be RGB 8-bit per channel compatible, wired for RGB565 mode.
*Plausible match to:
**[https://cdn-shop.adafruit.com/product-files/2353/Datasheet.pdf 7" TFT 800x480 Datasheet]
**[https://cdn-shop.adafruit.com/product-files/1680/Datasheet.pdf 5" TFT 800x480 Datasheet]

== Camera ==
*24 Pin Flat Flex connector at J10, lighting LEDs driven by U55.
*Signaling is mux'd with LCD thru U18
*Plausible match to ESP32-CAM OV2640

== ESP32-S3-WROOM2 ==

=== Pin Layout ===

[[File:ESP32-S3-WROOM2 Pin Layout.png]]

=== Firmware ===

When connecting to a linux machine, the following can be seen via <code>dmesg | tail</code>.
<pre>
new full-speed USB device number 99 using xhci_hcd
New USB device found, idVendor=303a, idProduct=1001, bcdDevice= 1.01
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Product: USB JTAG/serial debug unit
Manufacturer: Espressif
SerialNumber: 68:B6:B3:##:##:##
cdc_acm 3-2:1.0: ttyACM0: USB ACM device
</pre>

While the device enumerates with USB connected and has the capacity to facilitate serial communications, it is not really feasible with the constant reboot cycle. There are two slight variations of the board, the ones with a populated micro SD slot mostly have this issue, and the others do not. However connecting to the <code>TXD0</code> pin to the <code>Rx</code> of a USB/Serial UART converter the following can be captured. Additionally holding the ESP32 in reset and monitoring the UART you can capture the following by briefly releasing the reset and then re-enabling reset, otherwise you will get a continuous flood of the same messages at <code>115200 baud</code>.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
</pre>

Further experimentation <strike>is indicating it may be related to a fault in the thru-hole GPI0 as</strike> directly shorting <code>GPIO0</code> (Pin 27) to ground can result in the following.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x36 (SPI_DOWNLOAD_BOOT)
wait spi download
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x36 (SPI_DOWNLOAD_BOOT)
Saved PC:0x400507ae
wait spi download
</pre>

Attempting to use <code>esptool.py</code> generates a <code>Connecting...</code> message and then the serial output generates and updated message.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x36 (SPI_DOWNLOAD_BOOT)
Saved PC:0x400507ae
wait spi download
</pre>

However this seems to hang the USB connection and nothing further happens until it times out.

'''Update:''' the results above have been the result of <code>GPIO46</code> (Pin 16) floating. This is resolved by pulling it to ground along with <code>GPIO0</code> to properly enable <code>USB/UART0</code> for flashing. This can also be achieved using <code>TP50</code> which also connects to <code>GPI046</code>.

Some of the boards do properly enter "Boot Mode" which is done by connecting <code>GPIO0</code> to ground. This can easily be done by using a jumper wire from a through hole header that exposes both <code>GPIO0</code> and ground and pressing a reset button immediately below it. Alternatively this can be achieved by using a wire pressed to the bottom right most module pin and the metal RF shield on top of the module while connecting USB to power on.

Successfully resetting with <code>GPIO0</code> low and monitoring the <code>Tx</code> pin output, the device will send the following when properly configured and enabled to work with <code>esptool.py</code>.
<pre>
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x0 (DOWNLOAD(USB/UART0))
waiting for download
</pre>

For first time use with Micropython a complete erase of flash should first be performed with the following,
<pre>
esptool.py -p /dev/ttyACM0 -b 115200 erase_flash
esptool.py v4.8.0
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_1v8)
Crystal is 40MHz
MAC: 68:b6:b3:3c:f4:24
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 70.8s
Hard resetting via RTS pin...
</pre>

Note in this instance RTS is not connected, however the device remains in "Boot Mode" and the following action can be performed.

<pre>
esptool.py -p /dev/ttyACM0 -b 1500000 write_flash -z 0 ESP32_GENERIC_S3-SPIRAM_OCT-20240920-v1.24.0-preview.335.gb08ddbba5.bin
esptool.py v4.8.0
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_1v8)
Crystal is 40MHz
MAC: 68:b6:b3:3c:f4:24
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 1500000
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00197fff...
Compressed 1668096 bytes to 1089606...
Wrote 1668096 bytes (1089606 compressed) at 0x00000000 in 18.7 seconds (effective 714.0 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
</pre>

Note that in this case without <code>RTS</code> the device must be manually power cycled or reset to load the new firmware. Now you should see a different enumeration via <code>dmesg</code>.

<pre>
new full-speed USB device number 41 using xhci_hcd
New USB device found, idVendor=303a, idProduct=4001, bcdDevice= 1.00
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Product: Espressif Device
Manufacturer: Espressif Systems
SerialNumber: 123456
cdc_acm 3-2:1.0: ttyACM0: USB ACM device
</pre>

Monitoring <code>TXD0</code> the following is received.

<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x2a (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
Octal Flash Mode Enabled
For OPI Flash, Use Default Flash Boot Mode
mode:SLOW_RD, clock div:1
load:0x3fce3820,len:0x105c
load:0x403c9700,len:0x4
load:0x403c9704,len:0xbd8
load:0x403cc700,len:0x2e34
entry 0x403c989c
MicroPython v1.24.0-preview.335.gb08ddbba5 on 2024-09-20; Generic ESP32S3 module with Octal-SPIRAM with ESP32S3
Type "help()" for more information.
>>>
</pre>

You can also now use the USB interface, with something like <code>screen /dev/ttyACM0 115200</code>. If successful you should be greeted with blank output. Pressing <code>Enter</code> should generate a Micropython prompt <code>>>></code> and pressing <code>Ctrl+D</code> generates the following.

<pre>
MPY: soft reboot
MicroPython v1.24.0-preview.335.gb08ddbba5 on 2024-09-20; Generic ESP32S3 module with Octal-SPIRAM with ESP32S3
Type "help()" for more information.
>>>
</pre>

There's various ways you can now access the device, including over WiFi once configured. I highly recommend <code>rshell</code> which provides the ability to copy and move files as well as directly write and debug code using REPL. If you don't pass any arguments it will automatically attempt to connect, if you have multiple devices you can also specify the connection parameters. Here the built in USB/Serial interface is connected via <code>D+/D-</code> pins.

<pre>
rshell -p /dev/ttyACM0 -b 115200
Using buffer-size of 256
Connecting to /dev/ttyACM0 (buffer-size 256)...
Trying to connect to REPL connected
Retrieving sysname ... esp32
Testing if ubinascii.unhexlify exists ... Y
Retrieving root directories ... /boot.py/ /main.py/
Setting time ... Sep 26, 2024 09:42:01
Evaluating board_name ... pyboard
Retrieving time epoch ... Jan 01, 2000
Welcome to rshell. Use Control-D (or the exit command) to exit rshell.
</pre>

Once launched, any running code may be halted, entering <code>repl</code> will give an interactive Micropython prompt. Entering <code>Ctrl+D</code> will do a soft reset and any code configured to automatically start such as <code>main.py</code> will then run and you will see any output such as from <code>print()</code> in the terminal.

== BOM ==

<pre>
# Whirlybird "ECPB-00011-000 1/18/2024"

# Top RGBW Side
U10 "ZMYC" 6 pin
U13 "16248" 16 pin (2x8) no lead package
U15 "AKK 7YW +" 16 pin (4x4) no lead package
U43 "R5 0401 235" SOIC-8
# RGBW 5050 Inner
U46 0 center right
U47 1 center left
U48 2 far left
U49 3 lower left
U50 4 lower center
U51 5 lower right
U44 6 far right
U45 7 top center
# RGBW 5050 Outer
U24 0 top right of center
U23 1
U22 2
U21 3
U20 4
U19 5 3 O'clock furthest right middle
U30 6
U29 7
U28 8
U27 9
U26 10
U25 11 6 O'clock lowest center
U36 12
U35 13
U34 14
U33 15
U32 16
U31 17 9 O'clock furthest left middle
U42 18
U41 19
U40 20
U39 21
U38 22
U37 23 12 O'clock highest center
J3 Vcc Rx Tx GND RST 0
TP1
TP3
TP5
TP7
TP85-92 Top right to M5 pins
TP50 GPIO46 & U18
CAP_WIRE capacitive touch wire connection

# Bottom ESP32 Side
C18,19 "47 HFT S73" Electrolytic
D1 "TV7 J9" 6 lead
D2 "B5 J" (next to RST1)
D3 "S8 D0" J3 header power input
D4 "S8 D0" USB power input
D5 USB Connection ESD 6 pin (top/left)
D6 USB Connection ESD 6 pin (left side)
D7 "S8 D0" USB power input
J1 2x8 Connector
J4,J7 Micro USB Connector
J5 MicroSD slot
J8 "2272N50" 40-Pin Flat Flex Connector
J9 6 pin flat flex
L1 "5R6"
L2 "100 2229"
M5 "Amphenol E"
M3B 12-pin flat flex
P1 10 pin JTAG pads
R2,3,6,7 0 Ohm
R27 "01C" (next to RST1)
RST1 Tacticle momentary switch
U1 "2NMT" 6 lead
U2 "2NMT" 6 lead
U3 "2NMT" 6 lead
U4 "2NMT" 6 lead
U6 "WXM" 5 lead 2x3
U7 "L5144S TI 328 AGCS"
U8 "LN8B" 5 lead 2x3
U9 "4202" 6 lead
U16 "PI410E5V 6416ZDE 2341GG"
U17 "22-Biw" Capacitice Touch
U52 "JE3h4" 3 lead
U53 "F9 NZ" 8 pin lead
U54 "GEC"
U55 PCA9632 "9632 78 05 D335" 2x4 no lead package
U56 "1C7H 358 AFF 5" 6 pin no lead package
</pre>

=== Gallery ===
<gallery>
RGBW ESP32-S3 wiring RED-GREEN.png
U18 SD642AO.jpg
U11 PI5L200LE.jpg
U16 PI4IOE5V9535.jpg
D6 USBLC6-2SC6.jpg
U15 AKK 7YW.jpg
U55 PCA9632TK.jpg
Whirlybird Scratch and Sniff via Probing.jpeg
Whirlybird Camera Flat Flex.jpeg
</gallery>

File:Whirlybird 3D Printed Enclosure Tests.jpeg

2024-10-12T22:58:12Z

-.-6eau:

Whirlybird/RS41

2024-10-12T22:55:33Z

-.-6eau: Image of BETA

Documenting a particular fork in this where the focus is integration via serial communications with [[Vaisala RS41 Radiosonde Weather Balloon Sensor Payload]] for details on the overall project see the main page [[Whirlybird]].

Expanding ESP32-S3 capabilities with RS41 Radiosonde integration utilizing UART communications. One proof of concept <code>TEST</code> prototype has been constructed using point to soldered connections. The current <code>BETA</code> is being constructed using a modified 10 conductor 1mm spaced flat ribbon cable and 2x5 2mm IDC connector. This makes for a "plug-able" adapter between the sonde and main PCB. The position and connections utilized are an interim test of developing a custom M.2 Key E form factor adapter.

[[File:Whirlybird RS41 BETA Plugable Connector.jpeg|800px]]

<code>BETA</code> pictured above and first demo'd at Mountain View Reverse Engineering October 2024. Note that the sparkle infused hot glue on the M.2 connector does not actually attache the RS41 Radiosonde. Only the connector is secured to the Whirlbird PCB in lue of a M.2 adapter board and allows the sonde to be hot swapped without any modifications, soldering or other connections.

<code>TEST</code> utilizes the regulated 3v3 power directly to the sondes MCU and a GPIO expander port that enables a sink to ground for reset. <code>BETA</code> is experimenting with supplying 4v7 to the battery connection so the sonde can power itself from integrated voltage regulators.

=== Connector Pin Out ===
This is the mapping to a IDC flat ribbon cable with the red stripe indicating Pin 1.

# GROUND
# SWDIO
# SWCLK
# RESET
# BATTERY
# BUCK/BOOST
# 3 VOLT
# TX
# RX
# GROUND

Sample output via serial of sensor reading with the additional RS41-SG'''P''' barometric pressure sensor module.
<pre>
# (S)ensors
RH: 41.65 RHtu: 31.19 Trh: 31.24 T: 26.24 Tref: 33.38
Tmcu: 31.44 C: 47.58 Rt: 1138.87 Rts: 1097.28 Tp: 0.0624 Cp: 0.3628
Pressure: 1000.49 PressureT(NTC): 31.95
</pre>

(Changed the IO Expander to control the ground to RS41 rather than RESET via Q1. This totally fails and likely overloads the transistor. Unusable in this configuration unless powered directly from battery terminals.)

(Connecting to a via after scratching off soldermask. Accidentally exposed part of the ground plane and covered with kapton tape. Hot glue for stability.)

(https://www.tag-connect.com/product/tc2050-idc-tag-connect-2050-idc)

<gallery>
Whirlybird RS41 TEST Positioning Top.jpeg
Whirlybird RS41 TEST Positioning.jpeg
Whirlybird RS41 TEST M.2 Connector Alignment Position.jpeg
Whirlybird RS41 ALPHA RESET IO Expander.jpeg
Whirlybird RS41 ALPHA Serial UART Tx Rx.jpeg
Whirlybird RS41 TEST M.2 Prototype Wiring.jpeg
Whirlybird RS41 TEST M.2 Assembled Power Reset Serial.jpeg
Whirlybird RS41 ALPHA M.2 Prototype Wiring.jpeg
RS41 Radiosonde IDC 10 Conductor Ribbon Cable Attachment.jpeg
Whirlybird RS41 BETA Plugable Connector.jpeg
Whirlybird RS41 BETA TEST ALPHA.jpeg
</gallery>

File:Whirlybird RS41 BETA Plugable Connector.jpeg

2024-10-12T22:47:46Z

-.-6eau: First functional test of a direct plug in connector for RS41 to Whirlybird only using Power & IO accessible from M.2

== Summary ==
First functional test of a direct plug in connector for RS41 to Whirlybird only using Power & IO accessible from M.2

Whirlybird

2024-10-12T22:41:37Z

-.-6eau: /* LMR51440SDRRR Buck Converter (5v) */ +Datasheet

[EXPERIMENTAL]
Direction Finding (DF)

This is an exercise that started with up-cycling some e-waste that contains 32 RGBW LEDs and an ESP32-S3-WROOM2. There is a myriad of other components presumably intended to interface with other control circuits.

The primary objective here is not to reverse engineer its previously intended purpose, rather invent a new purpose. The objective is to utilize the outer ring of 24 blinkies as a 360 degree direction indicator. The ESP32 module, which appears to never have been flashed with functioning firmware, is erased and flashed with a current Octal SPI build of Micropython.

For the most part the components on the PCB are not directly connected to the ESP32. Rather there is a number of connectors they are wired to for an alternative "main" processor. This includes the addressable RGBWs that are some variant of [https://cdn-shop.adafruit.com/product-files/2757/p2757_SK6812RGBW_REV01.pdf SK6812RGBW]. Additionally for some reason even though these are individually addressable in series of over a hundred, they are broken in to two independent chains of 24 spaced in an outer circular pattern and 8 more arranged inside that circle.

The board is likely designed as some sort of prototype of an evolution of a production product. It is unknown if it was intended to be a technical evaluation of various features, in ongoing development or a one off experiment. I have ended up with several dozen of these, there are many unknown and some number of issues. The majority of them have thus far had an issue with enabling "Boot Mode" and power on only to continually restart themselves.

Also used for [[Instant_Omni_Pro_18_Toaster_Oven_and_Air_Fryer|Singing "QSV" Toaster]]

Customized peripherals [[Whirlybird/IMU|IMU]] and [[Whirlybird/RS41|RS41]]

<br>
= Components =

== TPS54202DDCR Buck Converter (3v3) ==

* Voltage In: 4.5-28 (12-28v typical)
* Voltage Out: Variable (5v typical)
* 2 Amp continuous, ~3 Amp current limit
* Over 90% Efficency 12v to 5v buck
* Package: SOT-6, Marking: "4202"
* [https://www.lcsc.com/datasheet/lcsc_datasheet_2410010331_Texas-Instruments-TPS54202DDCR_C191884.pdf Data Sheet]

Voltage In is provided from the first 4 pins of <code>J1</code> and this component is placed at <code>U9</code> with output voltage set point resistors <code>R25/R26</code> with values 100K and 22.1K respectively. Given the equation <code>(100/22.1 + 1) * 0.596 = 3.29</code>, the voltage output provided thru inductor <code>L2</code> in this configuration is set for 3.3 volts and provides the power to the ESP32 and related components. The 3v3 rail is also accessible at [TP](8) and voltage feedback at (TP13).

== LMR51440SDRRR Buck Converter (5v) ==
* Voltage In: 4-36
* Voltage Out: 0.8-28
* Max Current: 4 Amp
* Package: 12 Pin WSON 0.8mm Height
* [https://www.lcsc.com/datasheet/lcsc_datasheet_2309221225_Texas-Instruments-LMR51450FNDRRR_C5782413.pdf Datasheet]

The component is placed at <code>U7</code> and there is a bodge jumping the voltage set point pin via <code>R19/R20</code> with a 1K resistor to correct for an in initial routing error of <code>R21/R18</code> ~18K and 100K respectively. This all results in a designed output voltage of 5 volts thru inductor <code>L1</code> and accessible at [TP](3) along with the voltage feedback at (TP10).

== M.2 (NGFF) Key E ==
* Part #: [https://www.digikey.com/en/products/detail/amphenol-cs-fci/MDT420E03001/5810340 MDT420E03001]
* [https://www.amphenol-cs.com/product/mdt420e03001.html Amphenol Product Page]
* [https://cdn.amphenol-cs.com/media/wysiwyg/files/documentation/datasheet/ssio/ssio_pcie_m2.pdf Brochure]
* PCIe M.2 Connectors, Storage and Server Connector, P=0.5mm, H=4.2mm, Key E,Gold Plating

'''WARNING''' Pin out is not compatible with typical specifications!

Top is odd, bottom is even
* Ground Pins: 3,5,11,18,33,39,45,51,57,71,73
* 3v3 Pins: 2 & 4
* D+/D- Pins: 7 & 9 (via D6) to J7
* Tx/Rx Pins: 62 & 64 (via R37/R35)
* U16:P0_5 Pin: 54 (TP72)
* U16:P0_4 Pin: 67 (via Q1) to ground
* TP85-92 Pins: 38,46,48,50,52,56,58,60

== PI4IOE5V6416 I2C GPIO Expander ==
*I2C Address: 0x20 (32)
*Part Number: [https://www.diodes.com/datasheet/download/PI4IOE5V6416.pdf PI4IOE5V6416ZDEX] (TQFN)
*Size: 4mm x 4mm
*Pins: 24

{| class="wikitable"
|-
! Pin # !! Name !! Description|Function
|-
| 1 || P0_0 || I/O M3 via R51
|-
| 2 || P0_1 || I/O U6 & U8 Pin 3 (TP12,TP70)
|-
| 3 || P0_2 || I/O U56
|-
| 4 || P0_3 || I/O M5 Pin 67
|-
| 5 || P0_4 || GND M5 Pin 54
|-
| 6 || P0_5 || U15 Pin 4 via R44 (TP67)
|-
| 7 || P0_6 || P3 Pin 6 (TP68)
|-
| 8 || P0_7 || (TP62)
|-
| 9 || Vss || Ground
|-
| 10 || P1_0 || U54 Pin 4 via R80 (TP73), R34 O Ohm GPIO 16 & U10 Pin 4
|-
| 11 || P1_1 || J8 Pin 10 & R74 to GND (TP74)
|-
| 12 || P1_2 || U10 Pin 6 (TP75)
|-
| 13 || P1_3 || Select Input U11, HIGH for MicroSD SPI
|-
| 14 || P1_4 || U18 Pin 17 via R48 0 Ohm (TP77)
|-
| 15 || P1_5 || U17 Pin 1 (TOUT) & J9 & Pull-up via R7
|-
| 16 || P1_6 || U1 Pin 4 (TP2,TP81)
|-
| 17 || P1_7 || J9 (TP80)
|-
| 18 || ADDR || Address input, to Vdd or ground
|-
| 19 || SCL || Clock to Vdd via pull-up resistor
|-
| 20 || SDA || Data to Vdd via pull-up resistor
|-
| 21 || Vdd(P) || Power for Port P
|-
| 22 || INT || ESP32 GPIO8. Interrupt output, connect to Vdd via pull-up resistor
|-
| 23 || Vdd(I2C) || Power from I2C-bus, provides voltage-level translation
|-
| 24 || RESET || Active LOW reset (TP78), to Vdd via pull-up R45 10k
|}

== LEDs ==

=== RGBW 5050 ===
* Inner Chain
** U46,47,48,49,50,51,44,45
** Data in via R69 471 Ohm from U43 Pin 3 (TP118)
* Outer Chain
** U24,23,22,21,20,19,30,29,28,27,26,25,36,35,34,33,32,31,42,41,40,39,38,37
** Data in via R68 471 Ohm from U43 Pin 2 (TP63)
* ~5 volt via R17, L1, U7, J1 and USB/Header
* [https://cdn-shop.adafruit.com/product-files/2757/p2757_SK6812RGBW_REV01.pdf SK6812RGBW Datasheet (pdf)]
Note: May not be exact specification match for actual components used

Connected to ESP32 via U43 (muxer?)

=== Green 0603 ===
*Part Number: [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/1168/LTST-C193TGKT-5A.pdf LTST-C193TGKT-5A]
*Digi-Key #: [https://www.digikey.com/en/products/detail/liteon/LTST-C193TGKT-5A/2356246 160-1832-1-ND]
*Description: LED GREEN CLEAR CHIP SMD
*Size: 0603, 1.6mm x 0.8mm x 0.45mm
*Wavelength: 528nm

These are used for testing and some have been populated at D8-D16. Depending on how many are used they are 0-3 in parallel connected to the PCA9632 driver. Do to the lack of current limiting resistor and the high supply voltage, they tolerated a good level of abuse working out the appropriate PWM control for less than the rated 20mA.

=== PCA9632 I2C driver ===
4-bit Fm+ I2C-bus low power LED driver

*I2C Address: 0x62 (98)
*Type: PCA9632TK
*Marking: 9632
*Package: HVSON8
**plastic thermal enhanced very thin small outline package
**no leads
**8 terminals
**body 3 × 3 × 0.85 mm with 0.5 mm pitch
*Version: SOT908-1

This component is placed at <code>U55</code> with <code>LED0, LED1 & LED2</code> connected in groups of up to 3 LEDs in parallel providing a path to ground with the positive side of each LED going directly to >4 volts '''without''' a current limiting resistor. Using a PWM power value of <code>0xF0</code> or less seems to be quite reasonable and it is still quite visible with <code>0x01-0x05</code> as well, at least with the tested [[#Green 0603]] singularly or in a parallel pair.

Note: Datasheet claims that <code>LEDOUT</code> register supports LEDs are on, off, individual dimming or individual dimming and group dimming/blink. The individual dimming and group control states were only exclusively selectable in testing with bits <code>10, 11</code> for individual vs group control respectively.

{| class="wikitable"
|-
! Name !! Pin !! Type !! Description
|-
| LED0 || 1 || Out || LED driver 0
|-
| LED1 || 2 || Out || LED driver 1
|-
| LED2 || 3 || Out || LED driver 2
|-
| LED3 || 4 || Out || LED driver 3
|-
| GND || 5 || - || Ground
|-
| SCL || 6 || In || I2C Clock
|-
| SDA || 7 || In/Out || I2C Data
|-
| VDD || 8 || + || Power Supply
|}

*https://www.nxp.com/docs/en/data-sheet/PCA9632.pdf

Minimal test code, demonstrates individual channel dimming and group blink. Green LEDs were added to D8, D11, & D12.
<pre>
# PCA9632 I2C 4-Bit LED Driver by DEFAULT
from machine import Pin, SoftI2C, Timer
from time import sleep_ms
# I2C Address for LED Driver for D8-D16
ADDR = 0x62
# Register Addresses
MODE1 = 0x00 # 0x10=on,0x00=sleep
MODE2 = 0x01 # 0x00=dim,0x20=blink(group)
# 8-bit individual brightness
PWM0 = 0x02 # D11,D8,D14
PWM1 = 0x03 # D9,D10,D12
PWM2 = 0x04 # D16,D15,D13
PWM3 = 0x05 # not connected
# Group control
GRPPWM = 0x06 # 7-bit
GRPFREQ = 0x07 # 7-bit
# 0[1:0],1[3:2],2[5:4],3[7:6]
# 00=Off,01=On,10=PWMx,11=GRPPWM
LEDOUT = 0x08

# Whirlybird I2C (4+ devices connected)
i2c = SoftI2C(scl=4, sda=5, freq=100_000)

blinking = True

def write(reg,val):
i2c.writeto_mem(ADDR, reg, bytearray([val]))

def dim():
write(PWM0, 0x05) # D8 & D11
write(PWM1, 0x03) # D12
write(LEDOUT, 0x0A) # Enable PWM0 & PWM1
write(MODE2, 0x00)

def blink():
write(GRPPWM,0x0F) # Group brightness
write(GRPFREQ,0x0F) # Group blink rate
write(LEDOUT, 0x0F) # Enable DMBLNK
write(MODE2, 0x20)

def toggleMode(t):
global blinking
if blinking:
dim()
else:
blink()
blinking = not blinking

write(MODE1,0x00) # Power on Driver
toggleMode(None) # Start in Dimming
</pre>
[[User:-.-6eau|-.-6eau]] ([[User talk:-.-6eau|talk]]) 00:05, 4 October 2024 (UTC)

=== PI5L200 MUX ===

U11 connected to GPIO 6, 7 & 15 SPI. Normally open logic path to MicroSD J5.

Default connection is routed to M2 via U15, ''"scatch and sniff"'' for the routing RE win!

# Select Input U16 P1_3 grounded via 155K
# 1A0 Out to U15 Pin 1
# 1A1 Out to MicroSD MISO
# YA In from GPIO 15
# 1B0 Out to U15 Pin 16
# 1B1 Out to MicroSD Clock
# YB In from GPIO 7
# GND
# YC In from ?
# YC1 Out to ?
# YC0 Out to ?
# YD In from GPIO 6
# YD1 Out to MicroSD MOSI
# YD0 Out to U15 Pin 14
# Enable grounded (LOW enabled)
# Vcc

*https://www.digikey.com/en/products/detail/diodes-incorporated/PI5L200LE/1142607
*https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/2380/PI5L200.pdf

== LCD ==
*40 Pin Flat Flex connector at J8, backlight 18 volt boost from U54 enabled by GPIO Expand P1_0 or ESP32 GPIO 16.
*A number of pins are mux'd thru U18 and shared with camera.
*Looks to be RGB 8-bit per channel compatible, wired for RGB565 mode.
*Plausible match to:
**[https://cdn-shop.adafruit.com/product-files/2353/Datasheet.pdf 7" TFT 800x480 Datasheet]
**[https://cdn-shop.adafruit.com/product-files/1680/Datasheet.pdf 5" TFT 800x480 Datasheet]

== Camera ==
*24 Pin Flat Flex connector at J10, lighting LEDs driven by U55.
*Signaling is mux'd with LCD thru U18
*Plausible match to ESP32-CAM OV2640

== ESP32-S3-WROOM2 ==

=== Pin Layout ===

[[File:ESP32-S3-WROOM2 Pin Layout.png]]

=== Firmware ===

When connecting to a linux machine, the following can be seen via <code>dmesg | tail</code>.
<pre>
new full-speed USB device number 99 using xhci_hcd
New USB device found, idVendor=303a, idProduct=1001, bcdDevice= 1.01
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Product: USB JTAG/serial debug unit
Manufacturer: Espressif
SerialNumber: 68:B6:B3:##:##:##
cdc_acm 3-2:1.0: ttyACM0: USB ACM device
</pre>

While the device enumerates with USB connected and has the capacity to facilitate serial communications, it is not really feasible with the constant reboot cycle. There are two slight variations of the board, the ones with a populated micro SD slot mostly have this issue, and the others do not. However connecting to the <code>TXD0</code> pin to the <code>Rx</code> of a USB/Serial UART converter the following can be captured. Additionally holding the ESP32 in reset and monitoring the UART you can capture the following by briefly releasing the reset and then re-enabling reset, otherwise you will get a continuous flood of the same messages at <code>115200 baud</code>.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
</pre>

Further experimentation <strike>is indicating it may be related to a fault in the thru-hole GPI0 as</strike> directly shorting <code>GPIO0</code> (Pin 27) to ground can result in the following.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x36 (SPI_DOWNLOAD_BOOT)
wait spi download
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x36 (SPI_DOWNLOAD_BOOT)
Saved PC:0x400507ae
wait spi download
</pre>

Attempting to use <code>esptool.py</code> generates a <code>Connecting...</code> message and then the serial output generates and updated message.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x36 (SPI_DOWNLOAD_BOOT)
Saved PC:0x400507ae
wait spi download
</pre>

However this seems to hang the USB connection and nothing further happens until it times out.

'''Update:''' the results above have been the result of <code>GPIO46</code> (Pin 16) floating. This is resolved by pulling it to ground along with <code>GPIO0</code> to properly enable <code>USB/UART0</code> for flashing. This can also be achieved using <code>TP50</code> which also connects to <code>GPI046</code>.

Some of the boards do properly enter "Boot Mode" which is done by connecting <code>GPIO0</code> to ground. This can easily be done by using a jumper wire from a through hole header that exposes both <code>GPIO0</code> and ground and pressing a reset button immediately below it. Alternatively this can be achieved by using a wire pressed to the bottom right most module pin and the metal RF shield on top of the module while connecting USB to power on.

Successfully resetting with <code>GPIO0</code> low and monitoring the <code>Tx</code> pin output, the device will send the following when properly configured and enabled to work with <code>esptool.py</code>.
<pre>
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x0 (DOWNLOAD(USB/UART0))
waiting for download
</pre>

For first time use with Micropython a complete erase of flash should first be performed with the following,
<pre>
esptool.py -p /dev/ttyACM0 -b 115200 erase_flash
esptool.py v4.8.0
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_1v8)
Crystal is 40MHz
MAC: 68:b6:b3:3c:f4:24
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 70.8s
Hard resetting via RTS pin...
</pre>

Note in this instance RTS is not connected, however the device remains in "Boot Mode" and the following action can be performed.

<pre>
esptool.py -p /dev/ttyACM0 -b 1500000 write_flash -z 0 ESP32_GENERIC_S3-SPIRAM_OCT-20240920-v1.24.0-preview.335.gb08ddbba5.bin
esptool.py v4.8.0
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_1v8)
Crystal is 40MHz
MAC: 68:b6:b3:3c:f4:24
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 1500000
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00197fff...
Compressed 1668096 bytes to 1089606...
Wrote 1668096 bytes (1089606 compressed) at 0x00000000 in 18.7 seconds (effective 714.0 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
</pre>

Note that in this case without <code>RTS</code> the device must be manually power cycled or reset to load the new firmware. Now you should see a different enumeration via <code>dmesg</code>.

<pre>
new full-speed USB device number 41 using xhci_hcd
New USB device found, idVendor=303a, idProduct=4001, bcdDevice= 1.00
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Product: Espressif Device
Manufacturer: Espressif Systems
SerialNumber: 123456
cdc_acm 3-2:1.0: ttyACM0: USB ACM device
</pre>

Monitoring <code>TXD0</code> the following is received.

<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x2a (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
Octal Flash Mode Enabled
For OPI Flash, Use Default Flash Boot Mode
mode:SLOW_RD, clock div:1
load:0x3fce3820,len:0x105c
load:0x403c9700,len:0x4
load:0x403c9704,len:0xbd8
load:0x403cc700,len:0x2e34
entry 0x403c989c
MicroPython v1.24.0-preview.335.gb08ddbba5 on 2024-09-20; Generic ESP32S3 module with Octal-SPIRAM with ESP32S3
Type "help()" for more information.
>>>
</pre>

You can also now use the USB interface, with something like <code>screen /dev/ttyACM0 115200</code>. If successful you should be greeted with blank output. Pressing <code>Enter</code> should generate a Micropython prompt <code>>>></code> and pressing <code>Ctrl+D</code> generates the following.

<pre>
MPY: soft reboot
MicroPython v1.24.0-preview.335.gb08ddbba5 on 2024-09-20; Generic ESP32S3 module with Octal-SPIRAM with ESP32S3
Type "help()" for more information.
>>>
</pre>

There's various ways you can now access the device, including over WiFi once configured. I highly recommend <code>rshell</code> which provides the ability to copy and move files as well as directly write and debug code using REPL. If you don't pass any arguments it will automatically attempt to connect, if you have multiple devices you can also specify the connection parameters. Here the built in USB/Serial interface is connected via <code>D+/D-</code> pins.

<pre>
rshell -p /dev/ttyACM0 -b 115200
Using buffer-size of 256
Connecting to /dev/ttyACM0 (buffer-size 256)...
Trying to connect to REPL connected
Retrieving sysname ... esp32
Testing if ubinascii.unhexlify exists ... Y
Retrieving root directories ... /boot.py/ /main.py/
Setting time ... Sep 26, 2024 09:42:01
Evaluating board_name ... pyboard
Retrieving time epoch ... Jan 01, 2000
Welcome to rshell. Use Control-D (or the exit command) to exit rshell.
</pre>

Once launched, any running code may be halted, entering <code>repl</code> will give an interactive Micropython prompt. Entering <code>Ctrl+D</code> will do a soft reset and any code configured to automatically start such as <code>main.py</code> will then run and you will see any output such as from <code>print()</code> in the terminal.

== BOM ==

<pre>
# Whirlybird "ECPB-00011-000 1/18/2024"

# Top RGBW Side
U10 "ZMYC" 6 pin
U13 "16248" 16 pin (2x8) no lead package
U15 "AKK 7YW +" 16 pin (4x4) no lead package
U43 "R5 0401 235" SOIC-8
# RGBW 5050 Inner
U46 0 center right
U47 1 center left
U48 2 far left
U49 3 lower left
U50 4 lower center
U51 5 lower right
U44 6 far right
U45 7 top center
# RGBW 5050 Outer
U24 0 top right of center
U23 1
U22 2
U21 3
U20 4
U19 5 3 O'clock furthest right middle
U30 6
U29 7
U28 8
U27 9
U26 10
U25 11 6 O'clock lowest center
U36 12
U35 13
U34 14
U33 15
U32 16
U31 17 9 O'clock furthest left middle
U42 18
U41 19
U40 20
U39 21
U38 22
U37 23 12 O'clock highest center
J3 Vcc Rx Tx GND RST 0
TP1
TP3
TP5
TP7
TP85-92 Top right to M5 pins
TP50 GPIO46 & U18
CAP_WIRE capacitive touch wire connection

# Bottom ESP32 Side
C18,19 "47 HFT S73" Electrolytic
D1 "TV7 J9" 6 lead
D2 "B5 J" (next to RST1)
D3 "S8 D0" J3 header power input
D4 "S8 D0" USB power input
D5 USB Connection ESD 6 pin (top/left)
D6 USB Connection ESD 6 pin (left side)
D7 "S8 D0" USB power input
J1 2x8 Connector
J4,J7 Micro USB Connector
J5 MicroSD slot
J8 "2272N50" 40-Pin Flat Flex Connector
J9 6 pin flat flex
L1 "5R6"
L2 "100 2229"
M5 "Amphenol E"
M3B 12-pin flat flex
P1 10 pin JTAG pads
R2,3,6,7 0 Ohm
R27 "01C" (next to RST1)
RST1 Tacticle momentary switch
U1 "2NMT" 6 lead
U2 "2NMT" 6 lead
U3 "2NMT" 6 lead
U4 "2NMT" 6 lead
U6 "WXM" 5 lead 2x3
U7 "L5144S TI 328 AGCS"
U8 "LN8B" 5 lead 2x3
U9 "4202" 6 lead
U16 "PI410E5V 6416ZDE 2341GG"
U17 "22-Biw" Capacitice Touch
U52 "JE3h4" 3 lead
U53 "F9 NZ" 8 pin lead
U54 "GEC"
U55 PCA9632 "9632 78 05 D335" 2x4 no lead package
U56 "1C7H 358 AFF 5" 6 pin no lead package
</pre>

<gallery>
RGBW ESP32-S3 wiring RED-GREEN.png
U18 SD642AO.jpg
U11 PI5L200LE.jpg
U16 PI4IOE5V9535.jpg
D6 USBLC6-2SC6.jpg
U15 AKK 7YW.jpg
U55 PCA9632TK.jpg
Whirlybird Scratch and Sniff via Probing.jpeg
Whirlybird Camera Flat Flex.jpeg
</gallery>

Whirlybird

2024-10-12T22:40:55Z

-.-6eau: /* Components */ U7 LMR51440SDRRR 5v

[EXPERIMENTAL]
Direction Finding (DF)

This is an exercise that started with up-cycling some e-waste that contains 32 RGBW LEDs and an ESP32-S3-WROOM2. There is a myriad of other components presumably intended to interface with other control circuits.

The primary objective here is not to reverse engineer its previously intended purpose, rather invent a new purpose. The objective is to utilize the outer ring of 24 blinkies as a 360 degree direction indicator. The ESP32 module, which appears to never have been flashed with functioning firmware, is erased and flashed with a current Octal SPI build of Micropython.

For the most part the components on the PCB are not directly connected to the ESP32. Rather there is a number of connectors they are wired to for an alternative "main" processor. This includes the addressable RGBWs that are some variant of [https://cdn-shop.adafruit.com/product-files/2757/p2757_SK6812RGBW_REV01.pdf SK6812RGBW]. Additionally for some reason even though these are individually addressable in series of over a hundred, they are broken in to two independent chains of 24 spaced in an outer circular pattern and 8 more arranged inside that circle.

The board is likely designed as some sort of prototype of an evolution of a production product. It is unknown if it was intended to be a technical evaluation of various features, in ongoing development or a one off experiment. I have ended up with several dozen of these, there are many unknown and some number of issues. The majority of them have thus far had an issue with enabling "Boot Mode" and power on only to continually restart themselves.

Also used for [[Instant_Omni_Pro_18_Toaster_Oven_and_Air_Fryer|Singing "QSV" Toaster]]

Customized peripherals [[Whirlybird/IMU|IMU]] and [[Whirlybird/RS41|RS41]]

<br>
= Components =

== TPS54202DDCR Buck Converter (3v3) ==

* Voltage In: 4.5-28 (12-28v typical)
* Voltage Out: Variable (5v typical)
* 2 Amp continuous, ~3 Amp current limit
* Over 90% Efficency 12v to 5v buck
* Package: SOT-6, Marking: "4202"
* [https://www.lcsc.com/datasheet/lcsc_datasheet_2410010331_Texas-Instruments-TPS54202DDCR_C191884.pdf Data Sheet]

Voltage In is provided from the first 4 pins of <code>J1</code> and this component is placed at <code>U9</code> with output voltage set point resistors <code>R25/R26</code> with values 100K and 22.1K respectively. Given the equation <code>(100/22.1 + 1) * 0.596 = 3.29</code>, the voltage output provided thru inductor <code>L2</code> in this configuration is set for 3.3 volts and provides the power to the ESP32 and related components. The 3v3 rail is also accessible at [TP](8) and voltage feedback at (TP13).

== LMR51440SDRRR Buck Converter (5v) ==
* Voltage In: 4-36
* Voltage Out: 0.8-28
* Max Current: 4 Amp
* Package: 12 Pin WSON 0.8mm Height

The component is placed at <code>U7</code> and there is a bodge jumping the voltage set point pin via <code>R19/R20</code> with a 1K resistor to correct for an in initial routing error of <code>R21/R18</code> ~18K and 100K respectively. This all results in a designed output voltage of 5 volts thru inductor <code>L1</code> and accessible at [TP](3) along with the voltage feedback at (TP10).

== M.2 (NGFF) Key E ==
* Part #: [https://www.digikey.com/en/products/detail/amphenol-cs-fci/MDT420E03001/5810340 MDT420E03001]
* [https://www.amphenol-cs.com/product/mdt420e03001.html Amphenol Product Page]
* [https://cdn.amphenol-cs.com/media/wysiwyg/files/documentation/datasheet/ssio/ssio_pcie_m2.pdf Brochure]
* PCIe M.2 Connectors, Storage and Server Connector, P=0.5mm, H=4.2mm, Key E,Gold Plating

'''WARNING''' Pin out is not compatible with typical specifications!

Top is odd, bottom is even
* Ground Pins: 3,5,11,18,33,39,45,51,57,71,73
* 3v3 Pins: 2 & 4
* D+/D- Pins: 7 & 9 (via D6) to J7
* Tx/Rx Pins: 62 & 64 (via R37/R35)
* U16:P0_5 Pin: 54 (TP72)
* U16:P0_4 Pin: 67 (via Q1) to ground
* TP85-92 Pins: 38,46,48,50,52,56,58,60

== PI4IOE5V6416 I2C GPIO Expander ==
*I2C Address: 0x20 (32)
*Part Number: [https://www.diodes.com/datasheet/download/PI4IOE5V6416.pdf PI4IOE5V6416ZDEX] (TQFN)
*Size: 4mm x 4mm
*Pins: 24

{| class="wikitable"
|-
! Pin # !! Name !! Description|Function
|-
| 1 || P0_0 || I/O M3 via R51
|-
| 2 || P0_1 || I/O U6 & U8 Pin 3 (TP12,TP70)
|-
| 3 || P0_2 || I/O U56
|-
| 4 || P0_3 || I/O M5 Pin 67
|-
| 5 || P0_4 || GND M5 Pin 54
|-
| 6 || P0_5 || U15 Pin 4 via R44 (TP67)
|-
| 7 || P0_6 || P3 Pin 6 (TP68)
|-
| 8 || P0_7 || (TP62)
|-
| 9 || Vss || Ground
|-
| 10 || P1_0 || U54 Pin 4 via R80 (TP73), R34 O Ohm GPIO 16 & U10 Pin 4
|-
| 11 || P1_1 || J8 Pin 10 & R74 to GND (TP74)
|-
| 12 || P1_2 || U10 Pin 6 (TP75)
|-
| 13 || P1_3 || Select Input U11, HIGH for MicroSD SPI
|-
| 14 || P1_4 || U18 Pin 17 via R48 0 Ohm (TP77)
|-
| 15 || P1_5 || U17 Pin 1 (TOUT) & J9 & Pull-up via R7
|-
| 16 || P1_6 || U1 Pin 4 (TP2,TP81)
|-
| 17 || P1_7 || J9 (TP80)
|-
| 18 || ADDR || Address input, to Vdd or ground
|-
| 19 || SCL || Clock to Vdd via pull-up resistor
|-
| 20 || SDA || Data to Vdd via pull-up resistor
|-
| 21 || Vdd(P) || Power for Port P
|-
| 22 || INT || ESP32 GPIO8. Interrupt output, connect to Vdd via pull-up resistor
|-
| 23 || Vdd(I2C) || Power from I2C-bus, provides voltage-level translation
|-
| 24 || RESET || Active LOW reset (TP78), to Vdd via pull-up R45 10k
|}

== LEDs ==

=== RGBW 5050 ===
* Inner Chain
** U46,47,48,49,50,51,44,45
** Data in via R69 471 Ohm from U43 Pin 3 (TP118)
* Outer Chain
** U24,23,22,21,20,19,30,29,28,27,26,25,36,35,34,33,32,31,42,41,40,39,38,37
** Data in via R68 471 Ohm from U43 Pin 2 (TP63)
* ~5 volt via R17, L1, U7, J1 and USB/Header
* [https://cdn-shop.adafruit.com/product-files/2757/p2757_SK6812RGBW_REV01.pdf SK6812RGBW Datasheet (pdf)]
Note: May not be exact specification match for actual components used

Connected to ESP32 via U43 (muxer?)

=== Green 0603 ===
*Part Number: [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/1168/LTST-C193TGKT-5A.pdf LTST-C193TGKT-5A]
*Digi-Key #: [https://www.digikey.com/en/products/detail/liteon/LTST-C193TGKT-5A/2356246 160-1832-1-ND]
*Description: LED GREEN CLEAR CHIP SMD
*Size: 0603, 1.6mm x 0.8mm x 0.45mm
*Wavelength: 528nm

These are used for testing and some have been populated at D8-D16. Depending on how many are used they are 0-3 in parallel connected to the PCA9632 driver. Do to the lack of current limiting resistor and the high supply voltage, they tolerated a good level of abuse working out the appropriate PWM control for less than the rated 20mA.

=== PCA9632 I2C driver ===
4-bit Fm+ I2C-bus low power LED driver

*I2C Address: 0x62 (98)
*Type: PCA9632TK
*Marking: 9632
*Package: HVSON8
**plastic thermal enhanced very thin small outline package
**no leads
**8 terminals
**body 3 × 3 × 0.85 mm with 0.5 mm pitch
*Version: SOT908-1

This component is placed at <code>U55</code> with <code>LED0, LED1 & LED2</code> connected in groups of up to 3 LEDs in parallel providing a path to ground with the positive side of each LED going directly to >4 volts '''without''' a current limiting resistor. Using a PWM power value of <code>0xF0</code> or less seems to be quite reasonable and it is still quite visible with <code>0x01-0x05</code> as well, at least with the tested [[#Green 0603]] singularly or in a parallel pair.

Note: Datasheet claims that <code>LEDOUT</code> register supports LEDs are on, off, individual dimming or individual dimming and group dimming/blink. The individual dimming and group control states were only exclusively selectable in testing with bits <code>10, 11</code> for individual vs group control respectively.

{| class="wikitable"
|-
! Name !! Pin !! Type !! Description
|-
| LED0 || 1 || Out || LED driver 0
|-
| LED1 || 2 || Out || LED driver 1
|-
| LED2 || 3 || Out || LED driver 2
|-
| LED3 || 4 || Out || LED driver 3
|-
| GND || 5 || - || Ground
|-
| SCL || 6 || In || I2C Clock
|-
| SDA || 7 || In/Out || I2C Data
|-
| VDD || 8 || + || Power Supply
|}

*https://www.nxp.com/docs/en/data-sheet/PCA9632.pdf

Minimal test code, demonstrates individual channel dimming and group blink. Green LEDs were added to D8, D11, & D12.
<pre>
# PCA9632 I2C 4-Bit LED Driver by DEFAULT
from machine import Pin, SoftI2C, Timer
from time import sleep_ms
# I2C Address for LED Driver for D8-D16
ADDR = 0x62
# Register Addresses
MODE1 = 0x00 # 0x10=on,0x00=sleep
MODE2 = 0x01 # 0x00=dim,0x20=blink(group)
# 8-bit individual brightness
PWM0 = 0x02 # D11,D8,D14
PWM1 = 0x03 # D9,D10,D12
PWM2 = 0x04 # D16,D15,D13
PWM3 = 0x05 # not connected
# Group control
GRPPWM = 0x06 # 7-bit
GRPFREQ = 0x07 # 7-bit
# 0[1:0],1[3:2],2[5:4],3[7:6]
# 00=Off,01=On,10=PWMx,11=GRPPWM
LEDOUT = 0x08

# Whirlybird I2C (4+ devices connected)
i2c = SoftI2C(scl=4, sda=5, freq=100_000)

blinking = True

def write(reg,val):
i2c.writeto_mem(ADDR, reg, bytearray([val]))

def dim():
write(PWM0, 0x05) # D8 & D11
write(PWM1, 0x03) # D12
write(LEDOUT, 0x0A) # Enable PWM0 & PWM1
write(MODE2, 0x00)

def blink():
write(GRPPWM,0x0F) # Group brightness
write(GRPFREQ,0x0F) # Group blink rate
write(LEDOUT, 0x0F) # Enable DMBLNK
write(MODE2, 0x20)

def toggleMode(t):
global blinking
if blinking:
dim()
else:
blink()
blinking = not blinking

write(MODE1,0x00) # Power on Driver
toggleMode(None) # Start in Dimming
</pre>
[[User:-.-6eau|-.-6eau]] ([[User talk:-.-6eau|talk]]) 00:05, 4 October 2024 (UTC)

=== PI5L200 MUX ===

U11 connected to GPIO 6, 7 & 15 SPI. Normally open logic path to MicroSD J5.

Default connection is routed to M2 via U15, ''"scatch and sniff"'' for the routing RE win!

# Select Input U16 P1_3 grounded via 155K
# 1A0 Out to U15 Pin 1
# 1A1 Out to MicroSD MISO
# YA In from GPIO 15
# 1B0 Out to U15 Pin 16
# 1B1 Out to MicroSD Clock
# YB In from GPIO 7
# GND
# YC In from ?
# YC1 Out to ?
# YC0 Out to ?
# YD In from GPIO 6
# YD1 Out to MicroSD MOSI
# YD0 Out to U15 Pin 14
# Enable grounded (LOW enabled)
# Vcc

*https://www.digikey.com/en/products/detail/diodes-incorporated/PI5L200LE/1142607
*https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/2380/PI5L200.pdf

== LCD ==
*40 Pin Flat Flex connector at J8, backlight 18 volt boost from U54 enabled by GPIO Expand P1_0 or ESP32 GPIO 16.
*A number of pins are mux'd thru U18 and shared with camera.
*Looks to be RGB 8-bit per channel compatible, wired for RGB565 mode.
*Plausible match to:
**[https://cdn-shop.adafruit.com/product-files/2353/Datasheet.pdf 7" TFT 800x480 Datasheet]
**[https://cdn-shop.adafruit.com/product-files/1680/Datasheet.pdf 5" TFT 800x480 Datasheet]

== Camera ==
*24 Pin Flat Flex connector at J10, lighting LEDs driven by U55.
*Signaling is mux'd with LCD thru U18
*Plausible match to ESP32-CAM OV2640

== ESP32-S3-WROOM2 ==

=== Pin Layout ===

[[File:ESP32-S3-WROOM2 Pin Layout.png]]

=== Firmware ===

When connecting to a linux machine, the following can be seen via <code>dmesg | tail</code>.
<pre>
new full-speed USB device number 99 using xhci_hcd
New USB device found, idVendor=303a, idProduct=1001, bcdDevice= 1.01
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Product: USB JTAG/serial debug unit
Manufacturer: Espressif
SerialNumber: 68:B6:B3:##:##:##
cdc_acm 3-2:1.0: ttyACM0: USB ACM device
</pre>

While the device enumerates with USB connected and has the capacity to facilitate serial communications, it is not really feasible with the constant reboot cycle. There are two slight variations of the board, the ones with a populated micro SD slot mostly have this issue, and the others do not. However connecting to the <code>TXD0</code> pin to the <code>Rx</code> of a USB/Serial UART converter the following can be captured. Additionally holding the ESP32 in reset and monitoring the UART you can capture the following by briefly releasing the reset and then re-enabling reset, otherwise you will get a continuous flood of the same messages at <code>115200 baud</code>.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
</pre>

Further experimentation <strike>is indicating it may be related to a fault in the thru-hole GPI0 as</strike> directly shorting <code>GPIO0</code> (Pin 27) to ground can result in the following.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x36 (SPI_DOWNLOAD_BOOT)
wait spi download
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x36 (SPI_DOWNLOAD_BOOT)
Saved PC:0x400507ae
wait spi download
</pre>

Attempting to use <code>esptool.py</code> generates a <code>Connecting...</code> message and then the serial output generates and updated message.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x36 (SPI_DOWNLOAD_BOOT)
Saved PC:0x400507ae
wait spi download
</pre>

However this seems to hang the USB connection and nothing further happens until it times out.

'''Update:''' the results above have been the result of <code>GPIO46</code> (Pin 16) floating. This is resolved by pulling it to ground along with <code>GPIO0</code> to properly enable <code>USB/UART0</code> for flashing. This can also be achieved using <code>TP50</code> which also connects to <code>GPI046</code>.

Some of the boards do properly enter "Boot Mode" which is done by connecting <code>GPIO0</code> to ground. This can easily be done by using a jumper wire from a through hole header that exposes both <code>GPIO0</code> and ground and pressing a reset button immediately below it. Alternatively this can be achieved by using a wire pressed to the bottom right most module pin and the metal RF shield on top of the module while connecting USB to power on.

Successfully resetting with <code>GPIO0</code> low and monitoring the <code>Tx</code> pin output, the device will send the following when properly configured and enabled to work with <code>esptool.py</code>.
<pre>
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x0 (DOWNLOAD(USB/UART0))
waiting for download
</pre>

For first time use with Micropython a complete erase of flash should first be performed with the following,
<pre>
esptool.py -p /dev/ttyACM0 -b 115200 erase_flash
esptool.py v4.8.0
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_1v8)
Crystal is 40MHz
MAC: 68:b6:b3:3c:f4:24
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 70.8s
Hard resetting via RTS pin...
</pre>

Note in this instance RTS is not connected, however the device remains in "Boot Mode" and the following action can be performed.

<pre>
esptool.py -p /dev/ttyACM0 -b 1500000 write_flash -z 0 ESP32_GENERIC_S3-SPIRAM_OCT-20240920-v1.24.0-preview.335.gb08ddbba5.bin
esptool.py v4.8.0
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_1v8)
Crystal is 40MHz
MAC: 68:b6:b3:3c:f4:24
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 1500000
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00197fff...
Compressed 1668096 bytes to 1089606...
Wrote 1668096 bytes (1089606 compressed) at 0x00000000 in 18.7 seconds (effective 714.0 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
</pre>

Note that in this case without <code>RTS</code> the device must be manually power cycled or reset to load the new firmware. Now you should see a different enumeration via <code>dmesg</code>.

<pre>
new full-speed USB device number 41 using xhci_hcd
New USB device found, idVendor=303a, idProduct=4001, bcdDevice= 1.00
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Product: Espressif Device
Manufacturer: Espressif Systems
SerialNumber: 123456
cdc_acm 3-2:1.0: ttyACM0: USB ACM device
</pre>

Monitoring <code>TXD0</code> the following is received.

<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x2a (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
Octal Flash Mode Enabled
For OPI Flash, Use Default Flash Boot Mode
mode:SLOW_RD, clock div:1
load:0x3fce3820,len:0x105c
load:0x403c9700,len:0x4
load:0x403c9704,len:0xbd8
load:0x403cc700,len:0x2e34
entry 0x403c989c
MicroPython v1.24.0-preview.335.gb08ddbba5 on 2024-09-20; Generic ESP32S3 module with Octal-SPIRAM with ESP32S3
Type "help()" for more information.
>>>
</pre>

You can also now use the USB interface, with something like <code>screen /dev/ttyACM0 115200</code>. If successful you should be greeted with blank output. Pressing <code>Enter</code> should generate a Micropython prompt <code>>>></code> and pressing <code>Ctrl+D</code> generates the following.

<pre>
MPY: soft reboot
MicroPython v1.24.0-preview.335.gb08ddbba5 on 2024-09-20; Generic ESP32S3 module with Octal-SPIRAM with ESP32S3
Type "help()" for more information.
>>>
</pre>

There's various ways you can now access the device, including over WiFi once configured. I highly recommend <code>rshell</code> which provides the ability to copy and move files as well as directly write and debug code using REPL. If you don't pass any arguments it will automatically attempt to connect, if you have multiple devices you can also specify the connection parameters. Here the built in USB/Serial interface is connected via <code>D+/D-</code> pins.

<pre>
rshell -p /dev/ttyACM0 -b 115200
Using buffer-size of 256
Connecting to /dev/ttyACM0 (buffer-size 256)...
Trying to connect to REPL connected
Retrieving sysname ... esp32
Testing if ubinascii.unhexlify exists ... Y
Retrieving root directories ... /boot.py/ /main.py/
Setting time ... Sep 26, 2024 09:42:01
Evaluating board_name ... pyboard
Retrieving time epoch ... Jan 01, 2000
Welcome to rshell. Use Control-D (or the exit command) to exit rshell.
</pre>

Once launched, any running code may be halted, entering <code>repl</code> will give an interactive Micropython prompt. Entering <code>Ctrl+D</code> will do a soft reset and any code configured to automatically start such as <code>main.py</code> will then run and you will see any output such as from <code>print()</code> in the terminal.

== BOM ==

<pre>
# Whirlybird "ECPB-00011-000 1/18/2024"

# Top RGBW Side
U10 "ZMYC" 6 pin
U13 "16248" 16 pin (2x8) no lead package
U15 "AKK 7YW +" 16 pin (4x4) no lead package
U43 "R5 0401 235" SOIC-8
# RGBW 5050 Inner
U46 0 center right
U47 1 center left
U48 2 far left
U49 3 lower left
U50 4 lower center
U51 5 lower right
U44 6 far right
U45 7 top center
# RGBW 5050 Outer
U24 0 top right of center
U23 1
U22 2
U21 3
U20 4
U19 5 3 O'clock furthest right middle
U30 6
U29 7
U28 8
U27 9
U26 10
U25 11 6 O'clock lowest center
U36 12
U35 13
U34 14
U33 15
U32 16
U31 17 9 O'clock furthest left middle
U42 18
U41 19
U40 20
U39 21
U38 22
U37 23 12 O'clock highest center
J3 Vcc Rx Tx GND RST 0
TP1
TP3
TP5
TP7
TP85-92 Top right to M5 pins
TP50 GPIO46 & U18
CAP_WIRE capacitive touch wire connection

# Bottom ESP32 Side
C18,19 "47 HFT S73" Electrolytic
D1 "TV7 J9" 6 lead
D2 "B5 J" (next to RST1)
D3 "S8 D0" J3 header power input
D4 "S8 D0" USB power input
D5 USB Connection ESD 6 pin (top/left)
D6 USB Connection ESD 6 pin (left side)
D7 "S8 D0" USB power input
J1 2x8 Connector
J4,J7 Micro USB Connector
J5 MicroSD slot
J8 "2272N50" 40-Pin Flat Flex Connector
J9 6 pin flat flex
L1 "5R6"
L2 "100 2229"
M5 "Amphenol E"
M3B 12-pin flat flex
P1 10 pin JTAG pads
R2,3,6,7 0 Ohm
R27 "01C" (next to RST1)
RST1 Tacticle momentary switch
U1 "2NMT" 6 lead
U2 "2NMT" 6 lead
U3 "2NMT" 6 lead
U4 "2NMT" 6 lead
U6 "WXM" 5 lead 2x3
U7 "L5144S TI 328 AGCS"
U8 "LN8B" 5 lead 2x3
U9 "4202" 6 lead
U16 "PI410E5V 6416ZDE 2341GG"
U17 "22-Biw" Capacitice Touch
U52 "JE3h4" 3 lead
U53 "F9 NZ" 8 pin lead
U54 "GEC"
U55 PCA9632 "9632 78 05 D335" 2x4 no lead package
U56 "1C7H 358 AFF 5" 6 pin no lead package
</pre>

<gallery>
RGBW ESP32-S3 wiring RED-GREEN.png
U18 SD642AO.jpg
U11 PI5L200LE.jpg
U16 PI4IOE5V9535.jpg
D6 USBLC6-2SC6.jpg
U15 AKK 7YW.jpg
U55 PCA9632TK.jpg
Whirlybird Scratch and Sniff via Probing.jpeg
Whirlybird Camera Flat Flex.jpeg
</gallery>

Whirlybird

2024-10-12T21:54:31Z

-.-6eau: /* Components */ 3v3 Buck U9 TPS54202DDCR

[EXPERIMENTAL]
Direction Finding (DF)

This is an exercise that started with up-cycling some e-waste that contains 32 RGBW LEDs and an ESP32-S3-WROOM2. There is a myriad of other components presumably intended to interface with other control circuits.

The primary objective here is not to reverse engineer its previously intended purpose, rather invent a new purpose. The objective is to utilize the outer ring of 24 blinkies as a 360 degree direction indicator. The ESP32 module, which appears to never have been flashed with functioning firmware, is erased and flashed with a current Octal SPI build of Micropython.

For the most part the components on the PCB are not directly connected to the ESP32. Rather there is a number of connectors they are wired to for an alternative "main" processor. This includes the addressable RGBWs that are some variant of [https://cdn-shop.adafruit.com/product-files/2757/p2757_SK6812RGBW_REV01.pdf SK6812RGBW]. Additionally for some reason even though these are individually addressable in series of over a hundred, they are broken in to two independent chains of 24 spaced in an outer circular pattern and 8 more arranged inside that circle.

The board is likely designed as some sort of prototype of an evolution of a production product. It is unknown if it was intended to be a technical evaluation of various features, in ongoing development or a one off experiment. I have ended up with several dozen of these, there are many unknown and some number of issues. The majority of them have thus far had an issue with enabling "Boot Mode" and power on only to continually restart themselves.

Also used for [[Instant_Omni_Pro_18_Toaster_Oven_and_Air_Fryer|Singing "QSV" Toaster]]

Customized peripherals [[Whirlybird/IMU|IMU]] and [[Whirlybird/RS41|RS41]]

<br>
= Components =

== TPS54202DDCR Buck Converter ==

* Voltage In: 4.5-28 (12-28v typical)
* Voltage Out: Variable (5v typical)
* 2 Amp continuous, ~3 Amp current limit
* Over 90% Efficency 12v to 5v buck
* Package: SOT-6, Marking: "4202"
* [https://www.lcsc.com/datasheet/lcsc_datasheet_2410010331_Texas-Instruments-TPS54202DDCR_C191884.pdf Data Sheet]

Voltage In is provided from the first 4 pins of <code>J1</code> and this component is placed at <code>U9</code> with output voltage set point resistors <code>R25/R26</code> with values 100K and 22.1K respectively. Given the equation <code>(100/22.1 + 1) * 0.596 = 3.29</code>, the voltage output provided thru inductor <code>L2</code> in this configuration is set for 3.3 volts and provides the power to the ESP32 and related components.

== M.2 (NGFF) Key E ==
* Part #: [https://www.digikey.com/en/products/detail/amphenol-cs-fci/MDT420E03001/5810340 MDT420E03001]
* [https://www.amphenol-cs.com/product/mdt420e03001.html Amphenol Product Page]
* [https://cdn.amphenol-cs.com/media/wysiwyg/files/documentation/datasheet/ssio/ssio_pcie_m2.pdf Brochure]
* PCIe M.2 Connectors, Storage and Server Connector, P=0.5mm, H=4.2mm, Key E,Gold Plating

'''WARNING''' Pin out is not compatible with typical specifications!

Top is odd, bottom is even
* Ground Pins: 3,5,11,18,33,39,45,51,57,71,73
* 3v3 Pins: 2 & 4
* D+/D- Pins: 7 & 9 (via D6) to J7
* Tx/Rx Pins: 62 & 64 (via R37/R35)
* U16:P0_5 Pin: 54 (TP72)
* U16:P0_4 Pin: 67 (via Q1) to ground
* TP85-92 Pins: 38,46,48,50,52,56,58,60

== PI4IOE5V6416 I2C GPIO Expander ==
*I2C Address: 0x20 (32)
*Part Number: [https://www.diodes.com/datasheet/download/PI4IOE5V6416.pdf PI4IOE5V6416ZDEX] (TQFN)
*Size: 4mm x 4mm
*Pins: 24

{| class="wikitable"
|-
! Pin # !! Name !! Description|Function
|-
| 1 || P0_0 || I/O M3 via R51
|-
| 2 || P0_1 || I/O U6 & U8 Pin 3 (TP12,TP70)
|-
| 3 || P0_2 || I/O U56
|-
| 4 || P0_3 || I/O M5 Pin 67
|-
| 5 || P0_4 || GND M5 Pin 54
|-
| 6 || P0_5 || U15 Pin 4 via R44 (TP67)
|-
| 7 || P0_6 || P3 Pin 6 (TP68)
|-
| 8 || P0_7 || (TP62)
|-
| 9 || Vss || Ground
|-
| 10 || P1_0 || U54 Pin 4 via R80 (TP73), R34 O Ohm GPIO 16 & U10 Pin 4
|-
| 11 || P1_1 || J8 Pin 10 & R74 to GND (TP74)
|-
| 12 || P1_2 || U10 Pin 6 (TP75)
|-
| 13 || P1_3 || Select Input U11, HIGH for MicroSD SPI
|-
| 14 || P1_4 || U18 Pin 17 via R48 0 Ohm (TP77)
|-
| 15 || P1_5 || U17 Pin 1 (TOUT) & J9 & Pull-up via R7
|-
| 16 || P1_6 || U1 Pin 4 (TP2,TP81)
|-
| 17 || P1_7 || J9 (TP80)
|-
| 18 || ADDR || Address input, to Vdd or ground
|-
| 19 || SCL || Clock to Vdd via pull-up resistor
|-
| 20 || SDA || Data to Vdd via pull-up resistor
|-
| 21 || Vdd(P) || Power for Port P
|-
| 22 || INT || ESP32 GPIO8. Interrupt output, connect to Vdd via pull-up resistor
|-
| 23 || Vdd(I2C) || Power from I2C-bus, provides voltage-level translation
|-
| 24 || RESET || Active LOW reset (TP78), to Vdd via pull-up R45 10k
|}

== LEDs ==

=== RGBW 5050 ===
* Inner Chain
** U46,47,48,49,50,51,44,45
** Data in via R69 471 Ohm from U43 Pin 3 (TP118)
* Outer Chain
** U24,23,22,21,20,19,30,29,28,27,26,25,36,35,34,33,32,31,42,41,40,39,38,37
** Data in via R68 471 Ohm from U43 Pin 2 (TP63)
* ~5 volt via R17, L1, U7, J1 and USB/Header
* [https://cdn-shop.adafruit.com/product-files/2757/p2757_SK6812RGBW_REV01.pdf SK6812RGBW Datasheet (pdf)]
Note: May not be exact specification match for actual components used

Connected to ESP32 via U43 (muxer?)

=== Green 0603 ===
*Part Number: [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/1168/LTST-C193TGKT-5A.pdf LTST-C193TGKT-5A]
*Digi-Key #: [https://www.digikey.com/en/products/detail/liteon/LTST-C193TGKT-5A/2356246 160-1832-1-ND]
*Description: LED GREEN CLEAR CHIP SMD
*Size: 0603, 1.6mm x 0.8mm x 0.45mm
*Wavelength: 528nm

These are used for testing and some have been populated at D8-D16. Depending on how many are used they are 0-3 in parallel connected to the PCA9632 driver. Do to the lack of current limiting resistor and the high supply voltage, they tolerated a good level of abuse working out the appropriate PWM control for less than the rated 20mA.

=== PCA9632 I2C driver ===
4-bit Fm+ I2C-bus low power LED driver

*I2C Address: 0x62 (98)
*Type: PCA9632TK
*Marking: 9632
*Package: HVSON8
**plastic thermal enhanced very thin small outline package
**no leads
**8 terminals
**body 3 × 3 × 0.85 mm with 0.5 mm pitch
*Version: SOT908-1

This component is placed at <code>U55</code> with <code>LED0, LED1 & LED2</code> connected in groups of up to 3 LEDs in parallel providing a path to ground with the positive side of each LED going directly to >4 volts '''without''' a current limiting resistor. Using a PWM power value of <code>0xF0</code> or less seems to be quite reasonable and it is still quite visible with <code>0x01-0x05</code> as well, at least with the tested [[#Green 0603]] singularly or in a parallel pair.

Note: Datasheet claims that <code>LEDOUT</code> register supports LEDs are on, off, individual dimming or individual dimming and group dimming/blink. The individual dimming and group control states were only exclusively selectable in testing with bits <code>10, 11</code> for individual vs group control respectively.

{| class="wikitable"
|-
! Name !! Pin !! Type !! Description
|-
| LED0 || 1 || Out || LED driver 0
|-
| LED1 || 2 || Out || LED driver 1
|-
| LED2 || 3 || Out || LED driver 2
|-
| LED3 || 4 || Out || LED driver 3
|-
| GND || 5 || - || Ground
|-
| SCL || 6 || In || I2C Clock
|-
| SDA || 7 || In/Out || I2C Data
|-
| VDD || 8 || + || Power Supply
|}

*https://www.nxp.com/docs/en/data-sheet/PCA9632.pdf

Minimal test code, demonstrates individual channel dimming and group blink. Green LEDs were added to D8, D11, & D12.
<pre>
# PCA9632 I2C 4-Bit LED Driver by DEFAULT
from machine import Pin, SoftI2C, Timer
from time import sleep_ms
# I2C Address for LED Driver for D8-D16
ADDR = 0x62
# Register Addresses
MODE1 = 0x00 # 0x10=on,0x00=sleep
MODE2 = 0x01 # 0x00=dim,0x20=blink(group)
# 8-bit individual brightness
PWM0 = 0x02 # D11,D8,D14
PWM1 = 0x03 # D9,D10,D12
PWM2 = 0x04 # D16,D15,D13
PWM3 = 0x05 # not connected
# Group control
GRPPWM = 0x06 # 7-bit
GRPFREQ = 0x07 # 7-bit
# 0[1:0],1[3:2],2[5:4],3[7:6]
# 00=Off,01=On,10=PWMx,11=GRPPWM
LEDOUT = 0x08

# Whirlybird I2C (4+ devices connected)
i2c = SoftI2C(scl=4, sda=5, freq=100_000)

blinking = True

def write(reg,val):
i2c.writeto_mem(ADDR, reg, bytearray([val]))

def dim():
write(PWM0, 0x05) # D8 & D11
write(PWM1, 0x03) # D12
write(LEDOUT, 0x0A) # Enable PWM0 & PWM1
write(MODE2, 0x00)

def blink():
write(GRPPWM,0x0F) # Group brightness
write(GRPFREQ,0x0F) # Group blink rate
write(LEDOUT, 0x0F) # Enable DMBLNK
write(MODE2, 0x20)

def toggleMode(t):
global blinking
if blinking:
dim()
else:
blink()
blinking = not blinking

write(MODE1,0x00) # Power on Driver
toggleMode(None) # Start in Dimming
</pre>
[[User:-.-6eau|-.-6eau]] ([[User talk:-.-6eau|talk]]) 00:05, 4 October 2024 (UTC)

=== PI5L200 MUX ===

U11 connected to GPIO 6, 7 & 15 SPI. Normally open logic path to MicroSD J5.

Default connection is routed to M2 via U15, ''"scatch and sniff"'' for the routing RE win!

# Select Input U16 P1_3 grounded via 155K
# 1A0 Out to U15 Pin 1
# 1A1 Out to MicroSD MISO
# YA In from GPIO 15
# 1B0 Out to U15 Pin 16
# 1B1 Out to MicroSD Clock
# YB In from GPIO 7
# GND
# YC In from ?
# YC1 Out to ?
# YC0 Out to ?
# YD In from GPIO 6
# YD1 Out to MicroSD MOSI
# YD0 Out to U15 Pin 14
# Enable grounded (LOW enabled)
# Vcc

*https://www.digikey.com/en/products/detail/diodes-incorporated/PI5L200LE/1142607
*https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/2380/PI5L200.pdf

== LCD ==
*40 Pin Flat Flex connector at J8, backlight 18 volt boost from U54 enabled by GPIO Expand P1_0 or ESP32 GPIO 16.
*A number of pins are mux'd thru U18 and shared with camera.
*Looks to be RGB 8-bit per channel compatible, wired for RGB565 mode.
*Plausible match to:
**[https://cdn-shop.adafruit.com/product-files/2353/Datasheet.pdf 7" TFT 800x480 Datasheet]
**[https://cdn-shop.adafruit.com/product-files/1680/Datasheet.pdf 5" TFT 800x480 Datasheet]

== Camera ==
*24 Pin Flat Flex connector at J10, lighting LEDs driven by U55.
*Signaling is mux'd with LCD thru U18
*Plausible match to ESP32-CAM OV2640

== ESP32-S3-WROOM2 ==

=== Pin Layout ===

[[File:ESP32-S3-WROOM2 Pin Layout.png]]

=== Firmware ===

When connecting to a linux machine, the following can be seen via <code>dmesg | tail</code>.
<pre>
new full-speed USB device number 99 using xhci_hcd
New USB device found, idVendor=303a, idProduct=1001, bcdDevice= 1.01
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Product: USB JTAG/serial debug unit
Manufacturer: Espressif
SerialNumber: 68:B6:B3:##:##:##
cdc_acm 3-2:1.0: ttyACM0: USB ACM device
</pre>

While the device enumerates with USB connected and has the capacity to facilitate serial communications, it is not really feasible with the constant reboot cycle. There are two slight variations of the board, the ones with a populated micro SD slot mostly have this issue, and the others do not. However connecting to the <code>TXD0</code> pin to the <code>Rx</code> of a USB/Serial UART converter the following can be captured. Additionally holding the ESP32 in reset and monitoring the UART you can capture the following by briefly releasing the reset and then re-enabling reset, otherwise you will get a continuous flood of the same messages at <code>115200 baud</code>.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
invalid header: 0xa5ff005a
</pre>

Further experimentation <strike>is indicating it may be related to a fault in the thru-hole GPI0 as</strike> directly shorting <code>GPIO0</code> (Pin 27) to ground can result in the following.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x36 (SPI_DOWNLOAD_BOOT)
wait spi download
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x36 (SPI_DOWNLOAD_BOOT)
Saved PC:0x400507ae
wait spi download
</pre>

Attempting to use <code>esptool.py</code> generates a <code>Connecting...</code> message and then the serial output generates and updated message.
<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x36 (SPI_DOWNLOAD_BOOT)
Saved PC:0x400507ae
wait spi download
</pre>

However this seems to hang the USB connection and nothing further happens until it times out.

'''Update:''' the results above have been the result of <code>GPIO46</code> (Pin 16) floating. This is resolved by pulling it to ground along with <code>GPIO0</code> to properly enable <code>USB/UART0</code> for flashing. This can also be achieved using <code>TP50</code> which also connects to <code>GPI046</code>.

Some of the boards do properly enter "Boot Mode" which is done by connecting <code>GPIO0</code> to ground. This can easily be done by using a jumper wire from a through hole header that exposes both <code>GPIO0</code> and ground and pressing a reset button immediately below it. Alternatively this can be achieved by using a wire pressed to the bottom right most module pin and the metal RF shield on top of the module while connecting USB to power on.

Successfully resetting with <code>GPIO0</code> low and monitoring the <code>Tx</code> pin output, the device will send the following when properly configured and enabled to work with <code>esptool.py</code>.
<pre>
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x0 (DOWNLOAD(USB/UART0))
waiting for download
</pre>

For first time use with Micropython a complete erase of flash should first be performed with the following,
<pre>
esptool.py -p /dev/ttyACM0 -b 115200 erase_flash
esptool.py v4.8.0
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_1v8)
Crystal is 40MHz
MAC: 68:b6:b3:3c:f4:24
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 70.8s
Hard resetting via RTS pin...
</pre>

Note in this instance RTS is not connected, however the device remains in "Boot Mode" and the following action can be performed.

<pre>
esptool.py -p /dev/ttyACM0 -b 1500000 write_flash -z 0 ESP32_GENERIC_S3-SPIRAM_OCT-20240920-v1.24.0-preview.335.gb08ddbba5.bin
esptool.py v4.8.0
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_1v8)
Crystal is 40MHz
MAC: 68:b6:b3:3c:f4:24
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 1500000
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00197fff...
Compressed 1668096 bytes to 1089606...
Wrote 1668096 bytes (1089606 compressed) at 0x00000000 in 18.7 seconds (effective 714.0 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
</pre>

Note that in this case without <code>RTS</code> the device must be manually power cycled or reset to load the new firmware. Now you should see a different enumeration via <code>dmesg</code>.

<pre>
new full-speed USB device number 41 using xhci_hcd
New USB device found, idVendor=303a, idProduct=4001, bcdDevice= 1.00
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Product: Espressif Device
Manufacturer: Espressif Systems
SerialNumber: 123456
cdc_acm 3-2:1.0: ttyACM0: USB ACM device
</pre>

Monitoring <code>TXD0</code> the following is received.

<pre>
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x2a (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
Octal Flash Mode Enabled
For OPI Flash, Use Default Flash Boot Mode
mode:SLOW_RD, clock div:1
load:0x3fce3820,len:0x105c
load:0x403c9700,len:0x4
load:0x403c9704,len:0xbd8
load:0x403cc700,len:0x2e34
entry 0x403c989c
MicroPython v1.24.0-preview.335.gb08ddbba5 on 2024-09-20; Generic ESP32S3 module with Octal-SPIRAM with ESP32S3
Type "help()" for more information.
>>>
</pre>

You can also now use the USB interface, with something like <code>screen /dev/ttyACM0 115200</code>. If successful you should be greeted with blank output. Pressing <code>Enter</code> should generate a Micropython prompt <code>>>></code> and pressing <code>Ctrl+D</code> generates the following.

<pre>
MPY: soft reboot
MicroPython v1.24.0-preview.335.gb08ddbba5 on 2024-09-20; Generic ESP32S3 module with Octal-SPIRAM with ESP32S3
Type "help()" for more information.
>>>
</pre>

There's various ways you can now access the device, including over WiFi once configured. I highly recommend <code>rshell</code> which provides the ability to copy and move files as well as directly write and debug code using REPL. If you don't pass any arguments it will automatically attempt to connect, if you have multiple devices you can also specify the connection parameters. Here the built in USB/Serial interface is connected via <code>D+/D-</code> pins.

<pre>
rshell -p /dev/ttyACM0 -b 115200
Using buffer-size of 256
Connecting to /dev/ttyACM0 (buffer-size 256)...
Trying to connect to REPL connected
Retrieving sysname ... esp32
Testing if ubinascii.unhexlify exists ... Y
Retrieving root directories ... /boot.py/ /main.py/
Setting time ... Sep 26, 2024 09:42:01
Evaluating board_name ... pyboard
Retrieving time epoch ... Jan 01, 2000
Welcome to rshell. Use Control-D (or the exit command) to exit rshell.
</pre>

Once launched, any running code may be halted, entering <code>repl</code> will give an interactive Micropython prompt. Entering <code>Ctrl+D</code> will do a soft reset and any code configured to automatically start such as <code>main.py</code> will then run and you will see any output such as from <code>print()</code> in the terminal.

== BOM ==

<pre>
# Whirlybird "ECPB-00011-000 1/18/2024"

# Top RGBW Side
U10 "ZMYC" 6 pin
U13 "16248" 16 pin (2x8) no lead package
U15 "AKK 7YW +" 16 pin (4x4) no lead package
U43 "R5 0401 235" SOIC-8
# RGBW 5050 Inner
U46 0 center right
U47 1 center left
U48 2 far left
U49 3 lower left
U50 4 lower center
U51 5 lower right
U44 6 far right
U45 7 top center
# RGBW 5050 Outer
U24 0 top right of center
U23 1
U22 2
U21 3
U20 4
U19 5 3 O'clock furthest right middle
U30 6
U29 7
U28 8
U27 9
U26 10
U25 11 6 O'clock lowest center
U36 12
U35 13
U34 14
U33 15
U32 16
U31 17 9 O'clock furthest left middle
U42 18
U41 19
U40 20
U39 21
U38 22
U37 23 12 O'clock highest center
J3 Vcc Rx Tx GND RST 0
TP1
TP3
TP5
TP7
TP85-92 Top right to M5 pins
TP50 GPIO46 & U18
CAP_WIRE capacitive touch wire connection

# Bottom ESP32 Side
C18,19 "47 HFT S73" Electrolytic
D1 "TV7 J9" 6 lead
D2 "B5 J" (next to RST1)
D3 "S8 D0" J3 header power input
D4 "S8 D0" USB power input
D5 USB Connection ESD 6 pin (top/left)
D6 USB Connection ESD 6 pin (left side)
D7 "S8 D0" USB power input
J1 2x8 Connector
J4,J7 Micro USB Connector
J5 MicroSD slot
J8 "2272N50" 40-Pin Flat Flex Connector
J9 6 pin flat flex
L1 "5R6"
L2 "100 2229"
M5 "Amphenol E"
M3B 12-pin flat flex
P1 10 pin JTAG pads
R2,3,6,7 0 Ohm
R27 "01C" (next to RST1)
RST1 Tacticle momentary switch
U1 "2NMT" 6 lead
U2 "2NMT" 6 lead
U3 "2NMT" 6 lead
U4 "2NMT" 6 lead
U6 "WXM" 5 lead 2x3
U7 "L5144S TI 328 AGCS"
U8 "LN8B" 5 lead 2x3
U9 "4202" 6 lead
U16 "PI410E5V 6416ZDE 2341GG"
U17 "22-Biw" Capacitice Touch
U52 "JE3h4" 3 lead
U53 "F9 NZ" 8 pin lead
U54 "GEC"
U55 PCA9632 "9632 78 05 D335" 2x4 no lead package
U56 "1C7H 358 AFF 5" 6 pin no lead package
</pre>

<gallery>
RGBW ESP32-S3 wiring RED-GREEN.png
U18 SD642AO.jpg
U11 PI5L200LE.jpg
U16 PI4IOE5V9535.jpg
D6 USBLC6-2SC6.jpg
U15 AKK 7YW.jpg
U55 PCA9632TK.jpg
Whirlybird Scratch and Sniff via Probing.jpeg
Whirlybird Camera Flat Flex.jpeg
</gallery>