ESP32 CAM Project Questions

Support Finding Parts
21

It appears that the upload has failed. The message you are seeing in the monitor is likely the previous sketch uploaded to the device. What is the board you have selected in the Tools \ Board menu? The tutorial does not set out this step in detail.

Connect your XIAO to your computer via the USB-C connection. Now, see if the Arduino IDE identifies it correctly. If it doesn’t (it will likely find another ESP32S3 board), then do a manual search for it; you should find “XIAO ESP32S3”. If you can’t find the XIAO, then you probably need to update your boards manager.

There is one more step required after you select the correct board. You need to set the IDE PSRAM option to “OPI PSRAM”. Do that by selecting the Tools menu, then scrolling down to PSRAM . If it is currently disabled, then select OPI PSRAM .

The ‘search’ referred to here is in one of the ESP 32 sections of the Boards menu item. The settings changes that are mentioned are made in the tools menu after the correct board has been selected. The error you are seeing is the likely result of not selecting the correct board and not adjusting the settings as indicated. There could be other reasons.

If you reset the device the sketch should start. You could also just cycle the power.

1 Like
22

Jeff,

They are as per the document, i believe i have followed it…

Please see the screenshots attached…

esp32_type
esp32_type682×618 39.2 KB

PSRAM_Enbaled
PSRAM_Enbaled713×779 38.8 KB

23

In that case the next best guess is that the device is not what you have identified it as. Do you have a link to the exact device you have purchased?

If the upload succeeded then the problem occurs when the sketch runs. To identify what might be an upload issue separately from a problem with the sketch, when the upload is complete delete everything from the monitor widow then press Reset to start the sketch, and copy and paste the monitor content into a forum response.

1 Like
24

Thanks for all your help Jeff. I am really invested in sorting this out so appreciate all your help.

Is there a way to PM on here by chance?

To answer your questions:

Seeed Studio XIAO ESP32S3 Sense
SKU: SS113991115

