doc: Update Sphinx documentation #123
Conversation
Shetty-Anush
requested review from
SaikiranGudla,
jansunil,
D-Disha and
gprasadbng
as code owners
| @@ -70,6 +70,10 @@ and generate executable file (.bin/.hex) | |||
| .. image:: /source/build/stm32_exclude_syscalls.png | |||
| :width: 600 | |||
|
|
|||
| * Select 'Convert to binary file' to generate a .bin file as a post build output | |||
There was a problem hiding this comment.
Can elaborate this @Shetty-Anush ? Something like (right click on the project->click properties->....)
There was a problem hiding this comment.
Probably adding a screenshot would help?
| * Select 'Convert to binary file' to generate a .bin file as a post build output | ||
| .. image:: /source/build/stm32_convert_to_binary.png | ||
| :width: 600 | ||
|
|
||
| * Program by clicking on the "Run adxxxx_iio" option seen or by performing a copy->paste option of the .hex file seen in the STM32/Debug folder |
There was a problem hiding this comment.
I think this also can be updated making it more relevant and straight-forward.
Run builds the code and tries to program the board but with SDP-K1 (which isn't a native STM32 dev board although we use the stm32 mcu) and no available ST-Link; debug/run configurations need to be set for the programming to happen (either OpenOCD or J-Link) and a Segger J-Link probe (in case of J-Link).
We can just mention how to build code here with a screenshot: Project->right_click->build project
And flashing part is already being covered in the 'Running a project' section.
Add a step in stm32 build to demonstrate how to generate a binary file Signed-off-by: Anush Shetty <[email protected]>
Shetty-Anush
force-pushed
the
post_build_output
branch
from
716cff0 to
14bd15c
Compare
Add a step in stm32 build to demonstrate how to generate a binary file