Problems

Building, flashing or writing an app? See Troubleshooting.

Goal: Fix the common problems on your own.

Each entry says what you see, why it happens, and what to do.

The CrossPad does not turn on

You see: nothing happens when you hold the power button for 1.5 seconds.

Cause: one of these:

• The battery is empty.
• The CrossPad is in ship mode. Holding the power button for 7 seconds puts it there; it disconnects the battery completely.

Fix:

1. Plug the charger into the main USB port. This also wakes it from ship mode. While the CrossPad is off, a charge screen appears and the pads show the battery level.
2. Or hold the power button. This also wakes it from ship mode, and it starts by itself.
3. If the battery was only empty: once it has charged a little, hold the power button for about 1.5 seconds and let go. Nothing lights while you hold; the start-up animation follows.

Tip

To switch off normally, hold the power button for 4 seconds and let go. Keep holding to 7 seconds only if you want ship mode, for example before storing the CrossPad for a long time.

The SD card is not found

You see: Reading SD card… or No SD card - reinsert or restart when you open the Sampler or the kit browser.

Cause: Reading SD card… means the CrossPad is still scanning the card after starting. A full card takes a moment. No SD card means no card is mounted: it is missing, not pushed in fully, or unreadable.

Fix:

1. If it says Reading SD card…, wait a few seconds and try again.
2. If it says No SD card, push the card fully into its slot. The CrossPad picks up a card you put in later by itself. If not, restart the CrossPad.
3. Still nothing? Check the card on a computer. Kits must be in the crosspad/kits/ folder.

The pads do not respond

You see: no light and no sound when you hit the pads; the screen works.

Cause: the pads are switched off in Settings, or a pad controller update is running or failed.

Fix:

1. Open Settings (pad 16, labelled Setup on the MODE map) → System and check that STM Keypad Scan is on.
2. If the screen says Flashing STM32, wait for it to finish (about 15 seconds).
3. If it says STM32 update failed, see The pad controller update was postponed or failed.
4. Still nothing? Do a Factory reset.

There is no sound

You see: the pads light when you hit them, but you hear nothing.

Cause: one of these:

• No kit is loaded. Pick one after each start.
• A volume is at 0, or the speakers are switched off.
• An output is muted in the Mixer.

Fix:

1. Open Kits (pad 13) and pick a kit. See Play.
2. Open Settings → Audio. Check that Speakers (auto on play) is on and that the Speakers and Headphones sliders are above 0. The defaults are 64 and 64.
3. Open Mixer (pad 11) → OUT. Check that no output is muted and the faders are up.

4. In the Mixer, SOURCES: check that the sampler is not muted.

The computer does not see the CrossPad

You see: no drive, no MIDI port or no sound card on the computer, or the browser companion lists no port.

Cause: one of these:

• The cable only charges and carries no data.
• The cable is in the second USB port. Drives, USB audio and browser updates use the main USB port.
• The USB mode does not fit the job: browser updates need serial mode (MIDI + Serial), USB audio needs USB audio mode (MIDI + Audio).
• The browser is not Chrome or Edge.

Fix:

1. Use a USB-C data cable in the main USB port.
2. Set the right mode in Settings → USB → Mode. See With a computer.
3. For the companion, use Chrome or Edge.
4. For the SD card as a drive: check the cable and the port, or use a card reader. See Your sounds.

A kit I copied is missing

You see: you copied a kit folder onto the card, but it is not in the kit browser.

Cause: the CrossPad reads the list of kits when it starts. While the card is a USB drive, the CrossPad does not see what you copy. Or the folder is in the wrong place.

Fix:

1. On the computer, eject the drive first. Then on the CrossPad press Exit and restart on the USB Transfer screen. The CrossPad restarts and reads the card again.
2. Check that the kit is a folder inside crosspad/kits/, with its kit.json and its WAV files in it.
3. Look under LEGACY in the kit browser. USER shows only kits made on the CrossPad (with + NEW or the Slicer) or marked as user kits in their kit.json.

More: Your sounds.

A WAV file does not play

You see: a pad stays silent with your sample on it, or the file is refused when you open it in the Recorder or Slicer.

Cause: the CrossPad plays WAV files in 16-bit PCM, mono or stereo. It refuses 24-bit, 32-bit float and compressed WAV files.

Fix: convert the file on your computer to 16-bit PCM WAV at 44100 Hz, and copy it again. Most audio editors can do this when you export or save as WAV.

WiFi asks to restart in network mode

You see: Not enough memory — “WiFi does not fit beside what is running now. Restart in network mode?”

Cause: WiFi and a loaded kit run one at a time. Network mode is made for WiFi tasks such as updates.

Fix: press Restart. The CrossPad starts in network mode, with the WiFi, Store and Updates tabs and no sound. Do what you need, then press Exit to restart normally. See Updates.

An update failed or was rolled back

You see: after an update, Settings → Updates → Running still shows the old version. Or Status says Error: with a reason. Or the CrossPad says Update Failed!.

Cause:

• Old version after restarting: the new firmware did not start properly, so the CrossPad went back to the one before. This protects you; nothing is lost.
• Error: the WiFi download stopped. The reason is on screen, for example no WiFi network in reach or the SD card is full.
• Update Failed! the browser update was interrupted.

Fix:

• After a roll-back: open Firmware (pad 15, Update on the MODE map) → Library. The failed firmware shows rolled back. Open it and press Try this slot again, or Reinstall to write it fresh.
• After an Error: fix the reason and press Update again. The download resumes.
• After Update Failed!: check the cable and serial mode, and repeat the browser update.

Step by step: Updates.

The pad controller update was postponed or failed

You see: “Battery under 20%, no charger: plug in and reboot to be asked again.” with OK and Later. Or STM32 update failed. (STM32 is the pad controller.)

Cause: the update needs at least 20 % battery or the charger, so it cannot be cut off half-way. A failed update was interrupted.

Fix:

• Postponed: plug in the charger and restart the CrossPad. It asks again; press Update and wait about 15 seconds. You can also start it from Settings → Programming.
• Failed, pads still work: press Retry.
• Failed, pads still not responding after you switch off and on: use the Recovery page of the companion at https://play.crosspad.app/device in Chrome or Edge.

Not listed here? Check Settings for the setting involved, or Get started for the basics.