Adc-mcu not responding

[DavidOliveros]

I´m currently trying to run the ADC as you did, I had no problems with the CPU, but when I try with the mcu, it doesn’t work, I built and downloaded it as you explain, but when I run the setup_I2C_MCU.sh it displays the following:

./setup_I2C_MCU.sh: line 2: echo: write error: Device or resource busy
./setup_I2C_MCU.sh: line 3: echo: write error: Device or resource busy
./setup_I2C_MCU.sh: line 4: echo: write error: No such device
./setup_I2C_MCU.sh: line 5: echo: write error: No such device
./setup_I2C_MCU.sh: line 6: echo: write error: No such device
./setup_I2C_MCU.sh: line 7: echo: write error: No such device
./setup_I2C_MCU.sh: line 8: echo: write error: Device or resource busy
./setup_I2C_MCU.sh: line 9: echo: write error: Device or resource busy
./setup_I2C_MCU.sh: line 10: echo: write error: No such device
./setup_I2C_MCU.sh: line 11: echo: write error: No such device
./setup_I2C_MCU.sh: line 13: echo: write error: No such device
./setup_I2C_MCU.sh: line 15: /sys/class/gpio/gpio214/direction: No such file or directory
./setup_I2C_MCU.sh: line 16: /sys/class/gpio/gpio204/direction: No such file or directory
./setup_I2C_MCU.sh: line 17: /sys/class/gpio/gpio205/direction: No such file or directory
./setup_I2C_MCU.sh: line 20: /sys/class/gpio/gpio236/direction: No such file or directory
./setup_I2C_MCU.sh: line 21: /sys/class/gpio/gpio237/direction: No such file or directory
./setup_I2C_MCU.sh: line 22: /sys/class/gpio/gpio212/direction: No such file or directory
./setup_I2C_MCU.sh: line 23: /sys/class/gpio/gpio213/direction: No such file or directory

It gets stuck at this part and does nothing, any ideas?
Is the connection diagram correct, we aren’t using the interruption, are we? and the code is supposed to be reading the AIN0 – GND so we only should connect those wires, right?

Greetings,

David Oliveros

[humberto-garza]

Sorry for the late reply.
I hope you figured it out. But in other case.
I would suggest you flash your Edison to a whole new Image. right after that, load the MCU program and see if it works. Sometimes when you use the I2C from the Atom, it "holds" the bus for ...ever and you may never get it available for the MCU, when you use it, make sure to end the programs safely.

Let me know if it worked