Sketch uses 2938653 bytes (87%) of program storage space. Maximum is 3342336 bytes.
Global variables use 74084 bytes (22%) of dynamic memory, leaving 253596 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.5.1
Serial port COM3
Connecting…
Chip is ESP32-S3 (revision v0.2)
Features: WiFi, BLE
Crystal is 40MHz
MAC: 84:fc:e6:6a:ce:20
Uploading stub…
Running stub…
Stub running…
Changing baud rate to 921600
Changed.
Configuring flash size…
Flash will be erased from 0x00000000 to 0x00003fff…
Flash will be erased from 0x00008000 to 0x00008fff…
Flash will be erased from 0x0000e000 to 0x0000ffff…
Flash will be erased from 0x00010000 to 0x002ddfff…
Compressed 15104 bytes to 10399…
Writing at 0x00000000… (100 %)
Wrote 15104 bytes (10399 compressed) at 0x00000000 in 0.3 seconds (effective 476.7 kbit/s)…
Hash of data verified.
Compressed 3072 bytes to 114…
Writing at 0x00008000… (100 %)
Wrote 3072 bytes (114 compressed) at 0x00008000 in 0.1 seconds (effective 489.5 kbit/s)…
Hash of data verified.
Compressed 8192 bytes to 47…
Writing at 0x0000e000… (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 691.4 kbit/s)…
Hash of data verified.
Compressed 2939024 bytes to 2065370…
Writing at 0x00010000… (0 %)
Writing at 0x00014e4d… (1 %)
Writing at 0x0001a698… (2 %)
Writing at 0x00025d6e… (3 %)
Writing at 0x0002bc7d… (3 %)
Writing at 0x00030055… (4 %)
Writing at 0x0003446b… (5 %)
Writing at 0x00039342… (6 %)
Writing at 0x0003dfaf… (7 %)
Writing at 0x00042b63… (7 %)
Writing at 0x00047724… (8 %)
Writing at 0x0004c4a1… (9 %)
Writing at 0x00050f47… (10 %)
Writing at 0x0005534b… (11 %)
Writing at 0x0005978d… (11 %)
Writing at 0x0005db0f… (12 %)
Writing at 0x00061d0a… (13 %)
Writing at 0x0006614c… (14 %)
Writing at 0x0006a49e… (14 %)
Writing at 0x0006fb63… (15 %)
Writing at 0x0007439a… (16 %)
Writing at 0x00078d0b… (17 %)
Writing at 0x0007d735… (18 %)
Writing at 0x0008204d… (18 %)
Writing at 0x00086924… (19 %)
Writing at 0x0008b1b2… (20 %)
Writing at 0x0008fad9… (21 %)
Writing at 0x00094425… (22 %)
Writing at 0x00098cf6… (22 %)
Writing at 0x0009d5e0… (23 %)
Writing at 0x000a1f17… (24 %)
Writing at 0x000a6844… (25 %)
Writing at 0x000ab1b5… (25 %)
Writing at 0x000b0251… (26 %)
Writing at 0x000b52ae… (27 %)
Writing at 0x000b9a25… (28 %)
Writing at 0x000be251… (29 %)
Writing at 0x000c29f8… (29 %)
Writing at 0x000c72e7… (30 %)
Writing at 0x000cbca2… (31 %)
Writing at 0x000d03fc… (32 %)
Writing at 0x000d4b28… (33 %)
Writing at 0x000d9472… (33 %)
Writing at 0x000ddd7b… (34 %)
Writing at 0x000e24a3… (35 %)
Writing at 0x000e6bed… (36 %)
Writing at 0x000eb627… (37 %)
Writing at 0x000f00bb… (37 %)
Writing at 0x000f4ac1… (38 %)
Writing at 0x000f932d… (39 %)
Writing at 0x000fdb22… (40 %)
Writing at 0x0010248c… (40 %)
Writing at 0x00106e3d… (41 %)
Writing at 0x0010b835… (42 %)
Writing at 0x0011015a… (43 %)
Writing at 0x00114a42… (44 %)
Writing at 0x001192b4… (44 %)
Writing at 0x0011dc2b… (45 %)
Writing at 0x00122602… (46 %)
Writing at 0x00126db7… (47 %)
Writing at 0x0012b649… (48 %)
Writing at 0x00130003… (48 %)
Writing at 0x0013484d… (49 %)
Writing at 0x00138f3c… (50 %)
Writing at 0x0013d731… (51 %)
Writing at 0x001420d6… (51 %)
Writing at 0x0014689b… (52 %)
Writing at 0x0014afa6… (53 %)
Writing at 0x0014f89b… (54 %)
Writing at 0x00154299… (55 %)
Writing at 0x00158b39… (55 %)
Writing at 0x0015d300… (56 %)
Writing at 0x00161cf7… (57 %)
Writing at 0x00166751… (58 %)
Writing at 0x0016aedd… (59 %)
Writing at 0x0016f6e5… (59 %)
Writing at 0x00173ff9… (60 %)
Writing at 0x00178863… (61 %)
Writing at 0x0017d0a7… (62 %)
Writing at 0x00181788… (62 %)
Writing at 0x00185ea1… (63 %)
Writing at 0x0018a5fe… (64 %)
Writing at 0x0018ed59… (65 %)
Writing at 0x00193654… (66 %)
Writing at 0x0019afaf… (66 %)
Writing at 0x001af164… (67 %)
Writing at 0x001b578e… (68 %)
Writing at 0x001baf72… (69 %)
Writing at 0x001c05b3… (70 %)
Writing at 0x001c57fc… (70 %)
Writing at 0x001ca9c2… (71 %)
Writing at 0x001cf996… (72 %)
Writing at 0x001d49db… (73 %)
Writing at 0x001d9861… (74 %)
Writing at 0x001deab2… (74 %)
Writing at 0x001e488f… (75 %)
Writing at 0x001eb1ec… (76 %)
Writing at 0x001f2477… (77 %)
Writing at 0x001fa0cb… (77 %)
Writing at 0x00201932… (78 %)
Writing at 0x00207902… (79 %)
Writing at 0x0020d835… (80 %)
Writing at 0x0022e07d… (81 %)
Writing at 0x0023363a… (81 %)
Writing at 0x002386ea… (82 %)
Writing at 0x0023da12… (83 %)
Writing at 0x00243916… (84 %)
Writing at 0x00248693… (85 %)
Writing at 0x0024d72f… (85 %)
Writing at 0x002526a1… (86 %)
Writing at 0x00257b3a… (87 %)
Writing at 0x0025cf4f… (88 %)
Writing at 0x00262817… (88 %)
Writing at 0x0026821e… (89 %)
Writing at 0x0026e767… (90 %)
Writing at 0x00276687… (91 %)
Writing at 0x0027e82c… (92 %)
Writing at 0x0028683d… (92 %)
Writing at 0x0028c95c… (93 %)
Writing at 0x00294b52… (94 %)
Writing at 0x0029b3af… (95 %)
Writing at 0x002acc04… (96 %)
Writing at 0x002c3b0b… (96 %)
Writing at 0x002cc6ca… (97 %)
Writing at 0x002d1ee2… (98 %)
Writing at 0x002d73f9… (99 %)
Writing at 0x002dd2a3… (100 %)
Wrote 2939024 bytes (2065370 compressed) at 0x00010000 in 22.8 seconds (effective 1029.8 kbit/s)…
Hash of data verified.

