Nano 33 IOT and keyboard library

The Nano 33 IOT appears not to work with the Keyboard library. For instance

#include <Keyboard.h>

void setup()
  while (!Serial);
  Serial.println("Nano 33 IOT");
  pinMode(2, INPUT_PULLUP);
  while (digitalRead(2) == HIGH);
  Serial.println("output to Serial");
  Keyboard.println("output to PC application");

void loop()

produces no keyboard output, only Serial

Something funny is going on with USB ports. Reading around the problem it seems that there was something wrong with the board drivers when used in conjunction with the Keyboard library

My current situation is that Windows Device Manager shows one port for the Nano 33 IOT after uploading the sketch above
but I am not sure that is right. Uploading the Bare Minimum sketch produces a different result

I have version 1.8.11 of the board files installed for the Nano 33 IOT, which seems to be latest

All suggestions for fixes to this problem will be gratefully received

I will guess it's this issue:

(it only mentions the MKR boards, but the same applies just as well for Nano 33 IoT)

Try this fix:

a solution is to open Device Manager and uninstall the MKR1000 drivers; after reset, both serial and HID (keyboard) drivers should be automatically installed

Specific instructions:

  1. Right click the device in Device Manager for your board.
  2. Check the box next to "[] Delete the driver software for this device".
  3. Click the Uninstall button.
  4. Press and release the reset button on the board. The board should now automatically reinstall.

Thanks for the reply.

I went through the process of uninstalling and deleting the drivers for an entry with the yellow triangle so I believe that the Windows drivers are being used and there is now only one entry for the Nano in Device Manager

The driver being used is as follows

Checking for updated drivers results in Windows reporting the following
Searching Windows Update finds no newer/better drivers

I cannot delete the current driver using Device Manager as there is no option to do so on the right click menu, presumably because it is a Microsoft driver rather than a third party one

I can find very little information on this problem on line and so far, no solution

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.