Best posts made by easytarget

@HappyUser The Tab5 also has a M-BUS interface (the big 30pin socket on the back) and mounting points for the m-bus modules.

So; in theory you can 'just' plug in one of the modules from here: https://docs.m5stack.com/en/products?id=for stack-module

But in practice it will probably need a bunch of work and understanding to get the pin assignments and drivers on the tab5 aligned and working.

• There are other interesting M-BUS modules available (GPS, motor drive, prototype board, etc..)
• The tab5 has the correct threaded mounting points to make the boards secure etc.

@manmade
I dont see the nRESET signal being removed from the LCD, TouchPanel (and Camera).
It's a low=active reset for these devices, and the E1 pi4ioe5v6408 chip that controls them will default these pins to low (actually, input-pulldown) and holds the reset pin active. These are pins 4,5,6 on the chip:

Maybe you need something like:

  - platform: gpio
    id: lcd_nreset
    name: "LCD nRESET"
    pin:
      pi4ioe5v6408: pi4ioe1
      number: 4
    restore_mode: ALWAYS_ON

  - platform: gpio
    id: tp_nreset
    name: "TP nRESET"
    pin:
      pi4ioe5v6408: pi4ioe1
      number: 5
    restore_mode: ALWAYS_ON

  - platform: gpio
    id: cam_nreset
    name: "CAM nRESET"
    pin:
      pi4ioe5v6408: pi4ioe1
      number: 6
    restore_mode: ALWAYS_ON

Because these are active-low lines they are being applied when the unit powers up, you have to explicitly remove them after boot.

This is a guess, I'm not running HA on my tab5. There may be other things that need to happen too or are broken. But I just spent all day playing with some TAB5 hardware stuff in MicroPython and
this was one of the things I discovered..

Hi. I've been looking at the Tab5 Schematics a lot recently. And noticed something that appears 'wrong'.

In the block diagrams the camera modules CAM_MCLK line is shown as coming from pin G36 of the esp32-p4.

But the schematic tells a different story;

On the ESP32-P4 we have CAM_MCLK_GPIO36 coming from the esp32-p4:

It has a 10K pullup (R10) to SOC_3.3V:

But then is not used!

There are two N/C (Not Connected) resistors (R27 & R109) on the connection to U35 (which drives the camera modules CAM_MCLK_1V8 at 1.8v)

But note that the connection shown as PXT24M is connected, and comes from X2, a 24 MHz CMOS crystal oscillator.

Which is correct? The Schematic or the block diagrams?

If setting up a camera driver on the Tab5 can we safely ignore setting up gpio36 and just assume the camera MCLK is permanently fixed at 24MHz?

Edit: This isnt a criticism, it's quite normal; The board was designed so that it can accommodate two different camera module units. And the decision about which one to use can then be made closer to production time. Circuit designers do this a lot; the appropriate components are added/removed at production time without the PCB layout needing to be changed.