Hi Ben
a long long time ago the EE prom was working nice for me.
http://www.matrixtsl.com/mmforums/viewt ... ilit=24c32
Now I can just write or read one adress. Thats mean I have to disable the rest. If not, the program is hanging.
With much patience, I can write and read ABC....
I use a PIC32MZ2048EFG100
EE Prom 24C32
Moderator: Benj
-
- Valued Contributor
- Posts: 654
- Joined: Fri Aug 19, 2016 2:09 pm
- Location: switzerland
- Has thanked: 182 times
- Been thanked: 179 times
- Contact:
-
- Valued Contributor
- Posts: 1189
- Joined: Wed May 31, 2017 11:57 am
- Has thanked: 70 times
- Been thanked: 439 times
- Contact:
Re: EE Prom 24C32
Hi Stefan,
I'm just working on a i2c eeprom component (actually for the 24lc256) - there is an early draft in my post here: viewtopic.php?f=26&t=21723 (as a program - but I tried as a component yesterday)
This allows block reads / writes and uses the chip features (multi-byte writes/reads - so is a lot faster esp on writes - the current component taking 5ms per byte!)
It doesn't quite work - there is a 'skipped' byte at page boundaries in the posted code - hope to fix that tonight. But have a look and any ideas on interface etc gratefully received. (Silly mistake - was skipping back to start of buffer every time it rewrote the address to the eeprom)
So: Fixed the problem and exported as component.
Try: Note that this a 'barebones' component - there is no code to fill in default values - so just set all the properties.
Just tested reading 768 bytes to WS2812B array using Which is a (slight) kludge to load the entire buffer without using another buffer, and in a single call (rather than doing it in a loop) - works well....
Not sure how the 24c32 differs - but should be possible to modify to suit?
Martin
I'm just working on a i2c eeprom component (actually for the 24lc256) - there is an early draft in my post here: viewtopic.php?f=26&t=21723 (as a program - but I tried as a component yesterday)
This allows block reads / writes and uses the chip features (multi-byte writes/reads - so is a lot faster esp on writes - the current component taking 5ms per byte!)
It doesn't quite work - there is a 'skipped' byte at page boundaries in the posted code - hope to fix that tonight. But have a look and any ideas on interface etc gratefully received. (Silly mistake - was skipping back to start of buffer every time it rewrote the address to the eeprom)
So: Fixed the problem and exported as component.
Try: Note that this a 'barebones' component - there is no code to fill in default values - so just set all the properties.
Just tested reading 768 bytes to WS2812B array using Which is a (slight) kludge to load the entire buffer without using another buffer, and in a single call (rather than doing it in a loop) - works well....
Not sure how the 24c32 differs - but should be possible to modify to suit?
Martin
-
- Valued Contributor
- Posts: 654
- Joined: Fri Aug 19, 2016 2:09 pm
- Location: switzerland
- Has thanked: 182 times
- Been thanked: 179 times
- Contact:
Re: EE Prom 24C32
Hi Martin
Thank you for the support. I copied the component in both folder, but I can't see it in FC8.
C:\Program Files (x86)\Flowcode v8\DefaultData\FlowcodeV8\Component
C:\ProgramData\MatrixTSL\FlowcodeV8\Component
Yes I know I have to learn how to create a component...soon
I followed the Infos from the homepage
https://www.matrixtsl.com/wiki/index.ph ... _Component
regards
Stefan
Thank you for the support. I copied the component in both folder, but I can't see it in FC8.
C:\Program Files (x86)\Flowcode v8\DefaultData\FlowcodeV8\Component
C:\ProgramData\MatrixTSL\FlowcodeV8\Component
Yes I know I have to learn how to create a component...soon
I followed the Infos from the homepage
https://www.matrixtsl.com/wiki/index.ph ... _Component
regards
Stefan
-
- Valued Contributor
- Posts: 1189
- Joined: Wed May 31, 2017 11:57 am
- Has thanked: 70 times
- Been thanked: 439 times
- Contact:
Re: EE Prom 24C32
To install the component - save to a directory (probably best not to use the FC component folder) - then tell FC where to look for new components.
(View - Global Options - Locations) - add the directory to the 'Look for Components In' box.. I usually do a 'Refresh Component Cache' - though I'm not sure if it is needed.
- I think you'll find the component under Misc - but easiest using Search (I2C_EEPROM)
The i2c address of the eeprom is hardcoded (as it is in the FC component) - with A2..A0 as a property. I'm sure I read some where that all the chips have the same basic address - but if this is not the case then it would be easy to add an extra property (or change the control bits to the whole address).
Martin
(View - Global Options - Locations) - add the directory to the 'Look for Components In' box.. I usually do a 'Refresh Component Cache' - though I'm not sure if it is needed.
- I think you'll find the component under Misc - but easiest using Search (I2C_EEPROM)
The i2c address of the eeprom is hardcoded (as it is in the FC component) - with A2..A0 as a property. I'm sure I read some where that all the chips have the same basic address - but if this is not the case then it would be easy to add an extra property (or change the control bits to the whole address).
Martin
-
- Valued Contributor
- Posts: 654
- Joined: Fri Aug 19, 2016 2:09 pm
- Location: switzerland
- Has thanked: 182 times
- Been thanked: 179 times
- Contact: