Add STM32C0/G0/L0 ADC driver

[nandojve]

This fixes all open issues that blocks the STM32 ADC to run in the C0/G0/L0 devices. The related issues are:

• https://github.com/renode/renode/issues/414
• https://github.com/renode/renode/issues/542
• https://github.com/renode/renode/issues/569

This was tested using Zephyr mainline using https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/drivers/adc sample using the following branch https://github.com/nandojve/zephyr/tree/renode/fix_stm32_c0g0l0_adc.

Assuming the renode already in the path the below command allow build and run the simulation.

west build -b nucleo_g071rb deps/zephyr/samples/drivers/adc -t run
west build -b b_l072z_lrwan1 deps/zephyr/samples/drivers/adc -t run
west build -b nucleo_c031c6 deps/zephyr/samples/drivers/adc -t run

depends on https://github.com/antmicro/dts2repl/pull/6 and https://github.com/antmicro/dts2repl/pull/5

[otavio]

Cc: @mateusz-holenko

[tyler-macinnis]

Is there anything in particular that is delaying this PR from being completed? It has been over 2 months.

[nandojve]

Is there anything in particular that is delaying this PR from being completed? It has been over 2 months.

Hi @tyler-macinnis ,

We synced 2 weeks ago with Renode team and we are waiting decision about possible API changes. After that we may apply a few changes, if necessary, but I believe this will start to move forward soon.

[pgielda]

Is there anything in particular that is delaying this PR from being completed? It has been over 2 months.

I am confused here... Its been two months since what? Can you elaborate on what company/project you represent? This whole discussion is weird. You all seem to be working on some project that I (nor anyone else in my company) am not aware of. We will reach out (over email) to @nandojve since we know each other from Zephyr Project so that there is a possibility to get additional context, but if the tone here and the pressure (passive aggressive complaints or CCing people) will not change then I will close just this PR...

[otavio]

@pgielda, @nandojve, and I (@otavio) work for O.S. Systems. @tyler-macinnis is a community user who seems to be affected by the same issue that @nandojve and I resolved. We didn't want to appear impolite.

[tyler-macinnis]

I meant that it had been two months since this last message. I was just curious about the current state/progress of this PR since it will indeed resolve an issue I am affected by as well.

[pgielda]

Well pinging a random person on github was never a way to achieve a result. @mateusz-holenko (nor anyone from the Renode team) has no clue who @otavio is... Opening a PR is enough, no need to ping us, especially specific random engineers... It will be looked at when its looked at...

[pgielda]

Just so that its clear @tyler-macinnis, this is an external PR, so there is no timeline. None of the people in this discussion (apart from me) are from the Renode team.

But we do plan to address ADCs for more STM32 platforms at some point, but also tons of other things that are planned that might be more important... Unfortunately there is 10x more stuff to be done than time.

Having said that Renode does allow to load peripheral code in runtime so you can just download those and load them in runtime in your scripts. (just do "include @/path/to/file.cs" in your resc script and Renode will compile and load the code).