imx-iotcore icon indicating copy to clipboard operation
imx-iotcore copied to clipboard

Published 20 hours ago • verified publisher icon ms-iot

Errors after first project load

Open Cmac2016 opened this issue 6 years ago • 5 comments

Built and deployed the ffu with no issues. When I load my application it runs fine the first time. However when I make a code change and try to redeploy I get the following error: Severity Code Description Project File Line Suppression State Error DEP0100: Please ensure that target device has developer mode enabled. Could not obtain a developer license on 10.0.0.121 due to error 80004005.

Why could this be happening? I have developer mode on in my pc settings but this error implies the setting is on the device not my laptop.

Also noticing that the audio issues for speech recognition and synthesis still appear to be happening. One the device speaks the recognition stops and has to be restarted to work again. I have deployed the app on my laptop and also other devices and this issue is not happening.

Cmac2016 avatar Dec 15 '18 01:12 Cmac2016

I was able to recreate the deployment failure locally. I've filed a bug for it and I will keep this issue updated on the progress.

The audio recording halting once playback halts is a known limitation of the audio driver currently. I'll open an enhancement issue to track improving the audio clocking logic to accomidate both playback and recording independently.

hbeberman avatar Dec 18 '18 01:12 hbeberman

Thank you. For the application i am working on the audio is a big issue. The audio capabilities such as a discreet input and output was one of the main reasons i migrated my code to the Hummingboard and away from other boards such as PI.

Cmac2016 avatar Dec 18 '18 02:12 Cmac2016

@Cmac2016 I believe I've found a solution for the app deploy failure. By default the FFUs have kernel debugging enabled, which is conflicting with the Visual Studio remote debugger.

You can SSH into a fresh install of IoT Core and run the following to disable the kernel debugger:

bcdedit /set debug off
shutdown -r -t 0

You can also remove the line <Feature>IOT_KD_ON</Feature> from the TestOEMInput.xml file for your platform, which will disable kernel debugger by default in your FFU.

hbeberman avatar Jan 03 '19 00:01 hbeberman

I've found another solution. Instead of disabling kernel debug entirely you can also set the kernel debugger to ignore usermode exceptions using the /noumex flag.

bcdedit /dbgsettings SERIAL debugport:1 baudrate:115200 /noumex
shutdown -r -t 0

Full documentation on bcdedit /dbgsettings is available here.

hbeberman avatar Jan 03 '19 20:01 hbeberman

Thank you. I will do a fresh install and try these options. Are there any side effects of doing this?

Cmac2016 avatar Jan 05 '19 18:01 Cmac2016