Vitaly Svyastyn

> Running the tool across all the stm32 devices would be interesting as well. Is there any shared peripherall across all those? From my experience the answer is - almost...

Number 429 comes up only when you run script against ALL SVD files for STM32. Which includes STM32W108 with a lot of unique peripherals. Also there is RCC, which is...

Will try to share my findings so far. I decided to start from GPIO and it looks like that there is really only two types of it in all STM32...

@japaric Something like this I had in mind when proposed #122. I just thought that we will have to write base and device SVD files by hand for it to...

To @etrombly. I solved this problem by changing field definitions in SVD file. CNF and MODE bits for the same pin are adjacent so instead of separate 2-bit fields I...

If we were able to implement #96, then the solution to this problem would be greatly simplified. Then third-party crates could use not "stm32f103c8::TIM2" but something like "stm32::GPTimer" or "stm32::DAC"....

>For example, for 596 devices in dslite database, we have only 4 kinds of watchdog timer, 12 kinds of rtc clock, 3 kinds of AES accelerator, etc. In theory we...

@japaric I was referring to "re-exports" solution. If there was some way to tell svd2rust that peripherals in different devices are the same (like proposed in #96) then common crate...

@japaric This check is really impossible with XML schema. So if it is not hard to implement it would be nice if svd2rust printed a warning in such cases (like...

1-wire can be implemented not only in software or using timers. UART+DMA is very convenient for generating required waveforms and receiving data. I used this approach for working with DS18B20...