#no CIRCUITPY on Windows

1 messages · Page 1 of 1 (latest)

snow rune
#

let's start a thread

oak thicket
#

ok. I am here

#

No there is no disk unit on Windows Device Manager

#

Only COM4

#

pure serial

snow rune
#

do you have any other ESP32-S3 boards?

oak thicket
#

Yes

#

A bunch of them

#

Lets try another

snow rune
#

and they work fine on the same computer?

oak thicket
#

Not with circuitpython

#

This board has not suport yet

#

But this is not the problem.

snow rune
#

but do you have another ESP32-S3 board that does have a build available at circuitpython.org?

oak thicket
#

No

snow rune
#

so you only have the Xiao ESP32-S3 boards?

#

several?

oak thicket
#

I have Franzininho wifi, but is ESP32 S2

#

And I have XIAO ESP32 C3 also

snow rune
#

does that show up with CIRCUITPY?

oak thicket
#

Yes

snow rune
#

of course C3 is not going to have CIRCUITPY

#

since it doesn't have full uSB

oak thicket
#

But I can save files using IDE interface

#

And with S3, I can't

snow rune
#

Thonny uses the REPL invisibly to read and write files

oak thicket
#

But in windows only

#

In linux, works perfectly. Like in Raspberry Pi Pico

snow rune
#

have you forked the circuitpython repo? Could you push your additions for Xiao ESP32-S3 to your fork in a branch?

oak thicket
#

Yes

snow rune
#

so I can look at the code?

oak thicket
#

I've made two things: clone this repo and also clone adafruit repo and copy just the board folder.

#

With my Repo, the compiled version is 7.0.0

#

I don't understand why

snow rune
#

it is good to make changes like this on a branch instead of on main. Keep your main synchronized with upstream, and use a branch for changes. Then it's easy to submit a PR

#

but anyway, let me take a look

oak thicket
#

Sorry Danh, I'm not very good with Github. I usually save my experiences there, but I still don't really understand how to contribute. I'm working on this Seeed board because I really like their hardware and I can buy it here in Brazil at a good price.

#

I am also installed Circuitpython in another Xiao ESP32 S3. Same problem.

snow rune
oak thicket
#

Ok. Now I got it. clone original repo, create a new branch, start to make mess

snow rune
#

yes 🙂

#

i am looking at your board files now

oak thicket
#

As soon as we understand what is happening, i will clear and start again

snow rune
#

you could just delete your fork and start over. Or do a hard reset of main to match the adafruit repo

oak thicket
#

how can I make the hard reset?

snow rune
#

git reset --hard to a certain commit. But that's complicated. If you don't have other stuff in your fork, just deleting and starting over is easier

#

Do you know if there's a schematic for this board? I have not found one. Seeed either doesn't have them or buries the link.

oak thicket
#

No. I have it.

snow rune
#

do you mean you have a link? Could you paste it?

oak thicket
#

The pinout is in this excel file.

#

Seeed even announces that the board supports Circuitpython, but the person who made the version only uses a generic version of ESP32 S3. It does not comply with seeed compliance, pin nomenclature and does not support the camera and flash memory. That's why I decided to make it from scratch.

snow rune
#

have you loaded a generic ESP32-S3 build? Does it present CIRCUITPY on Windows?

oak thicket
#

Yes. I will make it again now

snow rune
#

do you mean load it or rebuild it?

oak thicket
#

This image opens Circuitpython drive

#

I've already tested before (and now too)

#

Do you think there is something wrong with flash config on my files?

snow rune
#

it is the same as the generic one above. it's not clear to me how the seeed board is configured

#

but if that one works, since it matches yours, then maybe it is a build problem. I can do a build locally with your board definition and you can try it.

#

are you using the UF2 or the .bin version of the generic, and how about for your own build?

oak thicket
#

the bin version

#

the UF2 drive wasn't show in any of my OSs

snow rune
#

and you've erased flash before loading it?

oak thicket
#

Yes

snow rune
#

did you just try the 9.1.1 espressif_esp32s3_devkitc_1_n8 version, or the 9.2.0-alpha.2350 version?

oak thicket
#

I am installing via Circuitpython download site

#

CIRCUITPY drive shows up

snow rune
#