Leaving…
Hard resetting via RTS pin…

Does this help?

25

That’s the IDE log (it clearly indicates a successful upload). It also indicates that the IDE has identified the module correctly.

If you now clear whatever is in the monitor window and press Reset, what do you get?

If it’s the same as you already posted then the thing to do is to add plenty of Serial.println(“…”); lines to your code with text that identifies the part of the code that has executed. You are trying to find out how far it gets before it spits the dummy. I think that “No core dump partition found!” means that it tried to create a record of the state of the CPU at the point of failure but could find anywhere to put it. It doesn’t matter that it couldn’t create the record because it is unlikely to be helpful, but knowing where in the code it occurs will be important.

1 Like
26

Pressing the reset button doesnt do anything. I tried a few times now.

27

Where did you add the first 'Serial.println(“…”); statement? If nothing appears in the monitor window then the problem is occurring before that first statement. At what point in the process do you get the message

E (518) esp_core_dump_flash: No core dump partition found!

Now that you have confirmed that the upload is working you should confirm that you can run a simpler example, such as Blink?

1 Like
28

ok i killed the arduino IDE program, connected the cam to the usb port on the computer and then opened the IDE. This time it seems to pick it up…

image
image1044×377 16.5 KB

Then i did an upload of the current program:
Sketch uses 2938653 bytes (87%) of program storage space. Maximum is 3342336 bytes.
Global variables use 74084 bytes (22%) of dynamic memory, leaving 253596 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.5.1
Serial port COM3
Connecting…
Chip is ESP32-S3 (revision v0.2)
Features: WiFi, BLE
Crystal is 40MHz
MAC: 84:fc:e6:6a:ce:20
Uploading stub…
Running stub…
Stub running…
Changing baud rate to 921600
Changed.
Configuring flash size…
Flash will be erased from 0x00000000 to 0x00003fff…
Flash will be erased from 0x00008000 to 0x00008fff…
Flash will be erased from 0x0000e000 to 0x0000ffff…
Flash will be erased from 0x00010000 to 0x002ddfff…
Compressed 15104 bytes to 10399…
Writing at 0x00000000… (100 %)
Wrote 15104 bytes (10399 compressed) at 0x00000000 in 0.3 seconds (effective 480.8 kbit/s)…
Hash of data verified.
Compressed 3072 bytes to 114…
Writing at 0x00008000… (100 %)
Wrote 3072 bytes (114 compressed) at 0x00008000 in 0.0 seconds (effective 532.8 kbit/s)…
Hash of data verified.
Compressed 8192 bytes to 47…
Writing at 0x0000e000… (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 696.6 kbit/s)…
Hash of data verified.
Compressed 2939024 bytes to 2065370…
Writing at 0x00010000… (0 %)
Writing at 0x00014e4d… (1 %)
Writing at 0x0001a698… (2 %)
Writing at 0x00025d6e… (3 %)
Writing at 0x0002bc7d… (3 %)
Writing at 0x00030055… (4 %)
Writing at 0x0003446b… (5 %)
Writing at 0x00039342… (6 %)
Writing at 0x0003dfaf… (7 %)
Writing at 0x00042b63… (7 %)
Writing at 0x00047724… (8 %)
Writing at 0x0004c4a1… (9 %)
Writing at 0x00050f47… (10 %)
Writing at 0x0005534b… (11 %)
Writing at 0x0005978d… (11 %)
Writing at 0x0005db0f… (12 %)
Writing at 0x00061d0a… (13 %)
Writing at 0x0006614c… (14 %)
Writing at 0x0006a49e… (14 %)
Writing at 0x0006fb63… (15 %)
Writing at 0x0007439a… (16 %)
Writing at 0x00078d0b… (17 %)
Writing at 0x0007d735… (18 %)
Writing at 0x0008204d… (18 %)
Writing at 0x00086924… (19 %)
Writing at 0x0008b1b2… (20 %)
Writing at 0x0008fad9… (21 %)
Writing at 0x00094425… (22 %)
Writing at 0x00098cf6… (22 %)
Writing at 0x0009d5e0… (23 %)
Writing at 0x000a1f17… (24 %)
Writing at 0x000a6844… (25 %)
Writing at 0x000ab1b5… (25 %)
Writing at 0x000b0251… (26 %)
Writing at 0x000b52ae… (27 %)
Writing at 0x000b9a25… (28 %)
Writing at 0x000be251… (29 %)
Writing at 0x000c29f8… (29 %)
Writing at 0x000c72e7… (30 %)
Writing at 0x000cbca2… (31 %)
Writing at 0x000d03fc… (32 %)
Writing at 0x000d4b28… (33 %)
Writing at 0x000d9472… (33 %)
Writing at 0x000ddd7b… (34 %)
Writing at 0x000e24a3… (35 %)
Writing at 0x000e6bed… (36 %)
Writing at 0x000eb627… (37 %)
Writing at 0x000f00bb… (37 %)
Writing at 0x000f4ac1… (38 %)
Writing at 0x000f932d… (39 %)
Writing at 0x000fdb22… (40 %)
Writing at 0x0010248c… (40 %)
Writing at 0x00106e3d… (41 %)
Writing at 0x0010b835… (42 %)
Writing at 0x0011015a… (43 %)
Writing at 0x00114a42… (44 %)
Writing at 0x001192b4… (44 %)
Writing at 0x0011dc2b… (45 %)
Writing at 0x00122602… (46 %)
Writing at 0x00126db7… (47 %)
Writing at 0x0012b649… (48 %)
Writing at 0x00130003… (48 %)
Writing at 0x0013484d… (49 %)
Writing at 0x00138f3c… (50 %)
Writing at 0x0013d731… (51 %)
Writing at 0x001420d6… (51 %)
Writing at 0x0014689b… (52 %)
Writing at 0x0014afa6… (53 %)
Writing at 0x0014f89b… (54 %)
Writing at 0x00154299… (55 %)
Writing at 0x00158b39… (55 %)
Writing at 0x0015d300… (56 %)
Writing at 0x00161cf7… (57 %)
Writing at 0x00166751… (58 %)
Writing at 0x0016aedd… (59 %)
Writing at 0x0016f6e5… (59 %)
Writing at 0x00173ff9… (60 %)
Writing at 0x00178863… (61 %)
Writing at 0x0017d0a7… (62 %)
Writing at 0x00181788… (62 %)
Writing at 0x00185ea1… (63 %)
Writing at 0x0018a5fe… (64 %)
Writing at 0x0018ed59… (65 %)
Writing at 0x00193654… (66 %)
Writing at 0x0019afaf… (66 %)
Writing at 0x001af164… (67 %)
Writing at 0x001b578e… (68 %)
Writing at 0x001baf72… (69 %)
Writing at 0x001c05b3… (70 %)
Writing at 0x001c57fc… (70 %)
Writing at 0x001ca9c2… (71 %)
Writing at 0x001cf996… (72 %)
Writing at 0x001d49db… (73 %)
Writing at 0x001d9861… (74 %)
Writing at 0x001deab2… (74 %)
Writing at 0x001e488f… (75 %)
Writing at 0x001eb1ec… (76 %)
Writing at 0x001f2477… (77 %)
Writing at 0x001fa0cb… (77 %)
Writing at 0x00201932… (78 %)
Writing at 0x00207902… (79 %)
Writing at 0x0020d835… (80 %)
Writing at 0x0022e07d… (81 %)
Writing at 0x0023363a… (81 %)
Writing at 0x002386ea… (82 %)
Writing at 0x0023da12… (83 %)
Writing at 0x00243916… (84 %)
Writing at 0x00248693… (85 %)
Writing at 0x0024d72f… (85 %)
Writing at 0x002526a1… (86 %)
Writing at 0x00257b3a… (87 %)
Writing at 0x0025cf4f… (88 %)
Writing at 0x00262817… (88 %)
Writing at 0x0026821e… (89 %)
Writing at 0x0026e767… (90 %)
Writing at 0x00276687… (91 %)
Writing at 0x0027e82c… (92 %)
Writing at 0x0028683d… (92 %)
Writing at 0x0028c95c… (93 %)
Writing at 0x00294b52… (94 %)
Writing at 0x0029b3af… (95 %)
Writing at 0x002acc04… (96 %)
Writing at 0x002c3b0b… (96 %)
Writing at 0x002cc6ca… (97 %)
Writing at 0x002d1ee2… (98 %)
Writing at 0x002d73f9… (99 %)
Writing at 0x002dd2a3… (100 %)

