The eeprom probably is a device, not a filesystem.
Use dd instead.
/Sven
tisdag 29 september 2020 kl. 17:59:14 UTC+2 skrev Johan Lind:
> I tried with only a short (6 bytes) string but still the same behaviour.
>
>
> tisdag 29 september 2020 kl. 17:45:47 UTC+2 skrev robert.sty...@gmail.com:
>
>>
I tried with only a short (6 bytes) string but still the same behaviour.
tisdag 29 september 2020 kl. 17:45:47 UTC+2 skrev robert.sty...@gmail.com:
> I suggest trying to write less than 32 bytes (the dmesg implies something
> wrong with offset or count) -- create a file of less than 32 bytes
I suggest trying to write less than 32 bytes (the dmesg implies something
wrong with offset or count) -- create a file of less than 32 bytes and copy
to eeprom
cd ~
echo "1234567890" > file10
cp -T file10 /sys/bus/w1/devices/23-02eddd9b/eeprom
In the data sheet you need a much smaller R[PU]
On Tue, Sep 29, 2020 at 9:55 AM 'Johan Lind' via BeagleBoard
wrote:
>
> Yes, it does still show eeprom
>
> debian@beaglebone:~$ ls /sys/bus/w1/devices/23-02eddd9b
> driver eeprom id name power subsystem uevent
> debian@beaglebone:~$ ls /sys/bus/w1/devices/
> 23-02eddd9b
Yes, it does still show eeprom
debian@beaglebone:~$ ls /sys/bus/w1/devices/23-02eddd9b
driver eeprom id name power subsystem uevent
debian@beaglebone:~$ ls /sys/bus/w1/devices/
23-02eddd9b w1_bus_master1
debian@beaglebone:~$
debian@beaglebone:~$ ls -al
Does
ls /sys/bus/w1/devices/23-02eddd9b
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
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-02eddd9b$ sudo sh -c "echo
'cat /home/debian/file' >
Oh, that looks fun, specially with no errors over dmesg..
Which kernel version?
uname -r ?
Regards,
On Tue, Sep 29, 2020 at 8:24 AM suprock tech wrote:
>
> Sorry it took a few days but heres some logs.
>
>
> Working beaglebone, Unit #1542:
> dmesg output when plugging in a cable:
> [
Sorry it took a few days but heres some logs.
Working beaglebone, Unit #1542:
dmesg output when plugging in a cable:
[ 74.039867] cpsw 4a10.ethernet eth0: Link is Up - 100Mbps/Full -
flow control off
[ 74.040069] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 74.162638]
On Tue, Sep 29, 2020 at 6:44 AM 'Johan Lind' via BeagleBoard
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
On Tue, Sep 29, 2020 at 7:07 AM Dylan Quinn wrote:
>
> Just to specify- it looks like am335x_evm.sh is causing the long boot time.
> What can I modify in the script to drastically reduce the 30 second time?
You can disable it, but the big delay in that script is loading the
usb gadget drivers..
Just to specify- it looks like am335x_evm.sh is causing the long boot time.
What can I modify in the script to drastically reduce the 30 second time?
On Monday, September 28, 2020 at 8:46:46 AM UTC-4 Dylan Quinn wrote:
>
> Hello everyone,
>
> I would like to reduce my boot time for the
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:
$ modprobe ds2482
$ echo ds2482 0x18 >
13 matches
Mail list logo
