nanoCLR task not start correctly on ESP32-S3!

[omidg2]

Target name(s)

ESP32-S3

Firmware version

No response

Was working before? On which version?

No response

Device capabilities

No response

Description

I use ESP32-S3, I flash nanoframework image to it by this command line:
nanoff --masserase --update --target ESP32_S3_BLE --serialport COM5
the nanoframework image was program on ESP32-S3 correctly as you can see on the first attached screen shot...

but when I connect my device to putty with baudrate 115200 and start it, it seems nanoCLR not start correctly, as you can see
in second screen shot

I use nanoFramework on other version of ESP32 like ESP32-WROOM-32 and it works correctly

How to reproduce

No response

Expected behaviour

nanoCLR task start correctly and we can see the device in Visual Studio Device Explorer...

Screenshots

Aditional information

No response

[alberk8]

Which ESP32 S3 do you have? From which manufacturer, make and model?

[omidg2]

Which ESP32 S3 do you have? From which manufacturer, make and model?

This is full part number: ESP32-S3-WROOM-1U-N4
as I mentioned, nanoFramework Image pragrammed correctly, (ESP32_S3_BLE 1.12.0.47)
but device not found in Visual Studio 22 Device Explorer, I check the problem and it seems nanoCLR task not start....

[alberk8]

Looks good and based on the screen capture it looks like the boot process is good. Are you sure that there are no other serial terminal app is opened when VS 2022 you plug in the ESP32 S3 and view it in Device Explorer? Make sure that the Device Watcher is enabled in Device Explorer.

[omidg2]

No, not good, if you see second screen capture, you can see that nanoCLR not started correctly, it stops in line
I (304) boot: Disabling RNG early entropy source ...
a good start up should be something like this screen capture:

this screen capture is from another board which works correctly,
as you see here, many lines such as
I (415) cpu_start: Multicore app

and lines after that should be exist,

[alberk8]

If your S3 has 2 usb-c port then VS will only detect it on the other USB port (usually the left hand side usb c).

[omidg2]

Dear Alber, I do not use USB, I use USART 0 on pin 36 and pin 37 of module, as you can see in the picture below:

my communications to module, fully are done through this USART port ...

[alberk8]

The current S3 firmware expect to communicated with VS 2022 via USB CDC, you could compile firmware with CDC off.

[omidg2]

It means if I connect my PC via USB port to IO19 and IO20 of module, like below diagram, it might work properly?

[alberk8]

most likely will work

[omidg2]

Thank you alberk8, I tested it and it didn't work, I'm probably doing something wrong somewhere,

[alberk8]

Check if you have the D+ and D- connected properly.

[omidg2]

I checked it ...the connection is OK, but not detected by windows...