https://espressif-docs.readthedocs-hosted.com/projects/esp-adf/en/latest/design-guide/dev-boards/get-started-esp32-lyrat.html has the documentation for the board and links to the ES8388 pdf as well

I found this user guide for the ES8388. (edit: forgot to add the link. https://dl.radxa.com/rock2/docs/hw/ds/ES8388%20user%20Guide.pdf ) Without too much confidence, I would say that the ADC is powered down by default, and would need to be enabled by setting the corresponding bits in register 3. (Page 16). You can see some typical startup sequences on pages 20+.

If you look at page 26, section 10.3, it looks like setting the registers shouldn't be too hard. I'm not really familiar with all of the terminology, but there are only a few terms that would need some googling. Most of the registers could just be set directly according to the flow of that page.

If you want to try to set the registers, have a look at this tutorial that explains how to write a driver: https://docs.toit.io/peripherals/drivers/sparkfun_joystick

the ESP-ADF does a lot of behind the scenes things as part of their audio-passthru example https://github.com/espressif/esp-adf/blob/master/examples/audio_processing/pipeline_passthru/main/passthru.c but I couldn't tell how much of it was C boilerplate that is abstracted away by some of toit niceties

And here seems to be the start routine for the chip: https://github.com/espressif/esp-adf/blob/master/components/audio_hal/driver/es8388/es8388.c#L154

Probably need the init configuration first: https://github.com/espressif/esp-adf/blob/master/components/audio_hal/driver/es8388/es8388.c#L263

It's bed time for me now, but I will check tomorrow again. So just keep posting and I (and probably Mikkel) will respond tomorrow.

I'm not sure why but my i2c.Bus scan is returning 16 (0x10) when according to the documentation, the ES8388 should be on 0x20

looks like the documentation is wrong.. if i try to read from 0x20 I get I2C read errors, but on 0x10 I seem to get register defaults that resemble that of an ES8388

Personally I try to go with datasheet and application notes first, and then fall back to other implementations when something isn't working as expected. It depends a bit in on what you want to get out of it. By starting with datasheet and application notes you tend to get a better understanding. With the code you often are faster in getting it to work.

And congratulations. You seem to be doing quite well for something who is green in programming hardware.

Just curious: which timezone are you in?

Unfortunately I'm somewhat stuck again.. back to getting zeroes out of the i2s bus... here is what my driver looks like: https://github.com/c22/toit-scratch/blob/main/ES8388_driver.toit and here is me trying to read out of the ADC using the driver: https://github.com/c22/toit-scratch/blob/main/basic-audio.toit

Seems like I didn't attach the user-guide I found... https://dl.radxa.com/rock2/docs/hw/ds/ES8388%20user%20Guide.pdf

and tbh, this was one of the areas I would need to google a bit, to know exactly what it means and how it is set up on the board.

(possibly taking some hints from the existing code).

A lost resort is also to modify the arduino code and add `printf`s around the i2c calls to see which calls are made. It's a bit annoying to switch IDEs, and setups, so I tend to avoid it. Not sure if I should. It would probably speed up debugging these things.

fwiw, it's a rewarding experience. After writing drivers I often feel like I'm a super expert. (Probably shouldn't but let me have that 😉

Fiddling with NFC boards (mfrc-522 and similar) right now, and the things I learned...

I will order an es8388 now, but since I usually order from aliexpress, it will take many weeks before it will arrive.

I did actually fiddle with a sensor that was located in South Africa

The system is set up in a way that `print`s don't need to go through the serial port, and we have plans to change Jaguar so it uses that feature.

If the device was publicly accessible (public IP), Jaguar could then actually do what you suggested.

(

jag scan <ip>

avoids the udp broadcast scanning and sets the target to the given IP)

I imagine it's not intended for that just yet, but it's doable

And tbh, I wouldn't have the time to look into it right now anyway. But it's a cool feature that already came in handy multiple times (on v1).

still only getting zeroes, I think I am at the point where I probably need to compare register by register to the reference driver and copy everything over until it works, even if the values don't really make sense to me

I just realised when adding logging that I was setting slave mode on the wrong register 🤦‍♂️

we have all been there...

That's definitely weird.

I would start by adding a print into the constructor and into

on

.

is your repository up to date?

https://github.com/c22/toit-scratch/blob/main/ES8388_driver.toit updated

The

print

issue seems to have been a fluke, so I didn't expect to see anything bad...

In case it's useful, I've transcribed the initialization of the driver here https://github.com/thaaraak/es8388/blob/master/src/es8388.cpp#L84-L120 into "plain english", this is mainly just for my own benefit 🙂

// https://github.com/thaaraak/es8388/blob/master/src/es8388.cpp#L84-L120

Writing 0x04 to register 25    // 0x04 mute/0x00 unmute&ramp;DAC unmute and disabled digital volume control soft ramp
Writing 0x50 to register 1    // normal all and power up all
Writing 0x00 to register 2
Writing 0x00 to register 8    // CODEC IN I2S SLAVE MODE
Writing 0xC0 to register 4    // disable DAC and disable Lout/Rout/1/2
Writing 0x12 to register 0    // Enfr=0,Play&Record Mode,(0x17-both of mic&paly)
Writing 0x18 to register 23    // 1a 0x18:16bit iis , 0x00:24
Writing 0x02 to register 24    // DACFsMode,SINGLE SPEED; DACFsRatio,256
Writing 0x00 to register 38    // 0x00 audio on LIN1&RIN1,  0x09 LIN2&RIN2
Writing 0x90 to register 39    // only left DAC to left mixer enable 0db
Writing 0x90 to register 42    // only right DAC to right mixer enable 0db
Writing 0x80 to register 43    // set internal ADC and DAC use the same LRCK clock, ADC LRCK as internal LRCK
Writing 0x00 to register 45    // vroi=0
Special handling for ADC/DAC volume on registers 16, 17, 26 and 27    // 0db
Special handling for enabled outputs on register 4
Writing 0xFF to register 3
Writing 0x11 to register 9    // MIC Left and Right channel PGA gain
Special handling for enabled inputs on register 10
Writing 0x02 to register 11
Writing 0x0d to register 12    // Left/Right data, Left/Right justified mode, Bits length, I2S format
Writing 0x02 to register 13    //ADCFsMode,singel SPEED,RATIO=256

//ALC for Microphone
Special handling for ADC/DAC volume on registers 16, 17, 26 and 27    // 0db
Writing 0x09 to register 3    //Power on ADC, Enable LIN&RIN, Power off MICBIAS, set int1lp to low power mode

my driver does a lot less, but I am trying to boil it down to only what's needed.. looking at this, perhaps setting volume levels is relevant

I changed tactics and tried to set the exact same register values (or as close as possible) as thaaraak's code above, but still getting zeroes out of the I2S bus 😞

Initalizing ES8388 codec...
Writing 0x04 to register 25
Writing 0x50 to register 1
Writing 0x00 to register 2
Writing 0x00 to register 8
Writing 0xC0 to register 4
Writing 0x12 to register 0
Writing 0x18 to register 23
Writing 0x02 to register 24
Writing 0x00 to register 38
Writing 0x90 to register 39
Writing 0x90 to register 42
Writing 0x80 to register 43
Writing 0x00 to register 45
Writing 0x00 to register 16
Writing 0x00 to register 17
Writing 0x00 to register 26
Writing 0x00 to register 27
Writing 0x3F to register 4
Writing 0xFF to register 3
Writing 0x11 to register 9
Writing 0x00 to register 10
Writing 0x02 to register 11
Writing 0x0D to register 12
Writing 0x02 to register 13
Writing 0x09 to register 3

Here's the code for that https://github.com/c22/toit-scratch/blob/main/ES8388_driver_brute.toit Back to being out of ideas 😦

Also, I tend to not care to much about the initialization sequence until I have audio through the system. The initialization mostly is to avoid clicks and stuff in the beginning, so not important for proto types. I also tend to just write absolute values (not read and do the bitwise opertations) and then when I am done initializing, I read out all registers and verify by hand that it looks ok. There is a %b to give you bit patterns.

and yeah the brute force driver is basically just writing the values directly to the register

I think that I might have something to do with the i2s initialization wrong, perhaps..

So, the I2S on the codec in slave mode needs only to set the CODEC in slave mode and set the word length.

i did try that 😅

Actually, reading the ES8388 datasheet it needs the MCLK even in slave mode.

wow.. you're a mad scientist! it worked!

I'm just happy to see something other than zeroes!

Writing 32 bytes
#[0xf9, 0xfe, 0x51, 0xff, 0xf5, 0xfe, 0x51, 0xff, 0xf7, 0xfe, 0x59, 0xff, 0xfd, 0xfe, 0x4f, 0xff, 0xf9, 0xfe, 0x4d, 0xff, 0x05, 0xff, 0x51, 0xff, 0xf9, 0xfe, 0x5b, 0xff, 0xfd, 0xfe, 0x55, 0xff]

My bad, because the CODEC we use does not need the MCLK, but uses just the BCLK. It is apparently different from codec to codec.

totally fine I had a feeling it was something so stupidly obvious that I must be missing...

I will work on it a bit more this week and hopefully share something more polished soon