sysfs-class-fpga-manager 2.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
  1. What: /sys/class/fpga_manager/<fpga>/name
  2. Date: August 2015
  3. KernelVersion: 4.3
  4. Contact: Alan Tull <atull@opensource.altera.com>
  5. Description: Name of low level fpga manager driver.
  6. What: /sys/class/fpga_manager/<fpga>/state
  7. Date: August 2015
  8. KernelVersion: 4.3
  9. Contact: Alan Tull <atull@opensource.altera.com>
  10. Description: Read fpga manager state as a string.
  11. The intent is to provide enough detail that if something goes
  12. wrong during FPGA programming (something that the driver can't
  13. fix) then userspace can know, i.e. if the firmware request
  14. fails, that could be due to not being able to find the firmware
  15. file.
  16. This is a superset of FPGA states and fpga manager driver
  17. states. The fpga manager driver is walking through these steps
  18. to get the FPGA into a known operating state. It's a sequence,
  19. though some steps may get skipped. Valid FPGA states will vary
  20. by manufacturer; this is a superset.
  21. * unknown = can't determine state
  22. * power off = FPGA power is off
  23. * power up = FPGA reports power is up
  24. * reset = FPGA held in reset state
  25. * firmware request = firmware class request in progress
  26. * firmware request error = firmware request failed
  27. * write init = preparing FPGA for programming
  28. * write init error = Error while preparing FPGA for programming
  29. * write = FPGA ready to receive image data
  30. * write error = Error while programming
  31. * write complete = Doing post programming steps
  32. * write complete error = Error while doing post programming
  33. * operating = FPGA is programmed and operating
  34. What: /sys/class/fpga_manager/<fpga>/status
  35. Date: June 2018
  36. KernelVersion: 4.19
  37. Contact: Wu Hao <hao.wu@intel.com>
  38. Description: Read fpga manager status as a string.
  39. If FPGA programming operation fails, it could be caused by crc
  40. error or incompatible bitstream image. The intent of this
  41. interface is to provide more detailed information for FPGA
  42. programming errors to userspace. This is a list of strings for
  43. the supported status.
  44. * reconfig operation error - invalid operations detected by
  45. reconfiguration hardware.
  46. e.g. start reconfiguration
  47. with errors not cleared
  48. * reconfig CRC error - CRC error detected by
  49. reconfiguration hardware.
  50. * reconfig incompatible image - reconfiguration image is
  51. incompatible with hardware
  52. * reconfig IP protocol error - protocol errors detected by
  53. reconfiguration hardware
  54. * reconfig fifo overflow error - FIFO overflow detected by
  55. reconfiguration hardware