Then i reset the board…

ESP-ROM:esp32s3-20210327

Build:Mar 27 2021

rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)

Saved PC:0x4210ef2a

SPIWP:0xee

mode:DIO, clock div:1

load:0x3fce3808,len:0x44c

load:0x403c9700,len:0xbd8

load:0x403cc700,len:0x2a80

entry 0x403c98d0

E (518) esp_core_dump_flash: No core dump partition found!

E (519) esp_core_dump_flash: No core dump partition found!

…

Looks like it is writing dots on the screen

Not sure what else to do…??

29

Been reading a bit and a lot of ppl are having very similar errors. Some are mentioning to create/modify the core dump partition in the partitions file. This is my current partitions file…

Name, Type, SubType, Offset, Size, Flags

nvs, data, nvs, 0x9000, 0x5000,
otadata, data, ota, 0xe000, 0x2000,
app0, app, ota_0, 0x10000, 0x3d0000,
fr, data, , 0x3e0000, 0x20000,

Does this need to be modified?

so modified the line to have coredumpdata
coredump, data, coredump, 0x400000, 0x100,

and now after booting i get this with NO coredump error…

ESP-ROM:esp32s3-20210327

Build:Mar 27 2021

rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)

Saved PC:0x4210ef2a

SPIWP:0xee

