How Long Does Safe Mode Take To Load Windows 7

From time to time, you volition run into issues when working with CircuitPython. Here are a few things you lot may see and how to resolve them.

As CircuitPython development continues and there are new releases, Adafruit will stop supporting older releases. Visit https://circuitpython.org/downloads to download the latest version of CircuitPython for your board. You must download the CircuitPython Library Package that matches your version of CircuitPython. Please update CircuitPython and so visit https://circuitpython.org/libraries to download the latest Library Packet.

Always Run the Latest Version of CircuitPython and Libraries

Equally CircuitPython development continues and there are new releases, Adafruit volition stop supporting older releases. You demand to update to the latest CircuitPython..

You need to download the CircuitPython Library Packet that matches your version of CircuitPython. Please update CircuitPython and then download the latest bundle.

As new versions of CircuitPython are released, Adafruit will stop providing the previous bundles equally automatically created downloads on the Adafruit CircuitPython Library Package repo. If you must continue to use an earlier version, you can still download the appropriate version of mpy-cross from the particular release of CircuitPython on the CircuitPython repo and create your ain uniform .mpy library files. However, information technology is all-time to update to the latest for both CircuitPython and the library bundle.

I accept to keep using CircuitPython five.ten or earlier. Where can I find compatible libraries?

Adafruit is no longer edifice or supporting the CircuitPython 5.10 or earlier library bundles. You are highly encourged to update CircuitPython to the latest version and use the current version of the libraries. Withal, if for some reason you cannot update, links to the previous bundles are available in the FAQ.

Bootloader (boardnameBOOT) Bulldoze Not Nowadays

You lot may have a dissimilar board.

Simply Adafruit Express boards and the SAMD21 non-Express boards send with the UF2 bootloader installed. The Feather M0 Basic, Feather M0 Adalogger, and similar boards use a regular Arduino-uniform bootloader, which does non show a boardnameBOOT drive.

MakeCode

If yous are running a MakeCode program on Excursion Playground Express, press the reset push but in one case to go the CPLAYBOOT drive to show up. Pressing it twice will not work.

MacOS

DriveDx and its accompanything Saturday SMART Commuter tin interfere with seeing the BOOT drive. Run across this forum mail for how to fix the trouble.

Windows 10

Did you install the Adafruit Windows Drivers package by mistake, or did you upgrade to Windows 10 with the driver package installed? You don't demand to install this package on Windows 10 for most Adafruit boards. The old version (v1.5) can interfere with recognizing your device. Get to Settings -> Apps and uninstall all the "Adafruit" commuter programs.

Windows 7 or 8.ane

To use a CircuitPython-uniform board with Windows 7 or 8.1, you lot must install a driver. Installation instructions are available here.

It is recommended that you upgrade to Windows 10 if possible; an upgrade is probably yet free for you. Check hither.

The Windows Drivers installer was last updated in Nov 2020 (v2.5.0.0) . Windows seven drivers for CircuitPython boards released since then, including RP2040 boards, are not yet available. The boards work fine on Windows 10. A new release of the drivers is in process.

You should now be done! Test by unplugging and replugging the board. You should see the CIRCUITPY bulldoze, and when you double-click the reset button (single click on Excursion Playground Limited running MakeCode), you should run across the advisable boardnameKick bulldoze.

Let us know in the Adafruit support forums or on the Adafruit Discord if this does not work for you!

Windows Explorer Locks Up When Accessing boardnameBOOT Bulldoze

On Windows, several third-party programs that can cause issues. The symptom is that you try to access the boardnameKicking drive, and Windows or Windows Explorer seems to lock upward. These programs are known to crusade trouble:

AIDA64: to fix, stop the program. This problem has been reported to AIDA64. They acquired hardware to exam, and released a beta version that fixes the problem. This may accept been incorporated into the latest release. Please let us know in the forums if you test this.
Hard disk Sentinel
Kaspersky anti-virus: To fix, you may need to disable Kaspersky completely. Disabling some aspects of Kaspersky does not always solve the problem. This problem has been reported to Kaspersky.
ESET NOD32 anti-virus: There have been problems with at least version ix.0.386.0, solved by uninstallation.

Copying UF2 to boardnameKicking Drive Hangs at 0% Copied

On Windows, a Western DIgital (WD) utility that comes with their external USB drives can interfere with copying UF2 files to the boardnameBOOT drive. Uninstall that utility to fix the problem.

