Does ls /sys/bus/w1/devices/23-000002eddd9b still show eeprom ? If not, what does ls /sys/bus/w1/devices show you?
I prefer to run commands from my home director, you can change to your home with 'cd ~' On Tuesday, 29 September 2020 at 15:15:27 UTC+1 Johan Lind wrote: > Thank you (and sorry for the double post) ! > However, I still have no luck writing to the eeprom. > > I have tried a couple of variations of the commands but I get error even > if logged in as root. > > debian@beaglebone:/sys/bus/w1/devices/23-000002eddd9b$ sudo sh -c "echo > 'cat /home/debian/file' > eeprom" > sh: 1: echo: echo: I/O error > debian@beaglebone:/sys/bus/w1/devices/23-000002eddd9b$ su > Password: > root@beaglebone:/sys/bus/w1/devices/23-000002eddd9b# echo 'cat > /home/debian/file' > eeprom > bash: echo: write error: Invalid argument > root@beaglebone:/sys/bus/w1/devices/23-000002eddd9b# cat /home/debian/file > > eeprom > cat: write error: Invalid argument > root@beaglebone:/sys/bus/w1/devices/23-000002eddd9b# exit > exit > debian@beaglebone:/sys/bus/w1/devices/23-000002eddd9b$ sudo cp -T > /home/debian/file eeprom > cp: error writing 'eeprom': Invalid argument > > fredag 25 september 2020 kl. 17:52:55 UTC+2 skrev [email protected]: > >> Also the copy command >> cp -T *source* *destination* >> so... >> sudo cp -T /home/debian/file eeprom >> >> On Friday, 25 September 2020 at 16:48:24 UTC+1 [email protected] >> wrote: >> >>> Wasn't the problem that the redirection of output by ">" was outside the >>> sudo *command* >>> The "echo" is not needed, only >>> sudo sh -c "cat /home/debian/file > eeprom" >>> >>> On Friday, 25 September 2020 at 15:59:06 UTC+1 RobertCNelson wrote: >>> >>>> On Fri, Sep 25, 2020 at 9:48 AM johan.lind via BeagleBoard >>>> <[email protected]> wrote: >>>> > >>>> > I would need some help to understand why I can't write to an DS2433 >>>> eeprom. >>>> > >>>> > System information: >>>> > BBB Industrial board >>>> > Debian 10 (Buster IoT Image 2020-04-06) >>>> > Hardware attached are DS2482 i2c to w1 interface and DS2433 eeprom. >>>> > >>>> > Commands executed to set-up system: >>>> > $ modprobe ds2482 >>>> > $ echo ds2482 0x18 > /sys/bus/i2c/devices/i2c-1/new_device >>>> > $ modprobe wire >>>> > >>>> > I can read the eeprom by executing >>>> > $ cd /sys/bus/w1/devices/23-000002eddd9b >>>> > $ cat eeprom | hexdump >>>> > >>>> > Getting this far I assume hardware is correct and drivers are loaded >>>> correctly. >>>> > >>>> > debian@beaglebone:/sys/bus/w1/devices/23-000002eddd9b$ ls >>>> > driver eeprom id name power subsystem uevent >>>> > >>>> > Should here be a directory called w1_slave? >>>> > I see such a directory on some web pages searching for similar >>>> problems with w1. >>>> > >>>> > Now to the problem. >>>> > Executing the following command will fail: >>>> > debian@beaglebone:/sys/bus/w1/devices/23-000002eddd9b$ sudo cat >>>> /home/debian/file > eeprom >>>> > [sudo] password for debian: >>>> > cat: write error: Invalid argument >>>> >>>> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Privileged_echo >>>> >>>> sudo sh -c "echo 'cat /home/debian/file' > eeprom" >>>> >>>> Regards, >>>> >>>> -- >>>> Robert Nelson >>>> https://rcn-ee.com/ >>>> >>> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/b1989070-3ca8-46a1-951c-c39daeaa8644n%40googlegroups.com.
