I found the solution ATMEL used to manufacture a 24c01. I performed the following-
root@beaglebone:~# echo 24c01 0x50 > /sys/bus/i2c/devices/i2c-1/new_device root@beaglebone:~/BBB-mikroBus-Cape# echo "This is a test" > /sys/bus/i2c/devices/1-0050/eeprom root@beaglebone:~/BBB-mikroBus-Cape# cat /sys/bus/i2c/devices/1-0050/eeprom | hexdump -C | more 00000000 54 68 69 73 20 69 73 20 61 20 74 65 73 74 0a ff |This is a test..| 00000010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00000080 I think the mikroBus capes and click boards are going to be a lot of fun. I'm going to use the ADFruit python libraries as a basis. The Logibone FPGA cape is also working well for me. Really having fun. On Saturday, August 1, 2015 at 6:27:14 PM UTC-7, Michael Carr wrote: > > I have a quick question about supported i2c eeprom types. > > From the user side is there a way to query/list supported types (ie. > 24c256)? > Conversely, is there a way to define a new type from user space and add > it, maybe through i2c-1/new_device? > > Documentation other than the SRM? > > Thanks! > > > On Thursday, July 30, 2015 at 8:42:05 AM UTC-7, Michael Carr wrote: >> >> Hi Robert, Jason and William, >> >> Sorry for not pulling the device tree files, I've been out of town. I >> hope the files help someone in the future if they purchase a mikroBus cape. >> >> This morning I found that the mikroBus cape is using a Microchip 24AA01 >> (1K, 128 x 8) eeprom not a 24C256. Two questions came to mind after I found >> this out. >> >> 1.) The Microchip 24AA01 doesn't use A0 ~ A2 (Don't Care). Responds to >> any 0x5X address. Potential cape addressing conflicts here. >> 2.) The non-B version clock is limited to 100Khz. >> >> Is the default clock for i2c bus 1 > 100khz? Ex. 400Khz 1000Khz? Can I >> force it to 100 Khz? >> >> Yep, having problems writing to the eeprom. The schematics don't agree >> with the delivered board. >> Looks like they intended to use the 24C256 but in manufacturing they used >> the 24AA01 instead. >> >> Mike >> >> >> On Monday, July 27, 2015 at 10:27:54 AM UTC-7, RobertCNelson wrote: >>> >>> Thanks! Pushed as part of: >>> >>> >>> https://github.com/RobertCNelson/bb-kernel/commit/c43f83c076c30cfbd98d4c00f962ca22a9563933 >>> >>> >>> On Thu, Jul 16, 2015 at 10:59 AM, Michael Carr <[email protected]> wrote: >>> > Hi Robert, >>> > >>> > I've ordered a MikroBus cape from MikroElektronica. They have a device >>> tree >>> > source file to support the cape. May I pass it along to you to add to >>> > github? >>> > >>> > The eeprom on the card is empty and I will need to generate the >>> contents. >>> > Does anyone have a tool to create/read/write eeprom contents via >>> cloud9? I >>> > tried running eeprom-web.js and I get a cloud9 error. >>> > >>> > Thanks, >>> > Mike >>> > >>> > -- >>> > 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]. >>> > For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> -- >>> 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]. For more options, visit https://groups.google.com/d/optout.
