Interfacing to the ...
 
Notifications
Clear all

Interfacing to the EERPOM's

8 Posts
5 Users
0 Reactions
6,301 Views
Posts: 789
Topic starter
(@chilloutdocdoc)
Prominent Member
Joined: 18 years ago
[#15569]

Has anybody worked at interfacing with the EEPROM's onboard yet? I'm working on the serial configuration, and it's starting to come along, but it's useless unless we can save the data for future use.

Josh


7 Replies
RPM
Posts: 1080
 RPM
(@rpm)
Noble Member
Joined: 19 years ago
chilloutdocdoc wrote:Has anybody worked at interfacing with the EEPROM's onboard yet? I'm working on the serial configuration, and it's starting to come along, but it's useless unless we can save the data for future use.

Josh

Since I'm not yet up to speed on using the code repository, I'll upload here for the moment.

I am attaching a PropController variant of my E1.31 (sACN) to DMX Bridge firmware.
This firmware is adapted from my board design, so it works pretty much the same with the exception of the LED routines, which have been adapted to the bi-color type
used on the PropController. I did my initial debugging on the PropController before I had my boards made up, so this is fully operational code.

It requires a "MODE" pushbutton switch attached to port 4 with a 4.7K pullup resistor to 3.3 volts for some functions to work, and the DMX I/O port pins are defined in the code.

This should give you examples of how to access the EEPROM and MAC IC for read/write operations.

Keep in mind that the "E1.31 DMX Bridge setup and operation (FW V1.00)" was written specifically for my E1.31 Bridge board, so the references to the LED and MODE switch operations will be different for the PropController, but the web interface commands and other setup info is pertinent to the firmware.

Robert


Reply
Posts: 2630
(@dynamoben)
Famed Member
Joined: 19 years ago

The basic I2C object will allow you to write to the bottom 32K of the EEProm. Beyond that pmscientist has some code for the MAC address EEProm.


Reply
Posts: 352
(@pmscientist)
Reputable Member
Joined: 16 years ago

There are a couple other i2c objects as well. I haven't tried those to see if they might support >32k address space. Files with code for detecting, reading, and using the MAC EEPROM have just been uploaded to the dev branch. One thing I've thought about, but haven't added is checking for bad data. Other than verifying the first 3 bytes, which would vary by manufacturer, I'm not sure how that would happen really, as I'm only taking the first byte. I can see getting a value other than that held on the chip, but a byte is a byte in this case. Is data verification worth pursuing in this case?

For what it's worth, the datasheet for the 24C1024 EEPROM shows the use of 2 bytes when specifying the address for read/write. Big endian order in that case. While the basic i2c object only allows for a 1 byte address, extending that with support for 2 byte memory addressing wouldn't be difficult if one of the other libraries doesn't already support that.


Reply
Posts: 2630
(@dynamoben)
Famed Member
Joined: 19 years ago

I started work to implement the MAC address eeprom in the ETH_128 project. James gave me a huge head start by modifying the Basic_I2C object, all I'm doing is optimizing the code. At the moment its in the dev branch, I expect to move it over in the coming days.


Reply
Posts: 1249
(@jstjohnz)
Noble Member
Joined: 17 years ago

The standard I2C object (Basic_I2C_Driver) will work without modification to address up to 64K bytes on 512kb eeproms, and will work without modification to access up to 128KB on the Atmel 1mb eeprom. Other manufacturers 1mb eeproms are not compatible as far as I know.


Reply
Posts: 2630
(@dynamoben)
Famed Member
Joined: 19 years ago
jstjohnz wrote:The standard I2C object (Basic_I2C_Driver) will work without modification to address up to 64K bytes on 512kb eeproms, and will work without modification to access up to 128KB on the Atmel 1mb eeprom. Other manufacturers 1mb eeproms are not compatible as far as I know.

The problem is that the standard I2C object assumes a word sized address, whereas the MAC address EEProm I'm using utilizes a byte sized address. To that end a couple of minor changes were made.


Reply
Posts: 2630
(@dynamoben)
Famed Member
Joined: 19 years ago

I have updated the main ETH_128 project, it now supports the MAC address EEProm and the one that is hard programmed in the code.


Reply
Share: