Skip to content
Joshua Zenn edited this page Aug 25, 2015 · 5 revisions

Should something go wrong during the execution of your program, an error code will be displayed. If you have a device with more program memory (like the Arduino Mega), build Octoduino with the build options CRASH_MSG_DETAIL and CORE_STACK to see more detailed error messages along with a descriptive app stack dump.

By default, when an error is encountered, the system will display an error message and then halt. If you build Octoduino with the build option CRASH_REBOOT, the system will restart upon a crash (may cause an infinite crash loop if error lies in program code).

If you follow the steps below and are still hitting errors, visit us on our Gitter channel and we will be glad to help you out (link is in ~/README.md).

Ex000

Program has been terminated by the script file.

Causes:

  • PB script called END;.
  • Reached end of root PB script file.

Possible fixes:

  • This is not an error code. If this is not the behavior you want, remove any calls to END; within your program.

Ex001

Error initializing Serial output channel.

Causes:

  • Waiting for PC serial connection loop timed out.

Possible fixes:

  • Make sure you have a Serial console open when the device is booted.
  • Build without the option IO_LOG_SERIAL.

Ex002

Error initializing SD log output channel.

Causes:

  • SD card is not fully inserted.
  • SD card is corrupted.
  • Another device or IO channel is using the required SS/data pins.
  • Your shield does not use pin 4 for data.
  • Your shield is incorrectly seated.

Possible fixes:

  • Format the SD card to FAT16 or FAT32.
  • Use a different SD card.
  • Make sure the card is not marked as read-only.
  • Verify that your shield uses pins 4/10. If not, use the GUI builder to change it.
  • Make sure that your shield is fully inserted.
  • Make sure that any non-shield device is using pins 4 and 10.

Ex003

Error initializing LCD output channel.

Causes:

  • The LCD library could not interface with the LCD device.

Possible fixes:

  • Make sure that your wiring is correct.
  • Check your LCD device for damage.
  • Ensure that no other devices are using the data lines.

Ex004

Error writing to log on SD card.

Causes:

  • SD card is not fully inserted.
  • SD card is corrupted.
  • Another device or IO channel is using the required SS/data pins.
  • Your shield does not use pin 4 for data.
  • Your shield is incorrectly seated.

Possible fixes:

  • Format the SD card to FAT16 or FAT32.
  • Use a different SD card.
  • Make sure the card is not marked as read-only.
  • Verify that your shield uses pins 4/10. If not, use the GUI builder to change it.
  • Make sure that your shield is fully inserted.
  • Make sure that any non-shield device is using pins 4 and 10.

Ex006

PB runner could not open file.

Causes:

  • .pba file has been moved or does not exists on device.

Possible fixes:

  • Verify all pathnames in your program code.

Ex007

Unrecognized command.

Causes:

  • Incorrectly typed opcode in .pba file.
  • Missing ';' or newline in source file.

Possible fixes:

  • Verify program opcodes.

Ex008

Error writing to file on SD card.

Causes:

  • SD card is not fully inserted.
  • SD card is corrupted.
  • Another device or IO channel is using the required SS/data pins.
  • Your shield does not use pin 4 for data.
  • Your shield is incorrectly seated.

Possible fixes:

  • Format the SD card to FAT16 or FAT32.
  • Use a different SD card.
  • Make sure the card is not marked as read-only.
  • Verify that your shield uses pins 4/10. If not, use the GUI builder to change it.
  • Make sure that your shield is fully inserted.
  • Make sure that any non-shield device is using pins 4 and 10.

Ex009

File does not exist on SD card.

Causes:

  • File paths are incorrect.

Possible fixes:

  • Verify the filepaths in your PB programs.

Ex010

Error reading from file on SD card.

Causes:

  • SD card is corrupted.
  • File is corrupted.
  • Filename does not conform to the 8.3 standard.
  • Another process is using the file.

Possible fixes:

  • Use a different SD card.
  • Make sure you are not reading from or system files including SWAP.

Ex011

Swap folder is not empty.

Causes:

  • Swap folder is not empty.

Possible fixes:

  • Open the SD card on your computer and delete the ~/swap folder.

Ex012

Tried to create a variable that already exists in SWAP.

Causes:

  • PB code is trying to create a variable that already exists.

Possible fixes:

  • Make sure you are not using system variable names.
  • Change the names of your variables.
  • Use a solid naming convention, like *APPID*-*VARNAME*

Ex013

Error writing new swap variable to SD card.

Causes:

  • See Ex010

Possible fixes:

  • See Ex010

Ex014

Swap variable already exists in swap space.

Causes:

  • See Ex012

Possible fixes:

  • See Ex012

Ex015

Error opening swapfile on SD card.

Causes:

  • See Ex010

Possible fixes:

  • See Ex0101

Ex016

Error deleting swap file on SD card.

Causes:

  • See Ex010 and Ex012

Possible fixes:

  • See Ex010 and Ex012

Ex017

Variable is not 8.0 compliant.

Causes:

  • Variable name is longer than 8 characters.

Possible fixes:

  • Rename all variables so that their names are 8 characters or less (including the $ symbol).