CIRCUITPY Drive Does Not Appear or Disappears Quickly

Kaspersky anti-virus can cake the appearance of the CIRCUITPY drive. There has not notwithstanding been settings change discovered that prevents this. Complete uninstallation of Kaspersky fixes the problem.

Norton anti-virus can interfere with CIRCUITPY. A user has reported this problem on Windows seven. The user turned off both Smart Firewall and Auto Protect, and CIRCUITPY then appeared.

Sophos Endpoint security software tin cause CIRCUITPY to disappear and the BOOT drive to reappear. It is non clear what causes this behavior.

Device Errors or Bug on Windows

Windows can become confused most USB device installations. This is particularly true of Windows seven and 8.1. Information technology is recommended that you upgrade to Windows ten if possible; an upgrade is probably still complimentary for you lot: encounter this link.

If not, try cleaning up your USB devices. Use Uwe Sieber's Device Cleanup Tool. Download and unzip the tool. Unplug all the boards and other USB devices yous desire to clean up. Run the tool as Administrator. You volition see a listing similar this, probably with many more devices. It is listing all the USB devices that are not currently attached.

Select all the devices you desire to remove, and then press Delete. Information technology is usually condom simply to select everything. Whatsoever device that is removed volition go a fresh install when you plug it in. Using the Device Cleanup Tool also discards all the COM port assignments for the unplugged boards. If you lot have used many Arduino and CircuitPython boards, you have probably seen higher and higher COM port numbers used, seemingly without end. This will fix that problem.

Series Console in Mu Not Displaying Annihilation

At that place are times when the serial console will accurately not display anything, such as, when no code is currently running, or when code with no serial output is already running before yous open the console. However, if you find yourself in a state of affairs where y'all feel it should exist displaying something like an error, consider the following.

Depending on the size of your screen or Mu window, when you open the serial panel, the serial panel panel may be very small. This tin be a problem. A basic CircuitPython error takes ten lines to display!

Car-reload is on. Only save files over USB to run them or enter REPL to disable. code.py output: Traceback (most recent call last):   File "code.py", line 7 SyntaxError: invalid syntax    Press any key to enter the REPL. Use CTRL-D to reload.

Car-reload is on. But save files over USB to run them or enter REPL to disable. code.py output: Traceback (most recent call last):   File "lawmaking.py", line vii SyntaxError: invalid syntax    Press whatsoever key to enter the REPL. Utilise CTRL-D to reload.

More than complex errors take even more than lines!

Therefore, if your serial console console is v lines tall or less, you may merely see blank lines or blank lines followed by Press any key to enter the REPL. Use CTRL-D to reload.. If this is the case, you lot demand to either mouse over the top of the panel to utilise the option to resize the serial console, or utilise the scrollbar on the right side to scroll upwards and discover your message.

This applies to any kind of serial output whether it be mistake messages or print statements. And so before you commencement trying to debug your trouble on the hardware side, be sure to check that you haven't but missed the serial messages due to serial output console acme.

lawmaking.py Restarts Constantly

CircuitPython volition restart lawmaking.py if yous or your computer writes to something on the CIRCUITPY drive. This feature is called auto-reload, and lets you test a alter to your program immediately.

Some utility programs, such as backup, anti-virus, or disk-checking apps, will write to the CIRCUITPY as part of their operation. Sometimes they practise this very oft, causing constant restarts.

Acronis True Prototype and related Acronis programs on Windows are known to cause this trouble. It is possible to prevent this by disabling the "Acronis Managed Machine Service Mini".

If you cannot cease whatever is causing the writes, you tin disable motorcar-reload past putting this code in boot.py or code.py:

import supervisor  supervisor.disable_autoreload()

import supervisor  supervisor.disable_autoreload()

CircuitPython RGB Condition Low-cal

Near all CircuitPython-capable boards have a unmarried NeoPixel or DotStar RGB LED on the board that indicates the status of CircuitPython. A few boards designed earlier CircuitPython existed, such equally the Feather M0 Bones, practice non.

Circuit Playground Express and Excursion Playground Bluefruit have multiple RGB LEDs, but do Non have a status LED. The LEDs are all dark-green when in the bootloader. In versions before 7.0.0, they do NOT bespeak any status while running CircuitPython.

CircuitPython seven.0.0 and Later

The status LED blinks were changed in CircuitPython seven.0.0 in gild to save bombardment power and simplify the blinks. These blink patterns will occur on single color LEDs when the board does not have any RGB LEDs. Speed and blink count too vary for this reason.

On first upwards, the LED will blink YELLOW multiple times for 1 2d. Pressing reset during this time volition restart the board and then enter safe fashion. On Bluetooth capable boards, after the yellow blinks, in that location will be a set of faster blueish blinks. Pressing reset during the Blue blinks will clear Bluetooth information and get-go the device in discoverable mode, then it can be used with a BLE code editor.

Once started, CircuitPython volition blink a pattern every 5 seconds when no user lawmaking is running to bespeak why the code stopped:

1 Greenish blink: Code finished without mistake.
two Cherry blinks: Code ended due to an exception. Bank check the serial panel for details.
iii YELLOW blinks: CircuitPython is in rubber mode. No user code was run. Bank check the series console for safe mode reason.

When in the REPL, CircuitPython will set up the condition LED to WHITE. You can change the LED color from the REPL. The status indicator will not persist on not-NeoPixel or DotStar LEDs.

CircuitPython 6.3.0 and earlier

Here's what the colors and blinking mean:

steady Dark-green: lawmaking.py (or code.txt, principal.py, or main.txt) is running
pulsing Greenish: code.py (etc.) has finished or does non exist
steady YELLOW at start up: (4.0.0-blastoff.5 and newer) CircuitPython is waiting for a reset to indicate that it should start in safe style
pulsing YELLOW: Circuit Python is in safety manner: information technology crashed and restarted
steady WHITE: REPL is running
steady Blueish: boot.py is running

Colors with multiple flashes following indicate a Python exception and and then indicate the line number of the error. The colour of the first flash indicates the type of error:

GREEN: IndentationError
CYAN: SyntaxError
WHITE: NameError
Orange: OSError
Majestic: ValueError
YELLOW: other fault

These are followed past flashes indicating the line number, including place value. WHITE flashes are thousands' place, BLUE are hundreds' place, YELLOW are tens' place, and CYAN are one's place. And so for example, an fault on line 32 would flash Xanthous three times and so CYAN two times. Zeroes are indicated by an extra-long dark gap.

Series console showing `ValueError: Incompatible .mpy file`

This error occurs when importing a module that is stored equally a .mpy binary file that was generated past a different version of CircuitPython than the ane its being loaded into. In particular, the mpy binary format changed between CircuitPython versions six.ten and 7.ten, 2.x and 3.x, and 1.10 and 2.x.

Then, for instance, if you upgraded to CircuitPython 7.x from 6.x you'll demand to download a newer version of the library that triggered the error on import . All libraries are available in the Adafruit bundle.

CIRCUITPY Drive Issues

You may find that you can no longer save files to your CIRCUITPY drive. You may observe that your CIRCUITPY stops showing upwards in your file explorer, or shows up as NO_NAME. These are indicators that your filesystem has issues. When the CIRCUITPY disk is not safely ejected before being reset past the button or being disconnected from USB, it may corrupt the flash bulldoze. It tin happen on Windows, Mac or Linux, though it is more common on Windows.

Be aware, if y'all take used Arduino to program your board, CircuitPython is no longer able to provide the USB services. You lot will demand to reload CircuitPython to resolve this situation.

The easiest kickoff pace is to reload CircuitPython. Double-tap reset on the lath and so y'all become a boardnameBOOT drive rather than a CIRCUITPY drive, and re-create the latest version of CircuitPython (.uf2) back to the board. This may restore CIRCUITPY functionality.

If reloading CircuitPython does not resolve your result, the side by side footstep is to effort putting the board into safe way.

Rubber Mode

Whether you've run into a situation where you tin can no longer edit your lawmaking.py on your CIRCUITPY drive, your board has gotten into a state where CIRCUITPY is read-only, or you have turned off the CIRCUITPY bulldoze altogether, condom way tin can help.

Safe way in CircuitPython does non run whatsoever user code on startup, and disables auto-reload. This means a few things. Kickoff, safe style bypasses any code in kicking.py (where you tin can set CIRCUITPY read-only or plough it off completely). 2d, it does non run the code in code.py. And finally, it does not automatically soft-reload when data is written to the CIRCUITPY drive.

Therefore, any you may take washed to put your board in a non-interactive state, condom mode gives you the opportunity to correct information technology without losing all of the data on the CIRCUITPY drive.

