I've registered a new case at Microchip Support, asking for missing files in documentation (5 days ago and there is no answer).
I trying to use SEC1210 UART ( http://ww1.microchip.com/downloads/en/AppNotes/00001977A.pdf )
In CCID driver (pg 2) is needed some files to serial mode work properly, so, i need thoses files, can someone help me ? or can someone explain, what i need to change to make serial comunication to work properly ?
Related
Good Day!
Can you please let me know, if I can get the information and print(in command line from a variable) of all files opened or read from say D:\ using an User Mode Kernel Driver?
Can I use WinDbg to debug the same driver and get the file information viewed?, As I felt it as a safe mode to avoid crashing the system.
Can you please let me know the process to do that?
Please accept my apologies, if it's a sub standard question, I am new to Windows Driver Development and As of now, I am learning the processes.
Thanks Guru
from France !
I just want to know if there is a tip for my old xperia s (LT 26i) to change this status ( bootloader unlock not allowed : NO !) to YES then i can unlock my bootloader at the end to install custom rom because there is more and more apps who didn't work at all !
i found old topics in xda (testpoint method, wotan and omnius server but it was only for 2011 smartphones). Now i was wondering if it's possible (if i find one with good status) to flash a TA partition ? In this case maybe you can send me one...
Anyway, i've never told about that when i've bought my phone, so my operator would be agree if you have to fix the phone...
I'm a tech guy with developper abilities so i can follow any procedure
Thanks for answering me because from now no one was able to give me a clear answer
Have a good day ( excuse my french, hope it's understandable ! )
Mr Niederlender
I have some experience with the Xperia bootloader, having an Xperia SP myself and messing with it.
Not so long ago, I stupidly flashed the simlock.ta file included in an .ftf file in Flashtool, thinking it would resolve my SIM-card reader issues. I've had an unlockable/unlocked bootloader up until that point. Upon booting the phone up again, the bootloader was locked, and the service menu said "Bootloader unlock allowed: NO".
I've tried messing with my TA partition and all kinds of simlock.ta files, but I've figured out with a friend of mine with an SP aswell, the TA seems to have a value, a sort of hash it checks the simlock section of the TA, and if it doesn't match, it activates a lockdown, disabling the SIM-card reading ability, disabling fastboot completely (booting normally to Android when volup + power or adb reboot bootloader). Literally changing the TA file and flashing it back won't work, the phone will be hard-bricked at that point and you'll need to use the testpoint found by taking the device's back apart, a hard-to-find tool to convert your TA backup into a SETool2-workable file and SETool2 to restore a backup of the TA you've made before doing any of the changes. (if you forget the backup, dead device)
Now I have done some research and found that 2011 Xperia devices had in their TAs a "Security Unit" section, which basically holds to-your-device-exclusive numbers that determine whether the TA is truly yours and whether the device boots. I'd assume the same holds true today, or at least for the Xperia SP, and if we could get an Xperia SP TA backup with an unlockable/unlocked bootloader, we could patch this TA file to have our own unique Security Unit inside and possibly have a bootable device with an unlockable bootloader with fastboot back, even if the SIM-card reading is gone.
This is, of course, definitely against what Sony would want us to do, and also not an answer that is a solution, but considering our warranties are over, the device has reached its end of support by Sony, and I've taken the device apart to be able to use its testpoint, I think this "hacky" method is still a theoretical solution.
Hope this helped you understand the situation better, and I'm also hoping there'll be someone that can help us in the future. This is such a great device with a custom ROM (specifically StryFlex Marshmallow is a beast on this device) and I'm hoping I'll one day see it working with it again.
TL;DR: Purely flashing a TA partition of another device hard-bricks the phone, possible (theoretical) workaround to hard-brick by patching the new TA to have our old Security Units section.
Simlock afterall does correspond to bootloader-unlockability, flashing a simlock file activates a sortof "lockdown" to SIM-reading, fastboot and bootloader-unlockability.
I am working on an application for our IT support team. For one of the requirement, I need to find out the manufacturing date of a laptop (and some desktops). I did some googling and found some solutions but none of them are feasible in my case:
Serial Number : get the serial number from the back of the machine and access the vendor's site with given serial number and get all the details.
-> This is not going to work because there are hundreds of machines and from many vendors like Dell, HP, Lenovo, etc.
Operating System : I can extract all the OS level info by using "systeminfo.exe". There is a field called "Original Install Date" which will give a date when OS was installed on the machine.
-> This is also not going to work for me because whenever a laptop is assigned to a new user, it is being formatted and fresh OS image is being deployed so everything this date will change.
BIOS : In one of the articles it is being stated that because BIOS is installed as soon as the assembly is finished so it can provide the most accurate date when the machine was ready to end user use after installing OS. So I have used "Win32_Bios" WMI class to extract this data.
-> The problem with this approach is whenever any BIOS version upgrade happens, this BIOS date is also getting modified, so I cannot get the real manufacturing date of the machine.
Last approach, I thought if I can get the processor manufacturing date then I might get some approximate date when the machine came into existence. I checked Device Manager --> Processors --> Properties.
-> Problem with this approach is, I am seeing the version and date of the processor driver and not the real processor and this date is showing way back from 2006
I would really appreciate if someone please share their views or experiences regarding the above situation.
I know this kind of the question has been asked before and it has been closed down because people thought it is not very interesting topic to discuss so I really request to all please do not close this question. Let's give a chance to everyone to share their views.
Thanks.
hi :
i was building kernel for my gentoo linux . when i start the kernel , i
got this message , and can't going on.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
non-volatile memory driver v1.3
i don't know how to solve this problem . and i need help . thanks .
Why don't you try to disable pci hotplug support in kernel (if I recall correctly is in main config menu / PCI support)? You probably don't need this.
I'm going to have to disagree with those voting to close, because I think there really is a question here, and the question is "How to debug this?"
I'm going to propose two approaches:
1) Studious approach: Learn about mechanisms intended for handling boot problems. See if you can increase the kernel debug message level. Disable un-needed drivers as Quizzo suggested.
2) Cowboy approach: grep the kernel sources for strings seen in the final messages, and start shotgunning all possibly relevant bits of code with your own "still alive at" printk messages. Once you know where it's hanging, figure out why and either remove that mechanism or fix it.
At an extreme there's also a tool for debugging the kernel - kgdb - which you could set up if you have a second machine available.
If you already have linux running on this box, see if there's a config.gz in /proc or in a boot folder which you can extract and compare to the configuration you are trying to compile. It might not be a bad idea to first recompile and test exactly the same version and configuration as you have running, and then make desired changes one by one.
Also you might see if there's odd hardware in your system you could temporarily remove. For example, an older PC I have has a bios that hangs during drive enumeration if I have a large USB external drive plugged in during boot.
i have solved the problem by enable all pci hotplug flag in kernel config file.
thinks all.
I am currently trying to build an application, that will talk to the super IO chip using port IO. As part of that, I am trying to develop a kernel-mode windows driver that I can contact, and which will do the IO for me. I have therefore downloaded the Windows Driver Kit v7.1.0, build 7600.16385.1, and I am trying to compile and install the sample portio driver, which is provided by WDK, since it seems to be quite close to what I need.
I have compiled the driver in both free and checked x86 XP build environments. This works fine, but when I try to install the resulting driver, using the provided instructions - which basically just amount to using the Add Hardware Wizard, and then supplying the files manually - I get the following error:
-The following hardware was installed: Sample PortIO Driver (KMDF)
-The software for this device is now installed, but may not work correctly
-Windows cannot load the driver for this hardware. The driver may be corrupted or missing. (Code 39)
So, I see two explanations: corrupted or missing. Missing, as far as I can tell, given my environment variables and .inf file, would mean that the generated .sys file is not in c:\windows\system32\drivers, but when I look there, the file is there.
So that would mean that the file is corrupted. Given that I haven't touched the driver code, and that I have found others with the same problem, it doesn't seem to be a problem with my compilation, but rather with the code itself, or some common combination of machine type and code. But I may be wrong.
Does anybody have any suggestions on how to solve this?
I would recommend enabling SetupAPI logging as described in the following document from Microsoft:
http://www.microsoft.com/whdc/archive/setupapilog.mspx
For Windows 7, the log files are split up as described here:
http://support.microsoft.com/kb/927521
You may be able to isolate the problem with the additional information in the SetupAPI logs.