You must be logged in to reply.

Page 2 of 3 out of 24 messages.

TinyCLR and windows 7

1 like
Reply #10 — Posted 1yr ago
by Bauland | Master | 6,336 exp
Reply #10 — Posted 1yr ago
by Bauland | Master | 6,336 exp
It's working for Brainpad too ! Clapping
2 likes
Reply #11 — Posted 1yr ago
by John_ghielectroncs | Employee
Reply #11 — Posted 1yr ago
by John_ghielectroncs | Employee
@MNO and Bauland - Glad to hear it's working. We'll look into this more for a future release.
Reply #12 — Posted 1yr ago
by MNO | Senior | 3,165 exp
Reply #12 — Posted 1yr ago
by MNO | Senior | 3,165 exp
@John_ghielectroncs - Hello John,
Thanks for the work done since TinyCLR v0.3.0. I installed TinyCLRv0.5.0 on Windows 7. G80 is now recognized by VS2017 but the debug mode does not work. The program is transferred but does not work step by step.
Reply #13 — Posted 1yr ago
by John_ghielectroncs | Employee
Reply #13 — Posted 1yr ago
by John_ghielectroncs | Employee
@MNO - Step by step?
Reply #14 — Posted 1yr ago
by MNO | Senior | 3,165 exp
Reply #14 — Posted 1yr ago
by MNO | Senior | 3,165 exp
@John_ghielectroncs - This seems to be a poor translation of (pas à pas) in this context . I wanted to say: In debug mode. Smiley
Reply #15 — Posted 1yr ago
by John_ghielectroncs | Employee
Reply #15 — Posted 1yr ago
by John_ghielectroncs | Employee
@MNO - So you can deploy an app like blink LED and if you just power the board it works, but when you try to start the VS debugger with the same program, it doesn't?
Reply #16 — Posted 1yr ago (modified)
by MNO | Senior | 3,165 exp
Reply #16 — Posted 1yr ago (modified)
by MNO | Senior | 3,165 exp
@John_ghielectroncs - Yes, when I try to start the VS debugger with the same program, it doesn't work.
Reply #17 — Posted 1yr ago
by John_ghielectroncs | Employee
Reply #17 — Posted 1yr ago
by John_ghielectroncs | Employee
@MNO - What behavior specifically are you seeing that's failing? Are there any errors shown anywhere?
Reply #18 — Posted 1yr ago
by MNO | Senior | 3,165 exp
Reply #18 — Posted 1yr ago
by MNO | Senior | 3,165 exp
@John_ghielectroncs -

I see this during the compilation :

Looking for a device on transport 'USB'.
Found device port 'USB' with ID '72400619-1d04-4ba9-8325-ddafbd648169' for transport 'Usb'.
Starting device deployment.
Attempting to connect to device 'USB:G80': iteration 0.
Opening port '\\?\usb#vid_1b9f&pid_0110#5&3971263f&0&1#{c13bcfe9-5e84-4187-9baa-45597ffcbb6f}'.
Attaching debugger engine.
Debugger engine attached.
Querying device assemblies.
Found assemblies:
- TinyCLRBlink v1.0.0.0.
- mscorlib v0.5.0.0.
- GHIElectronics.TinyCLR.Devices v0.5.0.0.
Generating device specific assemblies.
Deploying assemblies:
- TinyCLRBlink v1.0.0.0 with size 644 bytes at 'C:\Users\Administrateur\documents\visual studio 2017\Projects\TinyCLRBlink\TinyCLRBlink\bin\Debug\pe\TinyCLRBlink.pe'.
- mscorlib v0.5.0.0 with size 76 636 bytes at 'C:\Users\Administrateur\documents\visual studio 2017\Projects\TinyCLRBlink\TinyCLRBlink\bin\Debug\pe\mscorlib.pe'.
- GHIElectronics.TinyCLR.Devices v0.5.0.0 with size 40 968 bytes at 'C:\Users\Administrateur\documents\visual studio 2017\Projects\TinyCLRBlink\TinyCLRBlink\bin\Debug\pe\GHIElectronics.TinyCLR.Devices.pe'.
Total deployment size is 118 248 bytes.
Incrementally deploying assemblies to the device:
- Erasing sector 1 (131 072 bytes).
- Writing sector 1 (644 bytes).
- Erasing sector 2 (131 072 bytes).
- Writing sector 2 (117 604 bytes).
Assemblies deployed. There are 143 896 bytes left in the deployment area.
Restarting interpreter.
Attaching to device.
Waiting for device to initialize.
The debugging target and the debugger engine failed to initialize because of unspecified device errors.
The debugger engine thread has terminated unexpectedly with error 'Could not reconnect to the debugging target after rebooting it.'.
Reply #19 — Posted 1yr ago
by John_ghielectroncs | Employee
Reply #19 — Posted 1yr ago
by John_ghielectroncs | Employee
@MNO - Can you try to reflash the firmware, create a new project to test, and reinstall the VSIX?

Page 2 of 3 out of 24 messages.

You must be logged in to reply.