-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Port and build for STM32F411RE #141
Comments
@valoni I believe you've managed to successfully build this target. |
YES after some tips and info i received i learn more how to manage sources
- latest build - I build without problem
- also i can manage problem with overleap size
- activated SPI=ON without problem on DEBUG mode for both boards
(Discovery STM32F407VGT6 and NUCLEO STM32F411RET6) after managing oversize
but the problem i face is
at home i have pc with VS2017 (and i'm there just later or when i have
available time)
at work when i am and on faculty when i tech students we have VS2015
(there i have time but i could not change development tools so i cant use
it for development and test since need VS2017 except VS2017 code)
so for confirmation i managed to build today all those platforms for Nucleo
STM32F411RET6
*1.) nanoFramwork 0.2.0 *
*2.) NET Microframwork 4.4.0.0*(today i build) #
i dont know why it is not added by default on Discovery is OK but on
Nucleo NO so need to check for
- Microsoft.SPOT.Hardware.PWM,4.4.0.0
- Microsoft.SPOT.Hardware.OneWire,4.4.0.0
*3.) TinyCLR OS 0.6.0* (it can use now ST-LINK programmer- as SERIAL
Debug/Deploy with TinyCLR no need more for PA11/PA12 connector)
…On Tue, Sep 5, 2017 at 1:15 PM, José Simões ***@***.***> wrote:
@valoni <https://github.com/valoni> I believe you've managed to
successfully build this target.
If yes, then this can be closed. Please confirm.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#141 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOjzPcVOEg4HAJsGsCWPp7DED3WD_beks5sfS1SgaJpZM4PHSZI>
.
--
Valon Hoti
|
Please close this issue :)
--
Sent from myMail for Android Tuesday, 05 September 2017, 01:15PM +02:00 from José Simões [email protected] :
…
@valoni I believe you've managed to successfully build this target.
If yes, then this can be closed. Please confirm.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub , or mute the thread .
|
Thanks for letting us know about your successes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From nf-interpreter created by josesimoes : nanoframework/nf-interpreter#413
@valoni as I didn't want to hijack the .NETMF issue, so I'm opening this here were it belongs.
Regarding your questions on NETMF/netmf-interpreter#538:
(you'll find that you don't nee much 😉 )
Trust this can, at least, get you started. Anyways you'll get all the help that you ask for here on in the Slack community.
The text was updated successfully, but these errors were encountered: