I created a simple application toggling EXP_IO3, EXP_IO2, and EXPIO1 based on readings from three ADC pins MCA_IO1, MCA_IO3 and MCD_IO5. Everything was running fine and I left the application to run over night. When I came in this morning I noticed that the unit was spitting garbage out of the serial port. I figure something must have happened with my application and I corrupted the flash somehow. No matter what I do the serial port spits out jibberish. As I look through the steps to recover your device on the web site, I try to follow the Boot U-boot in USB debug mode
1. Install the SDK toolchain. See Application development.
2. Connect the USB serial cable to the CONSOLE connector on the SBC and to your host computer.
3. Connect the micro USB cable to the USB device port of the board (bottom layer, under the USB host connectors).
4. Close the BOOT jumper near the CONSOLE connector.
5. Power up the board.
6. Open a serial terminal at 115200/8/n/1.
7. On the host computer, as root, run the imx_usb tool installed with the SDK toolchain with the U-Boot file to boot as parameter. For example:
sudo /opt/dey/2.0-r5/sysroots/x86_64-deysdk-linux/usr/bin/imx_usb /mypath/u-boot-ccimx6ulsbc.imx
When I type this command I get the message no matching USB device found. Is there another method to restore the device or is this effectively bricked? I am not sure how my application could have corrupted flash this bad overnight but it is certainly possible.