Update 1:
Hi friends, could you please recommend me a powered USB hub in Australia(preferred in Melbourne)? I guess my problem is caused by the insufficient power supply.
Hi friends,
I have a FEZ Hydra Basic kit. I got it in 2012 (might be in Sep).
Today I downloaded the latest SDKs, drivers and everything(NETMF and Gadgeteer Package 2014 R1). (.NET Micro Framework 4.3 and the firmware I have on my laptop is 4.2.6.2)
But the firmware on my deivce is 4.1.x.x(I was lucky to saw the device's firmware version just once and I followed the instruction on the software FEZ Config, but failed with errors).
After that, I cannot get the Device's firmware version any more.
I found changing USB ports sometimes help. I have 4 USB ports, some of them can connected to the device, others are not.
So I have no idea to update the firmware in other way.
Could someone please help me to figure out how to find a way to update my firmware?
In the attached image, it shows: the FEZ Config detected the FEZ Hydra and was trying to get the device's firmware version, but it failed to do so and followed by an error message say: Failure - Device is not connected or not responding.
As I mentioned above, I was lucky to see the FEZ Config successfully got the device's version only once.
So my guess is - is it because the output power is not strong enough to support the operation, so I have to use something like a USB hub which has a strong and stable power?(I saw someone mentioned this and cannot find the comments any more).
Bt the way, all USB ports I mentioned above are directly on my laptop which means they get power directly from motherboard, so they should have strong and stable power to support my operations.
I have been stuck at this issue for the whole day, I really hope some friends can help me out.
Thank you very much in advance.
I've had like the same issue. While updating the firmware it threw me that message and I could not reach my Gadgeteer *Fez Hydra at all. I managed to solve it by attaching an external power supply to it. I use the USB Client DP (Dual Power) 1.3. This way you do need the power over USB part and you can safely update the firmware.
USB Client: https://www.ghielectronics.com/catalog/product/280
edit: If that doesn't solve your isse you might want to reset the Loader first. Which is given as a tip on the GHI website before updating the firmware.
Related
I am currently writing an OS based on ARMv8 processor. I want to find an emulator that acts like the processor so I can see my OS working or not and to check my work.
I am on windows 10. are there any emulators recommended ?
I searched SO but no answer. thanks.
Looks like QEMU version 2.1+ is what you want
the latest version of upstream QEMU (2.1) now includes full ARMv8 system emulation support. This means that users can use upstream QEMU to run a full 64-bit ARMv8-A kernel and filesystem, such as a 64-bit Ubuntu cloud image. This was no small endeavour as it involved emulating a completely new instruction set, exception model, CPU implementation, and more. The implementation was verified with a custom instruction verification tool (RISU) and was heavily reviewed upstream by an engaged and incredibly supportive upstream QEMU community.
source
I have a raspberry pi3 but I am having tremendous issues with trying to install win10 IOT on it. When I download the core and try to boot it I only get the "rainbow" screen. When installing noobs I dont even get the option for win10 IOT. Anyone else had problems with this? Will it work smoother on a raspberry pi2 rather then the pi3?
Im not asking if anyone know solutions for booting win10 IOT on pi3, I have tried most of it :) Just asking if anyone has better experiences using pi2 for it?
If you follow the link to Manually set up your IoT Core device Microsoft there explain how to install with a Windows computer.
If you are using UNIX however, there isn't much help for you. As an experienced Unix user who last used Windows seriously about six years ago I found it quite intimidating to have to
a) log into my Microsoft account (that I last used from a different continent)
b) sign up as a "Windows Insider"
Even after going through these hurdles I only stumbled across the ISO file by accident, and even then nothing for the Raspberry Pi.
This answer isn't given to help you achieve your aim, which I despair of doing, but to let you know that the whole process perplexed someone of considerable experience. I don't see myself using Win 10 for my Pis without buying a pre-configured SD card.
What you're going to need to do is follow this link and do what it says:
https://buildazure.com/2017/05/24/setup-raspberry-pi-with-windows-10-iot-core/
Basically:
Load up your microsd card onto the PC
Use the wizard
Insert card into the Pi
And boot it up.
i working in windows 10 iot core.
first time when i install windows 10 iot core i follow the following list.
how to install windows 10 iot core
follow the link.
i things your problem is solve...
I have installed Eucalyptus Cloud in a Box (Bundled with CentOS 6.4 64 bit)on an HP Probook 430 G1 laptop with the following processor specifications
Intel i7 4500u
Before Install I get the message "Unsupported Hardware of combination thereof detected".
Inspite of this I can still install Eucalyptus just fine.
However, after the first reboot and subsequent reboots I see a message
Detected CPU model 6 family 69
UNSUPPORTED HARDWARE device: Intel CPU Model
After this the machine does not go beyond the first loading screen.
1).Is this a problem with the new fourth generation Haswell architecture ?
2).And is there any solution to this apart from using another machine ?
3).What does CPU model 6 family 69 mean ?
4).Is there any way to know which specific hardware is unsupported ?
Below is the link that shows the supported hardware of Red Hat
https://hardware.redhat.com/laptop/Hewlett%20Packard/&quicksearch=
Thank you in advance. Any help will be greatly appreciated
Yes, I believe "Model 6 Family 69" is a 4th generation Haswell i7.
You should be able to add "unsupported_hardware" to your kickstart file, if that's when it's occurring.
I don't know, but here's Intel's information page for what I think is a typical 4th gen processor: http://ark.intel.com/products/76087/Intel-Core-i7-4750HQ-Processor-6M-Cache-up-to-3_20-GHz
You could look at the kernel source for the kernel you're using. Might be in arch/x86/kernel/cpu somewhere.
The "Feature" explained
http://fedoraproject.org/wiki/Anaconda/Features/WarnTaintedHardware
This says it should only affect the installer, so the "subsequent reboots" behavior you describe should not happen unless you're running the installer on every boot.
And a recent feature added to kickstart to allow it to boot unattended:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.4_Technical_Notes/
BZ#824963
A kickstart installation on unsupported hardware resulted in a dialog box asking for confirmation before proceeding with the installation process. As a consequence, it was not possible to perform a kickstart installation on unsupported hardware without any user input. To fix this bug, a new unsupported_hardware kickstart command has been added, which skips the interactive dialog warning when installing a system on unsupported hardware without user input.
First off I used to be an XP guy and I still have the copy that I bought back in 2002. I had to downgrade my computer to an old iMac I had in storage and the only copy that I have of XP (I really do not want to buy a new one) is the old copy. I installed into a fully formatted drive and then realised that this XP disc came out before service pack 1. Which means that there really is no support for this. Next I noticed that the ethernet driver is unrecognized (big shock) therefore I have no internet, so I cannot install using windows update. Therefore I do not have any updates (again this disc is very old) and no access to the internet.
I have another computer that I can burn discs off of and it has the internet but I will not have it for much longer.
The device I installed the XP on is an 20-inch iMac (Early 2006), 2.0 GHz Intel(R) CPU T2500 with 1.98GB RAM
Is it possible to update my machine and be able to do use it the way it should be?
How I managed it was that I downloaded found an executable version of SP1a and then updated the system by moving the file over, then I downloaded the service pack SP3 ISO, updated the system.
However it didn't fix the ethernet driver and since I had no idea what the controller's actual name nor the company that made it, I moved over the Auslogics System Information, did a diagnostics took the problem devices "Value" and did research in order to find the needed information, and got the driver and moved it over. Yay monotony.
I'm working on a Windows driver for a USB device and the installation has to override the built-in class driver from Microsoft, so that the device uses my driver.
The driver is self-signed but not WHQL signed. Installation is not a problem on Vista or Win7, where SetupAPI acknowledges the driver as signed and selects it as the preferred driver over the built-in class driver.
However, this does not work on Windows XP SP3. The SetupAPI log tells me that it finds the driver, but considers it untrusted. (Log excerpt: "Driver node not trusted, rank changed from 0x00000001 to 0x0000c001")
Previous answers to similar questions here on stackoverflow, and other places, suggest that WHQL signing is the only way for this to work on XP. Is that really the case, or are there any known workarounds?
Does anybody have any links to resources with information about workarounds, or a solution to the problem?
I appreciate any help on the matter.
Yes, this is really the case.
I might've mentioned a workaround we use in my project, but it's irrelevant for you, as your product is intended for the broad market and you cannot rely on your devices having a static Device Instance ID. (To maintain a "known" Device Instance ID, we use a filter driver on top of the USB hub. I'm only mentioning this because you might be curious about that "mysterious" workaround we use.)
By the way, maybe you could rewrite your driver as a device filter driver. They're not subject to the same WHQL limitations.
Edit: If you're willing to install your certificate into your customers' root certificate stores (a risky choice that might alienate your customers), there might be a solution for you:
Preinstalling WinXP USB drivers to be able to connect device without interaction