Few things on "how"
Have a pseudoce about WHAT is the purpose of the code showing inputs / outputs.
Than CHANGING the output would be more visible in code.
Get into habit to comment your code. I do 80% comments and 20% real code ratio.
I realize your construct your code using your native language that write it in English, so that is why there are no (English) comments in your code.
Find a IDE which allows you to set breakpoints or use some other method to track your code.
Hi All, I'm trying to expand my development setup. I have a win10 laptop that handles the average stuff, but being tied down with extra monitors and a real keyboard and mouse it's lost a lot of its mobility. That and a lack of desk space has got me dreaming of other expanses of unused surfaces around my apartment. I'm looking to do more embedded programming on a Linux o.s., and I currently have an ESXi host with a few vm's that can do the job. My spare laptop is an arm based chromebook. Not much I can do to connect to the vm's other than vlc and the like. Any ideas on how I could hook USB dev boards to my chromebook and program them through a remotely accessed VM ?? I haven't been able to find many tools for this purpose.
AS my development machine & my test machine are 64bit windows system with Windows 7 operating System So to give myself a head start I compiled the ComPort project under Windows-driver-samples-master/serial/VirtualSerial2 sample code provided by Microsoft, initial it flashed an error that said as follows "Provider cannot be "Microsoft", must be an organization who authored INF" so I changed the following line in .inx file MSFTUMDF=Microsoft to MSFTUMDF=Sample, then it compiled successfully.
Then I follow the following process to install the driver on the target machine.
1) I copied the VirtualSerial2um.cer file VirtualSerial2um.inf from Windows-driver-samples-master\serial\VirtualSerial2\ComPort\x64\Debug & devcon.exe from C:\Program Files\Windows Kits\10\Tools\x64 to a Sample folder in the C:\ drive of the Target device.
2) Then on target machine I open the internet explorer I went to Internet Options->content->Certificates->import then I selected the VirtualSerial2um.cer file & imported the Certificate.
3) Then on target machine I opened the command prompt as Administrator, browsed to the Sample folder & typed the following command.
I am searching for all btle devices with BluetoothLEAdvertisementWatcher.
It works fine but I need a device handle so I can use GATT api's.
How do I get a device handle from the information provided in BluetoothLEAdvertisementReceivedEventArgs?
“If I had asked people what they wanted, they would have said faster horses.”
― Henry Ford
I have a WDM upperfilter driver for some class devices(WPD, Printers). The wdm upper filter is from WDK generic toaster filter sample. The problem that I have is for some device that support or install UMDF drivers I receive STATUS DEVICE CONFIGURATION_ERROR at IRP_MN_START_DEVICE and device failed to start. Can you help me please or give me an advice?
I have a WDM filter driver, based on WDK toaster sample, that I am using to filter portable devices (mainly Phones), as upper filter. During AddDevice phase, I am querying device properties (such Description, Manufacturer and so on) and then attaching to device. I can see the IRP_MN_START_DEVICE, which I send down to next lower driver after setting a completion routine. This is working fine on most of the machines I am testing on, but on some systems (every XP and some Windows 7 and Server 2008), when I send the IRP_MN_START_DEVICE down to next driver, I get a STATUS_DEVICE_CONFIGURATION_ERROR, so this is preventing the device from being installed in the first place. I have managed to overcome this error by editing the hardware ID registry key for the device and creating "UpperDriverOk" and "KernelModeClientPolicy" values, setting them to 1. This way the device starts without issues and I can filter it as normal. Now, I am aware of Portable Devices being managed by an UMDF driver, but does that explains the issue with Start Device phase? I haven't found any differences between those systems with the issue and those that are working fine without needing the "registry values" workaround. Is there any system setting or service configuration that might be helping (or ruining) this filtering scenario? Would it be possible to apply the "KernelModeClientPolicy" workaround for the whole system and not separately for every single Phone device?
Yes, I've googled. I have the need to "program" SD Cards with an application deployment image. We've had some issues with reliably getting factory employees to properly program these SD cards - actually started with Windows Explorer. In any event, I now have a script that makes use of chkdsk and xcopy to expand the production image onto an SD Card.
However, there are random times (less than 1%) where the process fails. Following the xcopy command, the chkdsk might fail with a variety of errors:
1) "filename" first allocation unit is not valid. The entry will be truncated.
2) "filename" entry contains a nonvalid link. The size of <filename> entry is not valid.
I really don't expect xcopy to generate these errors. We're using commercial grade SD card readers (like you'd buy off Newegg or Amazon).
Any ideas or suggestions?
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
That are file system errors. They may be sourced by faulty SD cards or by a reader that has problems with specific SD card types.
If you got such errors sometimes I would not only perform a chkdsk but also a binary file compare on all files. Doing so you might find more unusable cards.
With disk images you may also create an image file and write that to the cards using an image writer utility (again followed by a verify that performs a binary comparison). While this takes more time it avoids the need of formatting and gives you identical images.
Because the error rate is below 1% you might live with it and dispose the faulty SD cards or try to reduce the error rate by using other SD cards and/or readers.
Last Visit: 26-Jan-20 16:49 Last Update: 26-Jan-20 16:49