mode:DIO, clock div:1

load:0x3fce3808,len:0x3ac

load:0x403c9700,len:0x9a8

load:0x403cc700,len:0x2920

entry 0x403c98b8

…

The freaking thing is still giving me dots and not a webserver IP… what next… :confused:

30

I had assumed that the failure to find a core dump partition was a problem following a crash (that’s when a core dump occurs) but it appears from that screen shot that it is checking for the existence of the partition without any crash having occurred. So the problem is likely in the board configuration, and that’s something I have never fiddled with.

I would not recommend simply changing the partitions file, as the arrangement depends on all the partition sizes and locations. The error message does not indicate a problem with the new file, but it might appear as an entirely different problem.

For the partition choices in Tools, OTA is optional, but you should include spiffs (not ffat). But there is no mention of which ones include core dump and which don’t; both Minimal and Huge should have a core dun\mp partition. In fact, you could try all the 4Mb and less options - the error might change but it won’t damage anything.

There are several specific suggestions for adjusting the configuration here:
ESP32-CAM esp_core_dump_flash - Using Arduino / Microcontrollers - Arduino Forum

Just in case, it would be worth trying again with a properly formatted SD card inserted: the sketch does not require it but perhaps it is still expected.

What was the result when you tried a simple sketch such as blink? Can you get any print statement to work, for instance if you place one immediately after the ‘Serial Begin(115200);’ line?

Edit/
I’m now thinking that the core dump partition is a red herring. I don’t think it is required and the message is just a warning that can be ignored.

I would recommend concentrating on getting a minimal sketch to run, such as blink, or just printing messages to console. Set the board partition scheme to minimal to rule out any memory problems. Set debug level to Info or higher to see if additional useful information is provided.
/Edit

1 Like
31

Hi Jeff,

Yes, up to that section.

  1. Model - Yes
  2. Yes ddouble checked
  3. Yes, it tells me it has
  4. How do i know?
    Right will reset it upon my return
