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

Allow ESP32 boards to work with Visual studio extension #108

Merged
merged 5 commits into from
Jan 4, 2018
Merged

Allow ESP32 boards to work with Visual studio extension #108

merged 5 commits into from
Jan 4, 2018

Conversation

AdrianSoundy
Copy link
Member

@AdrianSoundy AdrianSoundy commented Dec 29, 2017

Changes to allow ESP32 boards to work with Visual Studio extension

Description

The original code only allowed serial ports with the name "STM32 ST LINK" to connect, this change removes this check.

With the ESP32 boards the serial link would default to 7 bit data but 8 bit data is required. Now it is forced to 8 bit data.

Motivation and Context

How Has This Been Tested?

Now when an ESP32 board is connected it is seen in Visual Studio.

Screenshots

Types of changes

  • Improvement (non-breaking change that improves a feature, code or algorithm)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Signed-off-by: Adrian Soundy adriabsoundy@gmail.com

Removed the check for "STM32 STLINK" com port name.
Found that sometimes when connecting boards receieved a  Device error which was causing a NotImplemented Exception and stopped.
On some boards it defaults to 7 data bits

Signed-off-by: Adrian Soundy <adriabsoundy@gmail.com>
@nfbot
Copy link
Member

nfbot commented Dec 29, 2017

Hi @AdrianSoundy,

I'm nanoFramework bot.
Thank you for your contribution!

A human will be reviewing it shortly. 😉

@CLAassistant
Copy link

CLAassistant commented Dec 29, 2017

CLA assistant check
All committers have signed the CLA.

// the default on the current ST Link is different causing
// the communication to fail
/////////////////////////////////////////////////////////////
_device.DataBits = 8;
Copy link
Member

Choose a reason for hiding this comment

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

Please add back the comment block that was there. It seems harmless but it has cost a lot of time finding the root cause for the issue and that comment documents that. 😉

// the default on the current ST Link is different causing
// the communication to fail
/////////////////////////////////////////////////////////////
_device.DataBits = 8;
Copy link
Member

Choose a reason for hiding this comment

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

Please add back the comment block that was there. It seems harmless but it has cost a lot of time finding the root cause for the issue and that comment documents that. 😉

Also found another place where device is set up.
Copy link
Member

@josesimoes josesimoes left a comment

Choose a reason for hiding this comment

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

LGTM

@josesimoes josesimoes merged commit 9c095cb into nanoframework:develop Jan 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants