# Chip programming fails to (auto) erase ## Problem environment Chip programming applications like *openocd(1)* can erase chips before programming, a common practice to allow memory verification. According to documents, *openocd(1)* can be directed to autoerase as well. ## Steps to reproduce 1. Review *openocd(1)* documentation 1. Locate instructions to erase 1. Locate instructions to autoerase ## Expected result Sendcomm firmware is programmed to a chip after an erase operation completes. ## Actual result Erase operations are not configured and seemingly left unused. ## Severity level This is **low priority** because project requirements do not mandate user programming.