⚠️ Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
Thanks for your question online. However, could you please clarify it and indicate what you mean with “SVD for the Bluetooth SoC”? In addition, which device are you using? DA1469x or DA14580?
Unfortunately, this is not supported. During a debugging session, the developer can read, as well as set, systems registers including GPIOs and other peripheral registers. This is done in the Eclipse tool named EmbSys Registers. Please take a look at section 2.3. Device-Specific Registers.
谢谢你的信息。我可不是talking about debug session. The API generated from SVD will be used to write actual firmware (in Rust, instead of C) that runs on the SoC. I understand that Rust is not officially supported, and I wasnt asking for Rust support either. Nevermind, I have the SVD from Keil's website. So I'll use that instead.
Ηi jayaura,
Thanks for your question online. However, could you please clarify it and indicate what you mean with “SVD for the Bluetooth SoC”? In addition, which device are you using? DA1469x or DA14580?
Thanks, PM_Dialog
Thanks for the response. Sorry I overlooked the device option for the post. I am using DA14695. SVD's can be used to generate register interfaces in an automated fashion. For instance, STMicro provides them and in the Rust ecosystem, these files are used to generate API for accessing the SoC Registers. For reference, please seehttps://github.com/stm32-rs/stm32-rs/tree/master/svd/vendor. These files are used by svd2rust (https://github.com/rust-embedded/svd2rust/) to generate APIs likehttps://docs.rs/stm32f1/0.8.0/stm32f1/stm32f103/index.html
ST provides SVD files for stm32f1 series athttps://www.st.com/resource/en/svd/stm32f4_svd.zip
After some research I found I can download it fromhttps://www.keil.com/dd2/pack/. I think I will use this unless Dialog has an official source.
Thanks
Hi jayaura,
Unfortunately, this is not supported. During a debugging session, the developer can read, as well as set, systems registers including GPIOs and other peripheral registers. This is done in the Eclipse tool named EmbSys Registers. Please take a look at section 2.3. Device-Specific Registers.
http://lpccs-docs.dialog-semiconductor.com/tutorial_da1468x_debugging_techniques/debuggers_eclipse.html
Thanks, PM_Dialog
谢谢你的信息。我可不是talking about debug session. The API generated from SVD will be used to write actual firmware (in Rust, instead of C) that runs on the SoC. I understand that Rust is not officially supported, and I wasnt asking for Rust support either. Nevermind, I have the SVD from Keil's website. So I'll use that instead.
Hi jayaura,
Unfortunately, SVD files are not supported.
Thanks, PM_Dialog