User Tools

Site Tools


kb:ni-rt:linuxrt:debugging

99 Debugging

Errors

Misc

Booting into safe mode

for NI Linux RT on Intel x64 (i.e. Atom) based products

Boot into safe mode:

  /etc/init.d/nisetbootmode force-safemode && reboot

*note that it seems rebooting while in safe mode will boot back into run mode (unless you have some critical error preventing it, in which case it will fail back into safe mode)

Boot into run mode (Redundant, see comment above):

  /etc/init.d/nisetbootmode force-normal  && reboot

Checking a filesystem

To check a filesystem the filesystem has to be unmounted with umount /path/to_fs. If the filesystem is in use the unmount can be forced with -l. WARMING: To force the unmount can have unpredictable side effects.

To check the filesystem use fsck /path/to_device. If the actual filesystem is not autodetected you can select it manually, e.g. fsck.ext4 /dev/sda4.

Logging

Courtesy of NI forums user thoric

To have a more detailed crash dump:

  • add the following tokens to /etc/natinst/share/lvrt.conf
  DPrintfLogging=True
  Debugging=True
  • add the following tokens to [LVRT] section of /etc/natinst/share/ni-rt.ini
  EnableCoreDumps="True"
  • Save the files and reboot the cRIO
  • Log files will be found in /var/local/natinst/log/

UDP Broadcasts

if you assign an IP to the net address input, the UDP connection will be unable to receive broadcasts.

https://forums.ni.com/t5/LabVIEW/UDP-Broadcast-not-Received-by-UDP-Read-on-NI-Linux-RT-Target/td-p/4292684

kb/ni-rt/linuxrt/debugging.txt · Last modified: 2024/08/22 19:16 by joerg.hampel