Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add stm32p103 emulator instruction #4

Closed
wants to merge 1 commit into from

Conversation

mlouielu
Copy link
Contributor

@mlouielu mlouielu commented Aug 9, 2017

Add instruction for how to run stm32p103 emulator.

@mlouielu mlouielu mentioned this pull request Aug 9, 2017
@jserv
Copy link
Member

jserv commented Aug 9, 2017

Let's move the instructions into a new dedicated page at directory "Documentation/".

@mlouielu
Copy link
Contributor Author

mlouielu commented Aug 9, 2017

Do you want to use sphinx, or plain text is enough?

@jserv
Copy link
Member

jserv commented Aug 9, 2017

Using plain text should work.

Creating MTD device mtd0
Kernel bootstrap done.
--
Piko version 0.0.0 (uscc@uscc-Inspiron-7559) (armv7-m, cortex-m3) #Sun Apr 30 17:58:03 2017
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The two lines were generated by build host, and you don't have to include explicitly.

$ export PATH=$PATH:~/qemu_stm32-stm32_v0.1.3/arm-softmmu
```

You will need to modify the target from `stm32f429` to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not necessary to modify Makefile. Instead, you only have to execute make TARGET=stm32p103.

@mlouielu
Copy link
Contributor Author

Close this by proposing #13

@mlouielu mlouielu closed this Aug 15, 2017
@mlouielu mlouielu deleted the add_stm32p103_instruction branch August 15, 2017 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants