-
Notifications
You must be signed in to change notification settings - Fork 274
Errors in deploying to Intel Galileo #41
Comments
@Pooja-B, not having issues over here, although I wonder if this wasn't addressed in the pending pull requests. In the meantime, can you try the Galileo code that is available in @ivanignatiev 's fork? |
Can you please suggest me the proper steps to deploy the solution to Galileo? |
See the documentation available in my pending pull request for detailed instructions on deploying to the Galileo. Again, I want to stress that you use the updated Galileo project available in @ivanignatiev 's fork. |
Thanks I will try that . |
@Pooja-B, it happens because in the current branch /ConnectTheDotsGalileo.vcxproj.user file is missing and Visual Studio doesn't copy DLLs to the working directory on Intel Galileo board. It'll work fine when my pull request will be accepted. Fix for the current version in master branch: Also, you can copy additional files manualy. |
Thanks, It is working fine now. I was struggling from many days to implement the " I " part of my IoT app, Thanks for a great example and the documentation part is also well written. :) |
I tried to deploy the sample application given for Intel Galileo but it is giving runtime errors. Has someone worked with Galileo?
I am getting the following errors
'ConnectTheDotsGalileo.exe' (Win32): Loaded 'C:\test\ConnectTheDotsGalileo.exe'. Symbols loaded.
'ConnectTheDotsGalileo.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'. Cannot find or open the PDB file.
'ConnectTheDotsGalileo.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'. Cannot find or open the PDB file.
'ConnectTheDotsGalileo.exe' (Win32): Loaded 'C:\Windows\System32\kernel32legacy.dll'. Cannot find or open the PDB file.
'ConnectTheDotsGalileo.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'. Cannot find or open the PDB file.
The program '[1924] ConnectTheDotsGalileo.exe' has exited with code -1073741515 (0xc0000135) 'A dependent dll was not found'.
The text was updated successfully, but these errors were encountered: