I have raspberry Pi 3 with Windows IoT 10 Core.
I flashed 17763 build using Dashboard.
Everything was working properly, even debugging from Visual Studio 2017, but in some moment, I found my Raspberry with boot menu:
[1] Default EFI Boot Application
[2] Default EFI Boot Application
[3] Shell
[4] Boot Manager
Start: _
I connected keyboard via USB, I press 1, but it no response...
The keyboard was working properly with Raspberry before.
Is there some other solution except reflashing the SD card?
So, only one solution I found, is to reflash the SD card.
Related
I try to run Windows IoT Core 10 B+ over Raspberry Pi 3 B+.
The plate is new. The OS I downloaded from here: Windows IoT 10 B+, I used:
RaspberryPi 3B+ Technical Preview Build 17661
I user this manual to install the OS to teh flash.
I have 4 INCH HDMI LCD with Touch Pad connected to the plate.
For connect the LCD I was need to modify original config (g:\config.txt) file - see code below.
But the problem not in config, when I use original config, I have no device detected in Dashboard. If I use modified config, I have monitor working, but have blue screen.
I have follow drives after FFU uploading:
USB Drive F:
EFIESP G:
MainOS H:
Data J:
I searched for logs and important files, and didn't found much:
j:\FirstBoot.Complete
Some DUMP like files, however, it is unable to open it in Visual Studio as DUMP files:
j:\DUMP0c15.tmp
j:\DUMP0c35.tmp
j:\DedicatedDumpFile.sys
Follow directories, however it are empty:
j:\Logfiles\WMI\RtBackup\
j:\CrashDump\
h:\Windows\tracing\
h:\Windows\LiveKernelReports\
h:\Windows\system32\winevt\Logs\
The modified content of: g:\config.txt:
init_uart_clock=16000000 # Set UART clock to 16Mhz
kernel_old=1 # Load kernel.img at physical memory address 0x0
safe_mode_gpio=8 # A temp firmware limitation workaround
max_usb_current=1 # Enable maximum usb current
gpu_mem=32 # Set VC to 32MB, ARM DRAM to (1008-32)MB
hdmi_force_hotplug=1 # Enable HDMI display even if it is not connected (640x480)
core_freq=250 # Frequency of GPU processor core in MHz
framebuffer_ignore_alpha=1 # Ignore the alpha channel for Windows.
framebuffer_swap=1 # Set the frame buffer to be Windows BGR compatible.
disable_overscan=1 # Disable overscan
hdmi_group=2 # Use VESA Display Mode Timing over CEA
hdmi_mode=87 # 5 inch screen
hdmi_cvt 480 800 60 6 0 0 0 # 5 inch screen
dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=0,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900
display_rotate=3
This is screenshot of blue screen:
As I see, there is notification about: BAD_SYSTEM_CONFIG_INFO
I read troubleshooting page and some other information.
I have follow questions:
What are the drives responsible for: G:, F:, J:, H: ?
Where can I find boot logs in the Windows IoT file system?
Where can I find more documentation about Windows IoT OS architecture and its system's directory tree?
What can be the problem?
PS: I have successful expirianse to run Windows IoT Core 10 on Raspberry Pi 3.
Please note there is no official release version of Windows IoT Core for Raspberry Pi 3B+. There is only one insider preview version 17761 suppose to working on 3B+. So use the image you download without any modification to see if it works.
But th eproblem not in config, when I use original config, I have to
device detected in Dashboard. If I use modified config, I have monitor
working, but have blue screen.
If you mean you can't detected the device in Dashboard please connect a display via HDMI to see the system boot up or not. For me "BAD_SYSTEM_CONFIG_INFO" seems due to you change the default settings so cause the system boot fails.
What are the drives responsible for: G:, F:, J:, H: ?
MainOS: OS and OEM-preloaded apps.
EFI: Fixed-size partition with the boot manager, boot configuration database.
Data: User data partition, user registry hives, apps, apps data.
More detailed information please refer to "IoT Device Layout".
Where can I find boot logs in the Windows IoT file system?
You may need use WinDbg to get boot information when the system can boot up successfully.
Where can I find more documentation about Windows IoT OS architecture
and its system's directory tree?
It seem no such dedicated document. But you can reference the following documents:
"Windows kernel", "Architecture of Windows 10", "An overview of Windows 10 IoT", "Windows file sharing"
Windows IoT Core is a Windows 10 edition for IoT. It has many commonalities with Windows 10 other editions and has some limitations due to its device limited resource. So you can compare Windows 10 IoT Core and a full version Windows 10 like Windows 10 IoT Enterprise to understand it.
I am developing on an ARM Mbed board which connects to my Windows laptop over USB. I've just moved to a new Dell laptop running Win 10 [from a Dell laptop running Win 7] and I find that the laptop resets my development board every 15 minutes.
There are two things that will cause the ARM Mbed board to reset:
powering down/up the USB connection
sending "break" via the USB serial driver.
When the reset occurs there is nothing of note in the Windows event logs. I have all of the "allow Windows to power me down" boxes unticked on the USB hubs in System devices and in the Control Panel power management options.
Does anyone have any suggestions on how I (a) debug what's going on or (b) fix/workaround the problem? I've not yet tried connecting via a powered USB hub, will do that next...
I had the same issue using a FRDM-K64F running mBed and communicating over a USB COM port to a Windows 7 Dell machine. The communication would sometimes drop out. As #Rob suggested, uninstalling the Dell Support Assist Agent completely fixed the issue.
Just adding this answer as it was very difficult to find any information using google.
Another note in support of this solution for google...
I have a Dell 5480 running Windows 10, and started using from ST Nucleo boards on it. I've used the exact same boards at work, with no problems. Every 15minutes or so the board was reset.
I tried disabling the Dell Support Assist services but this did not seem to fix the problem.
Removing the programs did make the Nucleo work.
I have a problem with Windows IoT startup app, I choose my app to be startup. This works good but when I reset Rpi 2 or 3 via external arduino through RUN pin windows reboots and start my app but after approximately 30 seconds app is replaced by default IoT core app and removed from startup too. Do you know where is the problem?
Thanks
Unfortunately, I have to deal with J2ME (which I consider ancient technology these days) on Sony Ericsson J108i (aka Cedar).
Unfortunately I've failed to configure on-device debugging. I've done the following:
enabled Java developer mode in service settings
configured USB -> Advanced -> Internet access -> Via computer
installed J2ME SDK 2.5.0.6
disabled the Windows firewall
tried the whole procedure on both Windows XP and Windows 7
Unfortunately, Connection Proxy fails to connect to the device. The network interface is there, named 'Sony Ericsson Device 1039 USB Ethernet Emulation (NDIS 5)', but when I try to connect, the following is logged:
[18.03.12 13:23:45] Getting device ip. Failed to get deviceip for interface(Sony Ericsson Device 1039 USB Ethernet Emulation (NDIS 5) - Sterownik miniport Harmonogramu pakietów). Trying to get it from Connection Proxy settings(sdkme.properties). java.lang.RuntimeException: Unable to connect to the SEMC SDK Service1.
[18.03.12 13:23:45] Getting device ip. No device for interface=Sony Ericsson Device 1039 USB Ethernet Emulation (NDIS 5) - Sterownik miniport Harmonogramu pakietów
It actually looks like the interface is never assigned the correct IP. I've tried assigning IP manually, but it failed too (perhaps I did it incorrectly - the documentation is not really verbose here).
Any idea what I do wrong? Any success stories with on-device debugging using this particular phone?
I managed to get my Cedar device working on Vista 32-bit SP2:
1. First of all, make sure you're not using jdk7uX (otherwise you have to install MSVC 10 redistributable pack to make SEMC_SDK_Service start properly).
2. Edit SDK_Root/OnDeviceDebug/lib/sdkme.properties, set ipprovider.rebindOnConnect: true
(it's false by default), then uncomment and set proxy.device.ip: 192.168.8.2 and proxy.local.ip: 192.168.8.1 (both are commented out and empty by default)
3. Run SDK_Root/OnDeviceDebug/bin/restart_service.cmd
4. (Re)connect your Cedar device
5. Wait about a minute
6. Run SDK_Root/OnDeviceDebug/bin/restart_service.cmd
7. Run arp -a in console and ensure your interface is using 192.168.8.*, this could also take about a minute
8. Restart connection proxy and connect to your phone, everything should be OK
9. You should repeat steps 4-8 after each Windows start
I would like to create my Kinect development environment and am contemplating using iMac as the box with Windows 7 installed as dual boot and/or parallels.
Has anyone tried this configuration earlier and does it work?
Running Bootcamp(dual boot) works with windows 7/8 Parallels does not.
I have a macpro 1,1 and a mac air both work with bootcamp(dual boot).
The only thing that could cause it not to work is the USB configuration. Kinect requires that it be connected to a USB host controller and not a hub. I believe all of the iMac's USB ports are host ports so I don't believe this to be an issue. If you use the Kinect Sensor Chooser control built into the WPFViewers sample app it will tell you if that particular problem arises (insufficient bandwidth).
Parallels will not work with the SDK at the time of this writing due to driver. Kinect is not an official USB device and the driver requires direct communication with the Kinect. I hoped that this would be resolved with the official Kinect for Windows hardware but alas it was not.
You might want to look at native OSX Kinect development using OpenKinect
http://openkinect.org/wiki/Getting_Started
If you don't want to have to write all the image processing code yourself, and are working in C#, you could start with the Accord library:
http://accord-net.origo.ethz.ch/