Hi Buğra AYDOĞAR, you said "In case, the value which you wrote above is ASCII so you will see 31:32:33:34:35:36:37:38 in your EEPROM.",but how I can see it
在 2012年10月31日星期三UTC+8下午2时39分12秒，Buğra AYDOĞAR写道： > > Hi Gerald, > > No, it is not write protected. > > I wrote my EEPROM over Linux using Sysfs last night. > I dont remember exactly (I dont have my development board right now) but > it did sth like that > > cd sys/bus/i2c/devices/1-0050/ > echo 12345678 >eeprom > > In case, the value which you wrote above is ASCII so you will > see 31:32:33:34:35:36:37:38 in your EEPROM. Here is converter .( > http://www.dolcevie.com/js/converter.html) > > I think U-Boot I2C commands have some problems.It also doesnt always read > BeagleBone's EEPROM correctly.(%50 sucessfully show BeagleBone's header and > magic number.) . Maybe it is about U-Boot version. I also looked with > scope, it really sent data to EEPROM but I dont know exactly. > > As a result my problem is solved but it is more logicial to write EEPROM > over U-Boot. > > Regards, > Buğra > > On Tuesday, October 30, 2012 10:19:57 PM UTC+2, Gerald wrote: >> >> Is your EEPROM write protected? >> >> Gerald >> >> >> On Tue, Oct 30, 2012 at 1:28 PM, Buğra AYDOĞAR <bugraa...@gmail.com>wrote: >> >>> Hi folks, >>> >>> We have custom Am335x board with eeprom.We want to shape our eeprom like >>> BeagleBone (I mean name,version,serial etc...). >>> >>> I tried with U-Boot using I2C commands.You can see my logs below. >>> Firstly i read my eeprom, then i tried to write byte by btye.Then i read >>> again but nth happened.Then i tried to fill with 0xAA again it didnt >>> succeed. How do you do it? By the way,I ported and used U-Boot 2011.09 for >>> this purpose.I used i2c-tool over Linux but it says UU which means driver >>> is used by Linux and it doesnt let me dump or anything else. >>> >>> What do you suggest to move on? >>> >>> Regards, >>> Buğra >>> >>> U-Boot# i2c probe >>> Valid chip addresses: 24 48 4F 50 51 >>> U-Boot# i2c dev 1 >>> Setting bus to 1 >>> U-Boot# i2c dev 0 >>> Setting bus to 0 >>> U-Boot# i2c md 0x50 0 0x10 >>> 0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ >>> U-Boot# i2c mm 0x50 0 >>> 00000000: ff ? AA >>> 00000001: ff ? BB >>> 00000002: ff ? CC >>> 00000003: ff ? DD >>> 00000004: ff ? U-Boot# <INTERRUPT> >>> U-Boot# <INTERRUPT> >>> U-Boot# >>> U-Boot# >>> U-Boot# i2c md 0x50 0 0x10 >>> 0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ >>> U-Boot# >>> >>> U-Boot# i2c mw 0x50 0 0x10 0xAA >>> U-Boot# i2c md 0x50 0 0x10 >>> 0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ >>> U-Boot# i2c md 0x50 0 0x10 >>> 0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ >>> >>> -- >>> >>> >>> >> >> >> >> -- >> Gerald >> >> ger...@beagleboard.org >> g-co...@ti.com >> http://beagleboard.org/ >> http://circuitco.com/support/ >> >> -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