32

Sorry I was away from this. Had couple of deadlines at work and then had a small holiday to wind down the year. Back now and plan to get back to this.

Hope you all had a great Christmas!

Talk soon.

33

The correct message will appear in the console window. The one you are seeing now is not part of the code you are uploading. The message will be “Camera Ready! Use 'http://” followed by the URL that has been allocated, or an error message is something went wrong.

1 Like
34

Hi Jeff,

I seem to get no error msg. It detects the camera on COM3 and that is about it; starts writing dots on the screen.

The camera module is warm; it had red light on when booting up initially.

I am not sure what to do. I really want to get this working now!

…ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x4210ef2a
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x3ac
load:0x403c9700,len:0x9a8
load:0x403cc700,len:0x2920
entry 0x403c98b8

esp32_screen
esp32_screen1119×1398 70.1 KB

35

Unfortunately I cannot exactly replicate your setup, but I can show you what I get when I load and execute a simple blink sketch. It indicates that your upload s working correctly.

int flashPin = 4;

void setup() {
  pinMode(flashPin, OUTPUT);
}

void loop() {
    digitalWrite(flashPin, HIGH);
    delay(1000);
    digitalWrite(flashPin, LOW);
    delay(1000);
}

esptool.py v4.5.1
Serial port COM6
Connecting.....
Chip is ESP32-D0WDQ6 (revision v1.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 0c:b8:15:f6:b9:c8
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x00050fff...
Compressed 18992 bytes to 13110...
Writing at 0x00001000... (100 %)
Wrote 18992 bytes (13110 compressed) at 0x00001000 in 0.5 seconds (effective 291.5 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 146...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (146 compressed) at 0x00008000 in 0.1 seconds (effective 295.6 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 486.0 kbit/s)...
Hash of data verified.
Compressed 262704 bytes to 145841...
Writing at 0x00010000... (11 %)
Writing at 0x0001c65e... (22 %)
Writing at 0x00024e20... (33 %)
Writing at 0x0002a02d... (44 %)
Writing at 0x0002f42a... (55 %)
Writing at 0x00035004... (66 %)
Writing at 0x0003f452... (77 %)
Writing at 0x00045b40... (88 %)
Writing at 0x0004b079... (100 %)
Wrote 262704 bytes (145841 compressed) at 0x00010000 in 2.6 seconds (effective 822.6 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

Note that after uploading I don’t reset the board - I disconnect and then reconnect it. I am using the ESP32-CAM-MB Adapter mentioned here. That means I have to hold ‘IO0’ while connecting the ESP in order to put it into programming mode. Your process may differ, but as the upload is working that’s not an issue. But there might be something different in your board that means it doesn’t re-start in sketch mode when you reconnect. That’s all I can think of, although there’s no indication of any such feature in the documentation.

36

Thanks Jeff.

I did both resetting and another time simply unplugging and replugging the usb cable. Same thing I get both times; dots get printed on the screen.

Thank you for your help so far.

37

I wonder if any of the guys from the main site is actually monitoring this and if they could replicate the same steps on a new board and see what they get?

I mean i don’t really know what else to do…

38

I feel for you here - I can see how frustrating it is to have such little certainty about the paths forward for your project. This is the less attractive side of doing projects :frowning:

Have you ever seen a successful script load onto the xiao? eg. the blink sketch from the guide?
If not I wonder if there is something not quite right with the board?

Rest assured we do monitor the forums diligently and try to be as helpful as we can in a way that’s sustainable. It’s just not sustainable for us to replicate forum users projects to attempt troubleshooting though.

1 Like
39

Right ok. So i have successfully managed to upload the Blink program and got it to have the continuous orange LED blinking on my ESP32.

Phew! So ok, the ESP itself is working. Step 1 done.

Thanks for your help so far.

Now then…

1 Like
40

Great, we’ve split test the problem and know that we can upload some code. Now let’s find the point where things break down.

I’m assuming we’re already past the troubleshooting section that covers problems uploading to the board

Presumably you’ve used all the same board settings for both scripts. We have a script that works (blink) and a script that doesn’t (fully-fledged camera operations). Are there other examples that you can upload to build up the functionality?