Hello klaetze,

This is awesome! Because I remember there were issues to reach 2Msps, so finally they fix that situation.

Great!

Best regards.
Gianluca.

Hello Klaetze,

Great!
I haven't answer you yet because I haven't any time to test your fw. I'm glad you solved your problem.
Did you reach 2Msps?

Regards,

Gianluca.

Hello klaetze,

try to put ".use_apll = false," and also, which kind of values are you supposed to read?
To do some test, you can try to set up a DAC output and bring it (by a wire for example) to che ADC pin and try to read it in order to have a specific value.

Regars,

Gianluca.

hello klaetze, Giving a quick view of your code I noticed some point. In your configuration, you set " .bits_per_sample = I2S_BITS_PER_SAMPLE_16BIT, ", so, when you make a calloc you will need: uint16_t* adc_data_buf = (uint16_t*) calloc(NUM_SAMPLES, sizeof(uint16_t)); And so, in your read: ret = i2...

Hello klaetze,

Which IDF are you using? Before pointing to 2Msps, did you try with slower sampling rate?
Could you show me some of your code?

I don't call bootloader_random_disable() function because it is called by the fw start-up routine.

Gianluca.

Hello BitSmith, Before changing the IDF, I suggest you to manage the read from the dma's buffers using "I2S_EVENT_RX_DONE" event. You will find the code below. Let me know if you are able to see something different with this modifications. Regards, Gianluca. // ... QueueHandle_t adc_i2s_event_queue;...

Hi Gianluca, Thanks for the quick response. I'm using the stable(?) idf version 4.1. this seems to be the latest release bar the development version. I haven't changed any of the core idf code, thinking that the examples that are included with the version would have been tested on the version they ...

Hi Guys, This problem is doing my head in. I've been scouring the net trying to find documentation or running code. I have Arduino version of code that runs. But not esp-idf. I'm having the same problem. The documents from espressif are not the expressive and very light on specifics or working code...

In that case maybe try to find when it is happening and try to add small delay before bt command that is causing it. I don't think is a solution because, between the end of the scan and the restart there some operations. Anyway I tried adding 2ms delay before the restart and this message appears. A...

chegewara wrote: ↑

Thu Sep 17, 2020 7:29 am

Of course i am assuming you are getting this error:

Code: Select all

***ERROR*** A stack overflow in task Tmr Svc has been detected

What I have is this error only "BT_HCI: command_timed_out hci layer timeout waiting for response to a command. opcode: 0x200c"

Gianluca