Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning

Note: prior to V0.4.0, the updateRCE command had the argument order <tarball> <location>.

Troubleshooting and recovery

 

You've corrupted something, and you're stuck with a non-booting RCE

In most cases, it is best to use the updateFOO scripts above to recover, but if the RCE is stuck in an infinite boot loop, they won't work.

You can replace the RTEMS core libraries, the RTEMS APP libraries, as well as the bootloader and the FPGA bitstream from an SD reader.   The RTEMS APP area is most likely, since it is the only core partition writable from RTEMS.

  1.  Put the SD card in a reader, and observe that devices are created for the partitions SD card in /dev/sdXN (where X is a letter, and N is [1-7]).  If you need, you can use "partprobe -s" to list them as well.
  2. RTEMS APP libraries and SVTs:
    The RTEMS APP partition is /dev/sdX6.  Mount it.  Copy all files in SDK/tgt/rtemsapp/config to /mnt/config.  Sync the partition and eject.
  3. RTEMS Libraries:
    The RTEMS partition is /dev/sdX5.  Mount that partition.  Copy all the files in SDK/tgt/rtems/* to that mount point.  Sync the partition and eject.
  4.  Bootloader/FPGA bitstream
    The BOOT partition is /dev/sdX1.  Mount it.  Copy either boot.bin or fpga.bit from SDK/tgt/boot/dpm to that point.  Sync and eject.

This will leave you with a system which boots the core code, but your user code won't run automatically.  You'll have to reinstall your own code.in progress