Inbound Safe Mode in CircuitPython 7.x

To enter safe mode when using CircuitPython 7.ten, plug in your board or hit reset (highlighted in scarlet to a higher place). Immediately after the board starts up or resets, information technology waits 1000ms. On some boards, the onboard status LED will glimmer xanthous during that time. If you press reset during that 1000ms, the board volition starting time up in safety manner. It can be difficult to react to the yellow LED, so you may want to think of it but equally a "slow" double click of the reset button. (Retrieve, a fast double click of reset enters the bootloader.)

Entering Safe Mode in CircuitPython 6.10

To enter rubber way when using CircuitPython 6.x, plug in your board or hit reset (highlighted in red above). Immediately after the board starts upwardly or resets, it waits 700ms. On some boards, the onboard status LED (highlighted in dark-green higher up) will turn solid yellow during this time. If y'all printing reset during that 700ms, the board will start up in safe manner. It tin exist difficult to react to the yellow LED, so you may want to think of it just as a slow double click of the reset button. (Recall, a fast double click of reset enters the bootloader.)

In Safe Mode

Once you've entered safe manner successfully in CircuitPython 6.x, the LED volition pulse yellowish.

If you successfully enter safe way on CircuitPython 7.x, the LED will intermittently blink yellow three times.

If y'all connect to the serial panel, yous'll find the post-obit message.

Auto-reload is off. Running in prophylactic fashion! Not running saved code.  CircuitPython is in condom mode because yous pressed the reset button during boot. Printing again to exit safe mode.  Printing any key to enter the REPL. Use CTRL-D to reload.

Auto-reload is off. Running in safe style! Not running saved code.  CircuitPython is in safe mode because you pressed the reset button during boot. Printing once more to get out safety mode.  Press any key to enter the REPL. Apply CTRL-D to reload.

You lot can at present edit the contents of the CIRCUITPY drive. Think, your code will not run until you press the reset button, or unplug and plug in your board, to get out of rubber fashion.

At this point, y'all'll want to remove any user lawmaking incode.py and, if nowadays, the kick.py file from CIRCUITPY. One time removed, tap the reset button, or unplug and plug in your lath, to restart CircuitPython. This will restart the lath and may resolve your bulldoze issues. If resolved, yous can begin coding once more every bit usual.

If safe mode does not resolve your issue, the lath must be completely erased and CircuitPython must be reloaded onto the board.

You WILL lose everything on the lath when you lot complete the following steps. If possible, make a re-create of your code earlier continuing.

To erase CIRCUITPY: `storage.erase_filesystem()`

CircuitPython includes a built-in function to erase and reformat the filesystem. If you have a version of CircuitPython older than 2.iii.0 on your board, y'all tin update to the newest version to do this.

Connect to the CircuitPython REPL using Mu or a terminal programme.
Type the following into the REPL:

>>> import storage >>> storage.erase_filesystem()

>>> import storage >>> storage.erase_filesystem()

CIRCUITPY volition be erased and reformatted, and your board will restart. That'southward it!

Erase CIRCUITPY Without Admission to the REPL

If y'all can't access the REPL, or y'all're running a version of CircuitPython previous to two.iii.0 and you don't want to upgrade, in that location are options bachelor for some specific boards.

The options listed below are considered to be the "old style" of erasing your board. The method shown above using the REPL is highly recommended as the all-time method for erasing your board.

If at all possible, it is recommended to use the REPL to erase your CIRCUITPY bulldoze. The REPL method is explained above.

For the specific boards listed below:

If the board you lot are trying to erase is listed below, follow the steps to utilize the file to erase your board.

1. Download the correct erase file:

       2. Double-click the reset push button on the board to bring upward the boardnameKick drive.
       3. Drag the erase .uf2 file to the boardnameBOOT bulldoze.
       iv. The condition LED will turn yellow or blue, indicating the erase has started.
       5. Subsequently approximately xv seconds, the status LED will light upwards green. On the NeoTrellis M4 this is the kickoff NeoPixel on the grid
       6. Double-click the reset button on the lath to bring upwardly the boardnameBoot drive.
       7. Drag the advisable latest release of CircuitPython .uf2 file to the boardnameBoot drive.

It should reboot automatically and you should see CIRCUITPY in your file explorer again.

If the LED flashes red during stride 5, it means the erase has failed. Repeat the steps starting with ii.

