# EEPROM specification lacks a device tree fragment ## Problem environment The HAT standard requires valid EEPROM data, but does not include a compiled device tree structure. Such a structure can help a new user avoid GPIO manipulation steps considered to be advanced. ## Steps to reproduce 1. Refer to the test plan 1. Review programrom.txt 1. Search for a device tree ## Expected result A device tree fragment is compiled together with programdat to create a comprehensive EEP file. ## Actual result There is no device tree fragment available. ## Workaround Producing a EEP file and programming it to the EEPROM results in a valid HAT configuration, even without a device tree fragment. The user must manually configure GPIOs in use (for example GPIO26 to programmatically reset the MCU) before writing to or reading from them. ## Severity level This is **low priority** because project requirements do not include EEPROM identification.

Solved in 0859e50.