I recently got a new Mbed board - this one is MTS Dragonfly. I can't get flash-disk to show up correctly, and I am wondering if I have got a DOA module, or I am doing something wrong. Does this happens to other Mbed boards?
I have installed drivers from manufacturer website and do have a working serial connection, which defaults to the cellular module. However the flash disk does not show up correctly. Unlike other Mbed boards, I am greeted with a message "please insert disk" and I see no file system.
Interesting part is that the mbed microcontroller - that is the one doing the programming - is on a separate development / breakout board. The target is a separate module that is meant to be used in production.
If I do not insert the target into the development board, and connect development board to the PC, I get the same error. I have looked at diskpart, and when no target is present, it shows up as a 16 KB disk with no partitions or volumes.When the module is inserted, diskpart reports ~512 KB of space, also with no partitions. Thus I guess that I am plugging in the module correctly.
I have seen user discussions for a 'bricked' mbed board (damaged file-system), and this situation looks similar to me.
I tried diskpart to create a partition, or clean the disk, and it throws an IO error.
This question on mbed site
I just tested all of my Mbed boards and discovered that this is a regression in Windows 10 anniversary update.
MTS-Dragonfly and another board, Delta DFCM-NNN40, do not show up with a valid partition on any of my Windows 10 machines. I have a couple of FRDM boards and those work fine.
I tested Ubuntu, and it has no issue displaying the disk drives or programming the boards. I have not tested other versions of Windows. A workable solution is is to use Ubuntu in VirtualBox, and pass it control of the USB device.
Related
I'm trying to emulate STM32F429I discovery board using qemu & eclipse IDE. I got the blinky example running with the led turning on and off on the graphics screen but I have tried an example to run the on-board screen and it doesn't seem to be running, Is it supported? Also, many drivers fail when simulated with qemu (sdram, rcc, ...) How can I know exactly what peripherals that are fully supported?
Here's the part of documentation about the board, What is meant by "FP not emulated" anyway?
Note: Why this question is not off-topic
Some people seem to think this question is off-topic, and it would be better suited for Super User. Please give me a chance to explain why that's not the case.
The question is not about "general computing hardware" but about "embedded software". In the topic of "embedded software", there are tons of questions on StackOverflow related to OpenOCD, a popular open-source tool to connect your computer to embedded software development boards. All these questions are considered totally okay for StackOverflow. My question on this page is about PyOCD - an emerging OpenOCD alternative. So if you vote to close this question, then please also vote to close the 565 (!) other questions about OpenOCD too ;-)
I've got a NuMaker-M032SE V1.3 board from Nuvoton that I'm trying to flash/debug with PyOCD. It's my first time I'm experimenting with PyOCD and with Nuvoton chips. Unfortunately, PyOCD cannot find the device. I'll go step-by-step through the whole procedure. Please tell me what I did wrong.
1. My system
I'm running 64-bit Windows 10 on my desktop computer. I've got Python 3.8 and recently installed the latest PyOCD development version from a cloned GitHub repository (see https://github.com/mbedmicro/pyOCD).
2 Install Microcontroller board
Note: this paragraph is simply to show you the background situation, before I move on to explain the actual problem I got with PyOCD
I've got a Nuvoton NuMaker-M032SE V1.3 microcontroller board:
This board has a Nu-Link2-Me V1.0 probe on the right side. The first time I connect my board to my computer nothing really happened. So I figured out I had to install the Nuvoton ICP tool that comes with the Nu-Link USB Driver 1.6:
You can download the Nuvoton ICP tool here: https://www.nuvoton.com/hq/support/tool-and-software/development-tool-hardware/programmer/
When I first start the sofware, I see this:
And I get a request to update the firmware on the Nu-Link2-Me V1.0 probe:
I click OK and wait for the firmware update to complete. I plug out and back in the board. Windows clearly notices the device:
I can also see the device in my Control Panel > Device Manager. It's listed under Universal Serial Bus Controllers as Nuvoton Nu-Link2 USB:
3 Prepare PyOCD
PyOCD has a few built-in targets. But not the Nuvoton chip I got. So I consulted the documentation at https://github.com/mbedmicro/pyOCD/blob/master/docs/target_support.md and learn that I need to download a pack from http://www.keil.com/dd2/pack/ . That's where I download the Nuvoton ARM Cortex-M NuMicro Family Device Support pack:
Because I downloaded the pack manually, I know that I'll have to add the parameter --pack="C:/path/to/pack/Nuvoton.NuMicro_DFP.1.3.5.pack" to every PyOCD command, to ensure that PyOCD can access this pack whenever it needs to.
4. Connect PyOCD with Nuvoton board
I believe my microcontroller board is properly installed to go on to the final step: connect PyOCD to the Nuvoton microcontroller board.
First I want PyOCD to find the board. I issue the following command in a Windows console:
$ pyocd list --pack="C:/path/to/pack/Nuvoton.NuMicro_DFP.1.3.5.pack"
Unfortunately, I get the response:
No available debug probes are connected
I tried a few times, both with and without the --pack parameter. I always get the same error message.
Note:
I had expected to see something like:
# Probe Unique ID
---------------------------------------------------------------------------
0 ARM CMSIS-DAP v1 000000800a0c882800000000000000000000000097969902
That's the output I get when I issue the $ pyocd list command and I have my SWDAP probe connected to my computer. The SWDAP is the official probe from ARM (see https://os.mbed.com/components/SWDAP-LPC11U35/) that runs the DAPLink firmware (see https://github.com/ARMmbed/DAPLink).
I got a reply from Nuvoton. Apparently the NuMaker-M032SE V1.3 board is not yet supported in PyOCD at the time of writing (02 Dec 2019). At the moment, only NuMaker M252/M263 boards are supported.
Nuvoton will make efforts to support these boards in PyOCD too, in the future.
I have my processing code in dev/processing and my Arduino code put itself in Documents/Arduino.
However, whenever I get into one environment, it changes the most recent directory for the other because Arduino is written in processing.
Is there any quick way to disconnect the two environments so that they don't use the same location for "most recent directory?" I don't know whether the mechanism is a file, a registry entry or what, but I'm on Windows 8.1
I am using both Arduino IDE as well as Processing 2.1.2 in Windows 7 environment. It doesn't change the directory.
Since you are using Windows 8.1 (which is recently released), you may face very weird problems as those softwares are not tested on those OS. You will find errors for even other softwares that are designed before Windows 8.
I have the same problem with this post: MSDN Post. It seems nobody answered with a working solution on that thread.
The symptoms:
Kinect SDK 1.5 installed.
The Kinect device is recognized and drivers seem to be loaded correctly.The speech demo works correctly.
Skeleton Viewer shows "Could not enable Skeleton Tracking".
Shape Game starts, but does not track anything.
Kinect Explorer starts the small windows only showing that it has connected to the Kinect, the black window does not open. If I close the white window, the kinect explorer is still running I have to quit it through the task manager.
When I unplug and plug the USB after I open Kinect explorer; it says insufficient bandwith.
I tried:
Updated BIOS.
Updated motherboard software. (ASUS Maximus IV Gene-Z, Gen3)
Removed all USB's and plugged them all.
Restarted windows. (several million times)
I uninstalled and re installed. Kinect SDK 1.0. (but everything is the same)
My OS: Windows 7 64 bit Ultimate.
I have been struggling with this for 1 complete day. Any suggestions will be greatly appreciated.
EDIT: I tried my Kinect device on another computer (laptop), and it works.
If the Kinect shares a USB Controller with other devices, a problem such as yours can happen easily.
Try the following: Unplug all USB devices, then connect only the Kinect to your computer. If you have USB mouse and/or keyboard, plug those into a different set of ports (for example front usb ports if you have the Kinect plugged into the back of the computer). Then, try running the SDK's sample applications.
Should this approach fail, something might be wrong with your USB controller(s).
One more option: Try running the sample applications on a different Windows computer, preferably a laptop of some type, since you won't need to plug in any additional USB devices.
If this approach fails, your Kinect is most likely defective. In which case you can get a replacement or refund from your retailer, if the purchase didn't happen too long ago.
Best of luck to you!
I finally was able to made my kinect work. This MSDN Discussion helped me to do that.
The solution:
Uninstall all Kinect Drivers from Control Panel.
Reinstall Kinect SDK.
(IMPORTANT) Make sure to skip getting drivers from windows update during driver installation.
And yay! It works beautifuly ..
The same happened with me; I noticed a windows update related to Kinect, installed it. Kinect stopped working. Installing SDK from May 2d 2012 didn't fix the problem. Rolling back to February 2010 SDK didn't fix it either. At first I guessed that Microsoft doesn't want us to use Kinect for Xbox any more, and this is their way of telling us to buy Kinect for Windows... well, may be - but in my case Kinect Camera driver was somehow updated to Version 1.5 (May 2, 2012), while everything else was on version 1.0. Installing original driver fixed the problem.
I think this is a common problem for all developers using Windows CE 6.0 operating systems on specific hardware. I have a client that needs a custom operating system for its ICOP PDX-089T PC with Touch panel, that is based on DM&P SoC CPU Vortex86DX-1GHz.
I do not have the hardware with me, so every time I make a change I have to send at least the NK.bin file, or the whole ghost image to the client to make the tests for.
Is there any way to build a custom Windows CE emulator to add it to Visual Studio 2005 for testing or may be a custom virtual machine to launch it through VMWare or Virtual PC?
I tried some guidelines from the internet to build one, but every effort in making one resulted in hanging up my PC.
Does anybody have similar needs and some solution?
Note: The emulator I need is for Vortex86DX processor and ICOP board.
Microsoft abandoned the x86 Emulator some time ago, choosing to support only an ARM emulator (the BSP ships in the box with Platform Builder 6.0). This means that you can't create an emulator for the x86 processor, though I'm hard-pressed to think of a scenario where you'd really need to and where just getting hardware isn't a better solution for anyway.
There is a BSP for doing Virtual PC OS builds that would run on x86. It's not had much activity in some time, and I've never tried it, so YMMV.