stm32f429 USB CDC VCP detection - stm32

[guys i have installed the VCP driver and have loaded the code of USB_CDC in my stm32f429. but the VCP port is not visible in device manager. instead "unknown usb device,(device descriptor request failed)" is shown in device manager, as shown in figure. whom link is given below. kindly help me to solve this issue.
http://i.stack.imgur.com/qRzed.png ]1

Are you sure that you installed the right version of the driver (32 vs 64 bit)?
If you are, then try to increase the heap size in your project (it is located in the startup_stm32f429xx.s file).

Related

Where Can i find an emulator to test my operating system for ARMv8?

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

Cannot update FEZ Hydra firmware: Device is not connected or not responding

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.

Eucalyptus Cloud not booting

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.

Windows Phone 8 Emulator- Deployment Error

I am using Visual Studio 2012 in Windows 8. I have set up Windows Phone 8 sdk and everything was working fine until I made some changes to network settings. First I was unable to connect to internet through the emulator. But I managed to set up internet connectivity by sharing the physical connection with my USB modem. However now I'm having problems in launching the emulator which has been working absolutely fine before. When I run the emulator separately (via Hyper-V manager) everything is okay and I can connect to internet but the problem is when I launch the emulator from Visual Studio 2012.
A related question can be found here [1] but the answer is not what I am looking for. Is there a way to fix this issue without running the emulator on a virtual machine?
Thanks
1 Windows Phone 8 Emulator Deployment Issue with Internet
When I ran into this it was caused by my anti-virus software. Specifically, the 'AVG network filter driver' was enabled for the Hyper-V virtual adapter. Unchecking this option fixed the problem for me.
Interference from other virtualization or networking software and drivers outlines specifically which items should be checked for the virtual adapter.
The debugger runs over a TCP/IP connection so if you've changed the HyperV network settings it's possible you've isolated the VM from the host so it cannot open a connection. Try and reset the connection back to it was before you changed it to get the Internet working and this should re-store your debugger.
Edit the .VMX file in your virtual machine folder
vhv.enable = "TRUE"
hypervisor.cpuid.v0 = “FALSE”
and save it.
A little late, but I had to face the same problem and found this solution (all the other solutions didn't work for me)
1.go to network and sharing center
2.go to change adapter setting
3.go to v Ethernet (internal Ethernet port windows phone emulator internal switch)
4.right click it and enable it(if already enabled then disable and enable it again).

How to debug CUDA using eclipse Nsight with only one GPU

I'm getting an error: "all cuda devices are used for display and cannot be used while debugging"
(Using Ubuntu)
Is there ANY way to use Nsight eclipse with only one GPU for debugging?
I have seen solutions like
"sudo service lightdm stop"
to kill X but that kills Nsight eclipse too so what's the point?
Update: Since it is not possible to debug with the same GPU that runs X, I have to ask: How does one go about using ANOTHER computer in his home network to "remotely" access Ubuntu in such a way that the X desktop rendering will be performed by the Guest computer while letting the host GPU run the debugger?
In general, it's not supported to debug on the same GPU that is hosting an X display. From the nsight getting started guide: "A GPU that is running X11 (on Linux) or Aqua (on Mac) cannot be used to debug a CUDA application and will be hidden from the application ran in the debugger. Such GPU can still be used for profiling GPU applications. "
I believe there is actually different behavior amongst different window managers, however. I have a laptop with Quadro1000M and RHEL 6.2 (with GNOME), with CUDA 5.0, and I am able to get into the debugger in nsight EE (Project...Build Project followed by Run...Debug). At that point I can step through and set breakpoints in host code. And if I run the code to completion I get proper output. However, you still can't debug device code. If you set a breakpoint in the device code (and hit that breakpoint), you will hang the X session.
EDIT: CUDA 5.5 and beyond now support the ability to debug on a single cc3.5 or higher GPU.
It seems that you can use CUDA 5.5 to debug CUDA programs in a machine with only one GPU.
See section 1.7.3.2. CUDA-GDB of CUDA_Toolkit_Release_Notes
Another approach which might work is to use the onboard video output for the display.
That way you use the onboard graphics for the display and the GPU for debugging.
For this you have to:
Go to BIOS and change the primary display adapter to "On-Board" (this varies from manufacturer to manufacturer)
Physically connect you display to the on-board display output feed
Restart and then run Nsight
If you are using a system with no on-board graphics, then you are out of luck!
This guy here has been able to get it up and running in Windows with Visual studio and Nsight plugin.
P.S. You would probably need to edit your xorg.conf to make X use onboard graphics instead of your Nvidia GPU.