If y'all haven't already downloaded the latest release of CircuitPython for your board, check out the installation page. Yous'll also need to load your lawmaking and reinstall your libraries!

For SAMD21 not-Express boards that have a UF2 bootloader:

Whatsoever SAMD21-based microcontroller that does non have external flash bachelor is considered a SAMD21 non-Express board. Non-Limited boards that have a UF2 bootloader include Trinket M0, GEMMA M0, QT Py M0, and the SAMD21-based Trinkey boards.

If you are trying to erase a SAMD21 not-Express board, follow these steps to erase your lath.

1. Download the erase file:

       two. Double-click the reset button on the board to bring up the boardnameBOOT drive.
       iii. Drag the erase .uf2 file to the boardnameBOOT drive.
       4. The kicking LED will start flashing again, and the boardnameBOOT drive will reappear.
       five. Drag the advisable latest release CircuitPython .uf2 file to the boardnameKicking bulldoze.

It should reboot automatically and you should see CIRCUITPY in your file explorer over again.

If you haven't already downloaded the latest release of CircuitPython for your board, bank check out the installation page YYou'll also need to load your code and reinstall your libraries!

For SAMD21 non-Express boards that do not accept a UF2 bootloader:

Whatever SAMD21-based microcontroller that does non have external flash bachelor is considered a SAMD21 not-Express board. Non-Express boards that do not have a UF2 bootloader include the Feather M0 Bones Proto, Feather Adalogger, or the Arduino Zero.

If you are trying to erase a non-Limited board that does non take a UF2 bootloader, follow these directions to reload CircuitPython using bossac, which will erase and re-create CIRCUITPY.

Running Out of File Space on SAMD21 Non-Express Boards

Whatever SAMD21-based microcontroller that does non take external flash available is considered a SAMD21 not-Express board. This includes boards like the Trinket M0, GEMMA M0, QT Py M0, and the SAMD21-based Trinkey boards.

The file organization on the board is very tiny. (Smaller than an ancient floppy disk.) And so, its probable you'll run out of space but don't panic! There are a number of ways to free up space.

circuitpython_arduino_compatibles_gemma_out_of_space.png

Delete something!

The simplest way of freeing up space is to delete files from the drive. Mayhap there are libraries in the lib folder that yous aren't using anymore or test lawmaking that isn't in use. Don't delete the lib binder completely, though, simply remove what y'all don't need.

The lath ships with the Windows 7 serial commuter too! Experience costless to delete that if you lot don't need it or take already installed information technology. It's ~12KiB or then.

Utilise tabs

I unique feature of Python is that the indentation of code matters. Normally the recommendation is to indent lawmaking with four spaces for every indent. In general, that is recommended too. However, i trick to storing more than human-readable code is to use a single tab character for indentation. This approach uses one/4 of the space for indentation and tin be significant when you're counting bytes.

On MacOS?

MacOS loves to generate hidden files. Luckily you tin disable some of the extra hidden files that macOS adds by running a few commands to disable search indexing and create zero byte placeholders. Follow the steps below to maximize the corporeality of space bachelor on macOS.

Preclude & Remove MacOS Hidden Files

Start find the volume proper name for your board. With the board plugged in run this command in a terminal to listing all the volumes:

ls -l /Volumes

ls -l /Volumes

Await for a book with a name likeCIRCUITPY (the default for CircuitPython). The full path to the volume is the/Volumes/CIRCUITPY path.

Now follow the steps from this question to run these terminal commands that stop subconscious files from being created on the lath:

mdutil -i off /Volumes/CIRCUITPY cd /Volumes/CIRCUITPY rm -rf .{,_.}{fseventsd,Spotlight-5*,Trashes} mkdir .fseventsd touch .fseventsd/no_log .metadata_never_index .Trashes cd -

mdutil -i off /Volumes/CIRCUITPY cd /Volumes/CIRCUITPY rm -rf .{,_.}{fseventsd,Spotlight-5*,Trashes} mkdir .fseventsd bear on .fseventsd/no_log .metadata_never_index .Trashes cd -

Supercede/Volumes/CIRCUITPY in the commands above with the full path to your board'southward volume if it's different. At this betoken all the hidden files should be cleared from the board and some hidden files will exist prevented from being created.

Alternatively, with CircuitPython 4.x and in a higher place, the special files and folders mentioned above volition be created automatically if y'all erase and reformat the filesystem. Alert: Salvage your files first! Do this in the REPL:

