* change simulator svg

* change radio image

* Remove google fonts cdn

* change color of 'advanced' button

* font fix

* font fix 2

* display fix

* change fullsceen simulator bg

* Continuous servo

* handle continuous state

* adding shims

* update rendering for continuous servos

* fixing sim

* fix sig

* typo

* fix sim

* bump pxt

* bump pxt

* rerun travis

* Input blocks revision

- add Button and Pin event types
- merge onPinPressed & onPinReleased in new onPinEvent function
- create new onButtonEvent function

* update input blocks in docs and tests

* remove device_pin_release block

* Hide DAL.x behind Enum

* bring back deprecated blocks, but hide them

* shims and locales files

* fix input.input. typing

* remove buildpr

* bump V3

* update simulator aspect ratio

* add Loudness Block

* revoke loudness block

* Adds soundLevel

To be replaced by pxt-common-packages when DAL is updated.

* Remove P0 & P3 from AnalogPin

Co-authored-by: Juri <gitkraken@juriwolf.de>

2020-09-08 02:04:25 -07:00

3.9 KiB

Raw Blame History

Troubleshooting downloads from the Windows 10 App

~ avatar

Is the Windows App not downloading your program properly? Let's try to figure out why!

~

Step 1: Check your cable

Make sure that your @boardname@ is connected to your computer with a micro USB cable. You should see a MICROBIT drive appear in Windows Explorer when it's connected.

If you can see the MICROBIT drive go to step 2.

If you can't see the drive:

Make sure that the USB cable is working.

Does the cable work on another computer? If not, find a different cable to use. Some cables may only provide a power connection and don't actually transfer data.

Try another USB port on your computer.

Is the cable good but you still can't see the MICROBIT drive? Hmm, you might have a problem with your @boardname@. Try the additional steps described in the fault finding page at microbit.org. If this doesn't help, you can create a support ticket to notify the Micro:bit Foundation of the problem. Skip the rest of these steps.

Step 2: Check your firmware version

It's possible that the firmware version on the @boardname@ needs an update. Let's check:

Go to the MICROBIT drive.
Open the DETAILS.TXT file.
Look for a line in the file that says the version number. It should say Version: ...

If the version is 0234, you NEED to update the firmware on your @boardname@. Go to Step 3 and follow the upgrade instructions.

If the version is 0241, 0243 or higher, you have the right firmware. You can create a support ticket to notify the Micro:bit Foundation of the problem. Skip the rest of these steps.

Step 3: Upgrade the firmware

Put your @boardname@ into MAINTENANCE Mode. To do this, unplug the USB cable from the @boardname@ and then re-connect the USB cable while you hold down the reset button. Once you insert the cable, you can release the reset button. You should now see a MAINTENANCE drive instead of the MICROBIT drive like before. Also, a yellow LED light will stay on next to the reset button.
Download the firmware .hex file
Drag and drop that file onto the MAINTENANCE drive.
The yellow LED will flash while the HEX file is copying. When the copy finishes, the LED will go off and the @boardname@ resets. The MAINTENANCE drive now changes back to MICROBIT.
The upgrade is complete! You can open the DETAILS.TXT file to check and see that the firmware version changed to the match the version of the HEX file you copied.

~hint

If you want to know more about connecting the board, MAINTENANCE Mode, and upgrading the firmware, read about it in the micro:bit firmware guide.

~

Step 4: Wait for the driver updates

Once you've updated the firmware, Windows will detect the updated device and install the drivers necessary to enable communication with the @boardname@. This step happens in the background and may take a minute or two.

Step 5: Drag and drop a fresh .hex file

If different editors were used with this board, it may need a reset to bring it back to a known-good state. Do this by dragging a .hex file containing a simple program onto the drive. You can use the one here. Click on the Download icon below the blocks, then drag and drop the file onto the @drivename@ drive.

basic.forever(function() {
    basic.showString("OK")
})

3.9 KiB Raw Blame History