Repository navigation
Document MSPM0, HPM and the pin layout in the README - #29
Merged
Merged
Conversation
…forms in the README
Parsing an MSPM0 project runs SysConfig only when SYSCONFIG_TOOL and MSPM0_SDK_INSTALL_DIR are set and reuses a build output otherwise; the two sections get headings in the README's style; UART, I2C and SPI objects take the lower-case peripheral name; the HPM init_bsp_pins fallback applies only when main calls no pinmux function; the package rules and the data license name HPM.
The setup of every platform reminds to run xrobot gen once Modules/modules.yaml exists; the XRobot integration section named stm32 setup and the steps before modules.yaml only, and the MSPM0 and HPM example outputs lacked the reminder.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents in the README what #25 added: the MSPM0 and HPM flows and
libxr pinsfor the three platforms.What changes
libxr mspm0 setupon the root.syscfg; when SysConfig runs (SYSCONFIG_TOOL+MSPM0_SDK_INSTALL_DIR) and when a newer build output is reused; the generated objects (GPIO after the pin label, UART/I2C/SPI after the lower-case peripheral name, PWM aspwm_<timer>_c<n>) and their settings inlibxr_config.yaml.libxr hpm setuponapp.yaml+boards/*/*.hpmpc; pins from the pinmux functionsmaincalls outside preprocessor conditions,init_bsp_pins()only whenmaincalls none; GPIO renames; I2C and GPTMR PWM.libxr pins: STM32, MSPM0 and HPM models and packages, the-dproject overlay (project.assignments/project.peripherals, the whole-section GPIO rename of an HPM), and the pin data sources and licenses.Modules/modules.yamlexists, thexrobot genreminder after).libxr mspm0 setup,libxr hpm setup.README only. It merges cleanly with #26/#28 (CDC
interface) and #27 in either order.Verification
libxr mspm0 setupandlibxr hpm setupoutputs are line-for-line those of a fresh run of this dev line on bsp-mspm0g3507-mini and bsp-hpm5301evklite; excerpts are marked as such.generator_code_mspm0.py,generator_code_hpm.py,pin_project.pyandcli.pyon dev.