11 years ago.

windows 8.1 mbed update - anyone successful?

My newly-updated windows 8.1 machine refused to copy the file to the BOOTLOADER directory. It complained about not being able to find the file. Probably missing a driver, but not my area of expertise. I switched to a windows 7 machine, and it all went perfectly. If someone knows the magic spell to get it to work on WIndows 8.1, please post so others may benefit. Thanks!

Question relating to:

Hello Mark Reed,

the mbed team is aware of this issue. I believe it will be fixed soon.

posted by Martin Kojtal 04 Nov 2013

I`m waiting the result because my windows 8.1 can´t return to windows 8. I had used my FRDM-KL25Z, but now I´m stopped really and the visual software isn´t good to make real tasks.

posted by Davi Viotto 05 Nov 2013

Similar issue installing serial mbed driver under Windows 8.1 x64.

While trying to install "mbedWinSerial_16466.exe" the behavior of the installation routine differs from the usual one: although the mbed is not connected to USB, the routine doesn't wait for the mbed USB connection and shows a message "The driver was installed successfully". Unfortunately, it's not true: after the USB onnection has been established, the device manager shows a yellow exclamation sign at "mbed Composite Device" and neither something like "mbed Mass Storage" nor "mbed Serial Port" appears as device. So, mbed cannot be programmed and mbed virtual serial port doesn't exist.

Regards, Marcin

posted by Marcin Krajka 07 Nov 2013

Test code posted 4-dec-2013 by Martin Kojtal allowed me to successfully download & run code from 8.1. I did use a Windows 7 machine to update the bootloader on the KL25Z with Martin's code. Thanks!

posted by Mark Reed 22 Dec 2013

2 Answers

10 years, 11 months ago.

i have win 8.1 x64, I installed the mbedwinserial and my mbed work fine.

10 years, 11 months ago.

Tried to upgrade today my FRDM-KL25Z to mbed 2.0 on Windows 8.1 x64 and I have run into the same problems as Mark and had to use Window 7 to upgrade the firmware which worked as advertised.

Now I am trying to use Windows 8.1 for development and have a strange behavior with FRDM-KL25Z board. MBED disk keeps appearing and disappearing on it's own. When it appears it has new text file "fail.txt" with a single line TIMEOUT.

NXP's mbed LPC1768 works with no problems on the same computer.

I have also tested it with pyOCD and it works until -- TEST RESET -- where it crashes and hangs for a while, see below.

pyOCD output

READ16/WRITE316
write16 0x9859 at 0x20000003
read16 at 0x20000003: 0x9859

READ8/WRITE8
write8 0xDC at 0x20000002
read8 at 0x20000002: 0xDC


------ TEST READ / WRITE MEMORY BLOCK ------
TEST PASSED


------ TEST RESET ------
Unknown exception: SWD Fault
Traceback (most recent call last):
  File "basic_test.py", line 165, in <module>
    board.uninit()
  File "C:\Python27\lib\site-packages\pyOCD\board\board.py", line 55, in uninit
    self.target.resume()
  File "C:\Python27\lib\site-packages\pyOCD\target\cortex_m.py", line 427, in re
sume
    if self.getState() != TARGET_HALTED:
  File "C:\Python27\lib\site-packages\pyOCD\target\cortex_m.py", line 418, in ge
tState
    dhcsr = self.readMemory(DHCSR)
  File "C:\Python27\lib\site-packages\pyOCD\target\cortex_m.py", line 224, in re
adMemory
    return self.transport.readMem(addr, transfer_size)
  File "C:\Python27\lib\site-packages\pyOCD\transport\cmsis_dap.py", line 140, i
n readMem
    [addr])
  File "C:\Python27\lib\site-packages\pyOCD\transport\cmsis_dap_core.py", line 2
04, in dapTransfer
    raise ValueError('Transfer not completed')
ValueError: Transfer not completed