there are two downloads in the right column 9.1.1 and 9.2.0-alpha.2350, which one did you use?

oak thicket
#

9.1.1

snow rune
#

I will build a 9.1.1 but with your board files. back in a few minutes

oak thicket
#

Ok. I need to get my childreen at school

#

Thank you danh

snow rune
#

i have some other ideas about clearing out USB stuff on Windows if this does not work.

oak thicket
#

Same problem here. But when I download or install that firmware on Circuitpython site, the CIRCUITPY drive appears.

oak thicket
#

I simply copy the same number of Espressif board to see if it works

snow rune
#

are you saying the builds I uploaded above are not working for you?

oak thicket
#

No

#

I realy think that is the problem.

snow rune
#

the builds I made are working or are not workign?

oak thicket
#

not work

#

same error

#

I've copyied the USB_VID and USB_PID from Espressif board.

snow rune
oak thicket
#

I've made it

snow rune
#

since you may have had problems with early builds of the board, Windows might be remembering the VID/PID

oak thicket
#

When you sugested before

#

Now it works.

#

Just changed the beggining of file USB_VID and USB_PID values.

snow rune
#

ok, so try the cleanup tool I mentioned, and then try with my build again, with the original USB_PID value you gave.

#

this we hope will make windows forget "hey, this VID/PID is a bad device"

oak thicket
#

Those USB_PID and USB_VID numbers are not from Seeed Studio. They didn't fill out that list and this is a long-standing request from the Adafruit people to them. I don't remember where I got those values ​​from before. I had started working with this board and then I got involved with another project and only got back to it now. I'm going to keep the Espressif numbers, which are the ones that worked here, and I'm re-addressing this problem with the people at Seeed Studio. I'll try again with your version as soon as I restart the machine.

snow rune
oak thicket
#

Ok.

oak thicket
#

Thank you!

snow rune
oak thicket
#

Were you able to greatly shorten the list of USB devices in the Cleanup tool?
Yes.
But for now, I need to understand camera support and other stuff. I've already told to Seeed people about it. I have two versions working.

snow rune
oak thicket
#

Still working on this, ok? There is a lot of wrong pins. I will test if camera works.

#

An then I will be back to Windows USB issues

oak thicket
snow rune
#

CIRCUITPY_AUDIOBUSIO = 1 // Mic Support?. Don't put a comment on the same line as a value in the .mk file. First of all that's a C style comment. Second of all the entire line is taken, as the definition from the = following

#

audiobusio is I2S, not PDMIn.

#

hold on for more...

oak thicket
#

ok

snow rune
#

Sorry, audiobusio does include PDMIn, but there is no espressif implementation. CIRCUITPY_AUDIOBUSIO_PDMIN has to be set and it isn't, because there's no impl.

oak thicket
#

Ok.

snow rune
#

There is basically no audio in on Espressif. You might be able to use an analog microphone and use analogbufio, but I don't think it would be satisfactory for streaming audio

oak thicket
#

Could I add something like that:
#include "shared-module/audiobusio/init.h"
in pins.c?

snow rune
#

Not sure what you mean. there is no shared-module/audiobusio. The PDMIn is port-specific on the ports that provide it.

oak thicket
#

I will dig into it.

oak thicket
#

In schematics, this Mic is directly connected to pins GPIO42 (CLK) and GPIO41(DATA).

#

There is no I2S hardware

snow rune
#

I think we would do I2SIn before or instead of PDMIn, since there is a peripheral.

#

I forget, what is your use case for a microphone?

oak thicket
#

I just to fully support the board. Xiao ESP32_S3 has this accessory with OV2640 camera and microphone. I've allready got the camera working

#

But not the microphone.

snow rune
#

Is that the mic that is on the accessory?

#

ok, yes, the I2S peripheral could also do PDMIn, but we don't have an implementation :/

oak thicket
#

I will try to add this: CIRCUITPY_ANALOGBUFIO = 1

snow rune
#

that needs an analog mic

oak thicket
#

Ok.

#

So I believe that, barring this implementation, I already have a working firmware for the card and the expansion. I had already removed that comment that was on github from my compiled version. I did tests using the camera and the display. Now I'm going to get my test files for the other modules and I believe that when Seeed does its part, we will have functional support for this board.

#

Thank you very much, Danh. For your patience.