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

COM port "file not found" on windows #1

Open
kubaraczkowski opened this issue Aug 25, 2016 · 4 comments
Open

COM port "file not found" on windows #1

kubaraczkowski opened this issue Aug 25, 2016 · 4 comments

Comments

@kubaraczkowski
Copy link

Not sure if it's only me, but when programming NRG1.0 board I needed to change the msp430-gdb command to do "target remote \\.\COM26" on windows instead of simply "target remote COM26" which is default.
Could somebody perhaps try it as well? (tested on win7 64b)

@dberenguer
Copy link
Contributor

This is probably an old bug. We didn't fully test NRG 1.0 on the newest (at
that time) Windows distributions.

Daniel Berenguer
http://www.panstamp.com

On 25 August 2016 at 19:23, Kuba Raczkowski notifications@github.com
wrote:

Not sure if it's only me, but when programming NRG1.0 board I needed to
change the msp430-gdb command to do "target remote .\COM26" on windows
instead of simply "target remote COM26" which is default.
Could somebody perhaps try it as well? (tested on win7 64b)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA19-9xIGmDZkLCYNNjw5pJGU8cC2PAbks5qjc-WgaJpZM4JtToD
.

@kubaraczkowski
Copy link
Author

Yes, that's what I thought. I just have a bunch of them still and wanted to
make some use of them.

On Fri, Aug 26, 2016 at 10:32 AM Daniel Berenguer notifications@github.com
wrote:

This is probably an old bug. We didn't fully test NRG 1.0 on the newest (at
that time) Windows distributions.

Daniel Berenguer
http://www.panstamp.com

On 25 August 2016 at 19:23, Kuba Raczkowski notifications@github.com
wrote:

Not sure if it's only me, but when programming NRG1.0 board I needed to
change the msp430-gdb command to do "target remote .\COM26" on windows
instead of simply "target remote COM26" which is default.
Could somebody perhaps try it as well? (tested on win7 64b)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1, or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AA19-9xIGmDZkLCYNNjw5pJGU8cC2PAbks5qjc-WgaJpZM4JtToD

.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAh2nGfmvrwy8Y88wzAmMfCio6Ut_rBcks5qjqR5gaJpZM4JtToD
.

@dberenguer
Copy link
Contributor

Does your fix work?

Daniel Berenguer
http://www.panstamp.com

On 26 August 2016 at 10:35, Kuba Raczkowski notifications@github.com
wrote:

Yes, that's what I thought. I just have a bunch of them still and wanted to
make some use of them.

On Fri, Aug 26, 2016 at 10:32 AM Daniel Berenguer <
notifications@github.com>
wrote:

This is probably an old bug. We didn't fully test NRG 1.0 on the newest
(at
that time) Windows distributions.

Daniel Berenguer
http://www.panstamp.com

On 25 August 2016 at 19:23, Kuba Raczkowski notifications@github.com
wrote:

Not sure if it's only me, but when programming NRG1.0 board I needed to
change the msp430-gdb command to do "target remote .\COM26" on
windows
instead of simply "target remote COM26" which is default.
Could somebody perhaps try it as well? (tested on win7 64b)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1, or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AA19-
9xIGmDZkLCYNNjw5pJGU8cC2PAbks5qjc-WgaJpZM4JtToD

.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAh2nGfmvrwy8Y88wzAmMfCio6Ut_rBcks5qjqR5gaJpZM4JtToD>
.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA19-9koyRnES7j9OtK948ii54Ev5ISdks5qjqVFgaJpZM4JtToD
.

@kubaraczkowski
Copy link
Author

Well, for the moment I've only tried by taking the error message,
extracting the msp430-gdb command which does the programming, adapting the
COM port notation, running - gets the work done.
Did not try adapting in the arduino software...

On Fri, Aug 26, 2016 at 10:44 AM Daniel Berenguer notifications@github.com
wrote:

Does your fix work?

Daniel Berenguer
http://www.panstamp.com

On 26 August 2016 at 10:35, Kuba Raczkowski notifications@github.com
wrote:

Yes, that's what I thought. I just have a bunch of them still and wanted
to
make some use of them.

On Fri, Aug 26, 2016 at 10:32 AM Daniel Berenguer <
notifications@github.com>
wrote:

This is probably an old bug. We didn't fully test NRG 1.0 on the newest
(at
that time) Windows distributions.

Daniel Berenguer
http://www.panstamp.com

On 25 August 2016 at 19:23, Kuba Raczkowski notifications@github.com
wrote:

Not sure if it's only me, but when programming NRG1.0 board I needed
to
change the msp430-gdb command to do "target remote .\COM26" on
windows
instead of simply "target remote COM26" which is default.
Could somebody perhaps try it as well? (tested on win7 64b)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1, or mute the
thread
<
https://github.com/notifications/unsubscribe-auth/AA19-
9xIGmDZkLCYNNjw5pJGU8cC2PAbks5qjc-WgaJpZM4JtToD

.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
#1 (comment)
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAh2nGfmvrwy8Y88wzAmMfCio6Ut_rBcks5qjqR5gaJpZM4JtToD>
.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1 (comment)
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AA19-9koyRnES7j9OtK948ii54Ev5ISdks5qjqVFgaJpZM4JtToD

.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAh2nHSMapVp6WmZss594-uC4LH3KQ4Xks5qjqdogaJpZM4JtToD
.

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

No branches or pull requests

2 participants