kaluga devkit

[chegewara]

Hi,
i just received new kaluga kit and it is awesome. For that price it come with LCD, camera, touch pad board, music board and of course esp32 S2 with FT2232C dual UART. Everything nicely packaged.

It is more question rather than complaining now. My board is behaving strange, because after reset with RST button i am getting such logs:

ESP-ROM:esp32s2-rc4-20191025
Build:Oct 25 2019
rst:0x10 (RTCWDT_RTC_RST),boot:0x19 (SPI_FAST_FLASH_BOOT)
invalid header: 0xffffff3f
invalid header: 0xffffff3f
invalid header: 0xffffff3f
invalid header: 0xffffff3f
invalid header: 0xffffff3f
invalid header: 0xffffff3f
invalid header: 0xffffff3f
invalid header: 0xffffff3f
invalid header: 0xffffff3f
invalid header: 0xffffff1f
invalid header: 0xffffff1f
invalid header: 0xffffff1f

Then it reboots after few seconds and the same logs. I have to use turn on/off switch to make it running with pre-installed demo app.

I have also question. I see that display should be touch screen capable, but its not responding, is it implemented in demo?
Is it intended in demo to display image from camera with dithered gray scale or maybe i am so unlucky and my example is damaged?

20200521_103922.jpg (4.88 MiB) Viewed 10591 times

[chegewara]

I tested with examples from https://github.com/espressif/esp-dev-kits and touch pad board does not react, display is working good and camera example is displaying the same picture as demo shipped with board, dithered gray scale.

Parts number i got:
- kaluga-1 v1.2
- camera LyraP cam v1.0
- touch board lyraP TouchA v1.1
- display LyraP esp32 v1.1 (ST7789V)
- audio lyraT 8311A v1.2

Touch pad example output:

I (567) Touch pad: Denoise function init
I (577) Touch pad: touch pad waterproof init
I (577) Touch pad: touch pad filter init
I (687) Touch pad: touch pad [8] base 4194303, thresh 41943
I (687) Touch pad: touch pad [3] base 4194303, thresh 41943
I (687) Touch pad: touch pad [11] base 4194303, thresh 41943
I (687) Touch pad: touch pad [13] base 4194303, thresh 41943
I (697) Touch pad: touch pad [2] base 4194303, thresh 41943
I (707) Touch pad: touch pad [9] base 4194303, thresh 41943
I (707) Touch pad: touch pad [4] base 4194303, thresh 41943

EDIT i flashed the same code with saola wroom and here is result:

I (330) Touch pad: Initializing touch pad
I (330) Touch pad: Denoise function init
I (340) Touch pad: touch pad waterproof init
I (340) Touch pad: touch pad filter init
I (450) Touch pad: touch pad [8] base 7951, thresh 79
I (450) Touch pad: touch pad [3] base 7772, thresh 77
I (450) Touch pad: touch pad [11] base 8688, thresh 86
I (450) Touch pad: touch pad [13] base 8464, thresh 84
I (460) Touch pad: touch pad [2] base 7292, thresh 72
I (460) Touch pad: touch pad [9] base 8257, thresh 82
I (470) Touch pad: touch pad [4] base 7311, thresh 73
I (3360) Touch pad: network -> set the blue light
I (3530) Touch pad: photo -> set the red light
I (3670) Touch pad: record -> shut down the light
I (6080) Touch pad: record -> shut down the light
I (6200) Touch pad: network -> set the blue light
I (6250) Touch pad: vol_down -> make the light darker:190
I (6290) Touch pad: photo -> set the red light
I (7410) Touch pad: record -> shut down the light
I (7580) Touch pad: network -> set the blue light
I (7610) Touch pad: vol_down -> make the light darker:190
I (7650) Touch pad: photo -> set the red light
I (7780) Touch pad: ERROR

I (7830) Touch pad: play -> set the green light
I (7850) Touch pad: vol_up -> make the light brighter:1

UPDATE after disconnecting display and audio boards touch pad board is working now
it is small chance its problem with USB power cable, even if power source is 2A


Also rare symptom:

ESP-ROM:esp32s2-rc4-20191025
Build:Oct 25 2019
rst:0x3 (RTC_SW_SYS_RST),boot:0x1d (SPI_FAST_FLASH_BOOT)
Saved PC:0x40055134
SPIWP:0xee
mode:DIO, clock div:1
load:0x3ffe8100,len:0x4
load:0x3ffe8104,len:0x1958
load:0x40050000,len:0x18a8
load:0x40054000,len:0x210c
entry 0x40050314
I (48) boot: ESP-IDF v4.2-dev-1575-ga3520970f-dirty 2nd stage bootloader
I (48) boot: compile time 12:58:53
I (48) boot: chip revision: 0
E (52) boot_comm: mismatch chip ID, expected 2, found 32768

EDIT 2 after removing audio board, camera is working properly now

EDIT 3 after assembling everything back i made final test, powered boards with laboratory power supply straight to 5V and GND pins; current draw is about 150mA (3.3V and 200mA) and image from camera is bad quality, after removing audio board, just display and camera (3.3V and 160-165mA) and good quality image

[ESP_LBB]

Hi chegewara，

First of all, thanks for your understanding.

1. the issue with RST button:
Because the strapping 45 and 46 are used in the camera and audio board, these two would interfere the RST function. This would be updated in V1.3 later.

2. The LCD screen in the kit is not a touch screen, we wanted to show a simple GUI and showed what the boards can do, but it seems to be very confusing with the GUI. We will update the demo too.
V1.2 is compatible with a touch screen, but in V1.3 we would remove it and simplify the design, as a touch screen requires too many pins. We might design another board with touch screen only.

3. For the camera display issue, it's caused by IO46, pulled-up in the audio board, which interferes the output of the camera. You can remove the audio board and try the camera function again, it should work fine. It's mentioned in the readme of camera demo.

4. For touch pad issue, you would need config the DIP switch, also mentioned in the readme.

Please feel free to share your ideas to help us make the board more powerful, thanks.

[chegewara]

3. For the camera display issue, it's caused by IO46, pulled-up in the audio board, which interferes the output of the camera. You can remove the audio board and try the camera function again, it should work fine. It's mentioned in the readme of camera demo.

4. For touch pad issue, you would need config the DIP switch, also mentioned in the readme.

Thanks for info, im not educated and i dont know Chinese, sorry.

Im happy its not problem with hardware just problem with design, i can live with that. Lucky for me audio board is least useful part at least for now.

Please feel free to share your ideas to help us make the board more powerful, thanks.

Just one thing for now. Since S2 is supporting dfu, it would be nice to have option similar to nrf52840 dongle to enter dfu mode with just 1 button press. Im sure its not hard to add and wont increase boards production too much.

Thanks for explanations and nice piece of hardware even if designed with few bugs

BTW if display is without touch screen option, then what for are dip switches on back? they are labeled like touch screen configuration

[chegewara]

I just found that kaluga board has hardware motion detector. I never saw something that smart before.
On board LED ws2812 data pin is connected to camera D3 pin. Almost always change in camera image is reflected in color changes of LED.

[chegewara]

I am studying kaluga schematics now and i can see that USB pins (19 and 20) should be connected to D+/D- to USB connector. I didnt test it with multimeter or any other equipment, but i can say that linux cant see it when i switch device to dfu mode, but when i connect wires straight to pins 19/20 i can see it thou. Just guessing now, but probably pins might be reverted.

I found that touch pad DIP switch is also controlling extension board pins. For example turn off pins 2, 3, and 7 on SW4 (any of them) causing my LCDis not working. Those are MISO, MOSI and D/C pins on LCD. Why?

[ESP_Alvin]

Hi chegewara,

We had some documentation about ESP32-S2-Kaluga kit on ESP-IDF master branch now, https://github.com/espressif/esp-idf/co ... efae4be59e, hope this helps. Thanks.

Alvin

[chegewara]

Hi chegewara,

We had some documentation about ESP32-S2-Kaluga kit on ESP-IDF master branch now, https://github.com/espressif/esp-idf/co ... efae4be59e, hope this helps. Thanks.

Alvin

Thanks, but i already seen it here:
https://docs.espressif.com/projects/esp ... 1-kit.html

and there is no info about conflict between camera and audio module, which is pointed in here:
https://github.com/espressif/esp-dev-ki ... 2%E9%99%A4
or conflict between touch pad extension and LCD.
Like i said, ive been studying schematics too:
https://dl.espressif.com/dl/schematics/ ... 00424A.pdf

page 4, 4C, we can see USB D+/D- connected to EXT19 and EXT20. Thus my question, why its not mounted as DFU device, which obviously works when i wire pins 19 and 20.

I have more strange behaviors. For example i have all touchpad DIP switched OFF, just for test. Guess what, touch pad is working. Readings are inaccurate (i can accept that, switches are OFF), but this also i causing that i cant use LCD, Like i mentioned, pins shared between LCD and touchpad, when switched OFF on DIP (any LCD pin) cause LCD being unusable.

Conclusion:
- i cant use touchpad with LCD, audio or camera,
- i cant use audio with camera or LCD,
- hopefully i can use camera with LCD,
- no simple option to use DFU, even having 2 USB connectors on board,
- i didnt check JTAG yet, but there is chance it works, because its using.

Honestly, its a waste of money for board, not even a beta, but v1.2. Im not saying about software support, because this is WIP and can be fixed, but hardware issues cant be solved. In addition espressif knew about at least few problems, but i dont see any annotation in official docs about it, which could let me make decision if i want to buy it and deal with those isssues or wait for next, maybe a better revision.

[meltdown03]

@chegewara, There are a couple more examples at https://github.com/xiongyumail/esp32-s2-hmi (need to change CAM_CLK pin to 33 in main.c files) and https://github.com/espressif/esp-dev-kits if you haven't found them yet. I had the same issue with terrible video quality until I found this thread and removed the Audio board.
I tried some of the ESP-ADF examples, but got only 2 of the the ESP32-S2 compatible ones to work. The speakers were clicking when nothing was playing too. Did you try any of them?