>>> import storage
>>> storage.erase_filesystem()

However there are still some cases where hidden files will exist created by MacOS. In particular if y'all copy a file that was downloaded from the net it will have special metadata that MacOS stores equally a subconscious file. Luckily you can run a re-create command from the final to re-create files without this hidden metadata file. See the steps below.

Re-create Files on MacOS Without Creating Hidden Files

Once yous've disabled and removed hidden files with the above commands on macOS you demand to be careful to copy files to the board with a special command that prevents hereafter hidden files from being created. Unfortunately you cannot apply elevate and drib re-create in Finder considering it will still create these subconscious extended attribute files in some cases (for files downloaded from the cyberspace, like Adafruit's modules).

To copy a file or folder employ the-X choice for thecp command in a final. For example to copy a file_name.mpy file to the board use a command similar:

cp -X file_name.mpy /Volumes/CIRCUITPY

cp -X file_name.mpy /Volumes/CIRCUITPY

(Supervene upon file_name.mpy with the name of the file you desire to copy.)

Or to copy a folder and all of the files and folders contained inside, use a command like:

cp -rX folder_to_copy /Volumes/CIRCUITPY

cp -rX folder_to_copy /Volumes/CIRCUITPY

If you are copying to the lib folder, or some other folder, make sure it exists before copying.

# if lib does not exist, you'll create a file named lib ! cp -X file_name.mpy /Volumes/CIRCUITPY/lib # This is safer, and will complain if a lib folder does not exist. cp -X file_name.mpy /Volumes/CIRCUITPY/lib/

# if lib does not exist, y'all'll create a file named lib ! cp -X file_name.mpy /Volumes/CIRCUITPY/lib # This is safer, and will mutter if a lib folder does not exist. cp -X file_name.mpy /Volumes/CIRCUITPY/lib/

Other MacOS Space-Saving Tips

If you'd like to see the corporeality of space used on the drive and manually delete subconscious files hither'due south how to do then. First, move into the Volumes/ directory with cd /Volumes/, and then list the amount of space used on the CIRCUITPY bulldoze with the df control.

That's not very much space left! The next footstep is to show a list of the files currently on the CIRCUITPY bulldoze, including the hidden files, using the ls command. You lot cannot use Finder to do this, y'all must do it via command line!

At that place are a few of the hidden files that MacOS loves to generate, all of which begin with a ._ before the file name. Remove the ._ files using the rm command. You tin remove them all one time by running rm CIRCUITPY/._*. The * acts as a wildcard to apply the command to everything that begins with ._ at the same fourth dimension.

Finally, you can run df again to see the current infinite used.

Squeamish! You have 12Ki more than than earlier! This space can now exist used for libraries and code!

Device Locked Up or Boot Looping

In rare cases, information technology may happen that something in your code.py or kick.py files causes the device to get locked up, or even go into a boot loop. A kick loop occurs when the board reboots repeatedly and never fully loads. These are non acquired past your everyday Python exceptions, typically information technology's the result of a deeper problem within CircuitPython. In this situation, it tin be difficult to recover your device if CIRCUITPY is not assuasive you lot to modify the lawmaking.py or boot.py files. Safe style is one recovery selection. When the device boots up in safe manner it will non run the code.py or boot.py scripts, simply will notwithstanding connect the CIRCUITPY drive so that you lot can remove or alter those files as needed.

The method used to manually enter safe manner can be different for different devices. It is likewise very like to the method used for getting into bootloader manner, which is a different matter. So it can take a few tries to get the timing correct. If you end up in bootloader fashion, no problem, you can try over again without needing to practise anything else.

For most devices:
Press the reset button, and and so when the RGB status LED blinks yellow, printing the reset button again. Since your reaction time may non be that fast, attempt a "slow" double click, to catch the yellow LED on the second click.

For ESP32-S2 based devices:
Printing and release the reset button, and so press and release the kick button about 3/4 of a second afterwards.

Refer to the diagrams in a higher place for kicking sequence details.

This guide was starting time published on Dec 19, 2017. It was last updated on 2021-12-01 16:32:33 -0500.

This folio (Troubleshooting) was last updated on Mar 31, 2022.

Text editor powered by tinymce.

Source: https://learn.adafruit.com/welcome-to-circuitpython/troubleshooting

Posted by: pricedrabland1987.blogspot.com