DS2431 erasing issue

Here you can ask technical questions about REVELPROG-IS and device/memory programming.
rsm
Posts: 11
Joined: Thu Feb 15, 2024 3:42 am
Has thanked: 8 times

DS2431 erasing issue

Postby rsm » Thu Feb 15, 2024 4:03 am

I have a DS2431 (tsoc-6 package); I just purchased the revel prog-IS programmer and am very new to this kind of device.

Reading seems fine, it is as follows:
https://drive.google.com/file/d/1WeYGdo ... sp=sharing

When I try to erase memory, all seem to be deleted:
https://drive.google.com/file/d/1w7Irqh ... sp=sharing

But when I click read memory, I still have the first two lines of the code, they are not deleted:
https://drive.google.com/file/d/1odi1RV ... drive_link

My questions are:
1- Is it possible to delete the first two lines and set the chip as totally empty?
2- Will a brand new DS2431 TO-92 packaging have the same issue?


Regards

ArT
Posts: 1539
Joined: Wed Mar 25, 2015 8:54 am
Location: Warsaw, Poland
Has thanked: 56 times
Been thanked: 166 times

Re: DS2431 erasing issue

Postby ArT » Thu Feb 15, 2024 9:52 am

It seems to me that it's communiation issue. Please show me how did you connected this TSOC-6 - it's important to make the same length of wires and if you are programming in external circuit - it should be not any additional elements on communication line. REVELPROG-IS was tested with DS2431 TO92 package.

rsm
Posts: 11
Joined: Thu Feb 15, 2024 3:42 am
Has thanked: 8 times

Re: DS2431 erasing issue

Postby rsm » Thu Feb 15, 2024 12:51 pm

Thank you for the reply.

I tried multiple times, same issue. It is directly connected to the chip as described.

This chip has eight rows of bytes; rows 0000 and 0001 seem to be fixed and not affected by erasing, but the rest 6 I can erase, modify and save as long as the top two rows have not been modified.

Is it possible they locked the top two rows? I'm definitely trying it on a 92 packaging now. Are the packaging interchangeable in function? Now I'm worried it may not work as expected :D.


Kind regards

ArT
Posts: 1539
Joined: Wed Mar 25, 2015 8:54 am
Location: Warsaw, Poland
Has thanked: 56 times
Been thanked: 166 times

Re: DS2431 erasing issue

Postby ArT » Thu Feb 15, 2024 3:52 pm

Here you have datasheet:
https://www.analog.com/media/en/technic ... DS2431.pdf

Memory is organized to 4 pages each 256bits and each page can be permanently Write Protected. You can read control bytes using custom script tool from addresses >=0x80 as described in datasheet page 7/27

Please check this topic:
viewtopic.php?f=32&t=699&p=3130&hilit=ds2431

rsm
Posts: 11
Joined: Thu Feb 15, 2024 3:42 am
Has thanked: 8 times

Re: DS2431 erasing issue

Postby rsm » Fri Feb 16, 2024 10:46 pm

The link helps a lot, thank you.

Ok, so we have:
4 protection control bytes
1 copy protection byte
1 factory byte
2 user bytes
= 8 bytes in total

First five bytes If programmed to AAh or 55h, it can not be erased. Factory bytes are read-only, so they are definitely not erasable, but 2x user bytes are erased and rewritten all day.

Now if I use the revelprog-is software as it is to write in UI, is it programming to AAh or 55h by default?

Does their status as write-protected somehow affect their readability? Or 10/10 chips, would you be able to read the chips completly?

Regards

ArT
Posts: 1539
Joined: Wed Mar 25, 2015 8:54 am
Location: Warsaw, Poland
Has thanked: 56 times
Been thanked: 166 times

Re: DS2431 erasing issue

Postby ArT » Mon Feb 19, 2024 9:57 am

It does not change any bytes in this register. After programming standard eeprom area, control bytes stays the same. You need to change them intentionally e.g. with custom script.

Many chips have some configuration or protection bytes which are not accessed in standard usable range addresses.

rsm
Posts: 11
Joined: Thu Feb 15, 2024 3:42 am
Has thanked: 8 times

Re: DS2431 erasing issue

Postby rsm » Wed Feb 21, 2024 9:27 am

Now, I'm talking very specifically about the programmer device and its app. If I write on a brand new DS2431 chip, will it write-protect it by default at address 0080h* to 0084h*?

Basically, what I'm asking is what is the difference between writing and reading via app UI functions, and customs scripts mentioned?

Regards

ArT
Posts: 1539
Joined: Wed Mar 25, 2015 8:54 am
Location: Warsaw, Poland
Has thanked: 56 times
Been thanked: 166 times

Re: DS2431 erasing issue

Postby ArT » Wed Feb 21, 2024 10:15 am

When you select DS2431 from memory database you can read/write standard memory area (0x00 - 0x7F) - data memory page 0,1,2 and 3. Additional registers (0x80 - 0x8F) are untouched.

With custom script tool you can do anything. You can read/write single bytes at specific addr, you can modify additional registers, you can use it for automation etc. You can also make standard read (0x00 - 0x7F) and results will be the same as when you select DS2431 from database.
Attachments
2024-02-21 101616.png
2024-02-21 101616.png (62.44 KiB) Viewed 2520 times

rsm
Posts: 11
Joined: Thu Feb 15, 2024 3:42 am
Has thanked: 8 times

Re: DS2431 erasing issue

Postby rsm » Sat Feb 24, 2024 4:09 pm

This explains a lot, thank you.

How would you approach the task of storing the content of a DS2431 and copying it entirely on a new DS2431?

I don't see a customer script for reading/writing all the address ranges.


Kind regards

ArT
Posts: 1539
Joined: Wed Mar 25, 2015 8:54 am
Location: Warsaw, Poland
Has thanked: 56 times
Been thanked: 166 times

Re: DS2431 erasing issue

Postby ArT » Mon Feb 26, 2024 12:11 pm

Because content is only on addr range 0x0 - 0x7F.

If you would like to set protection bytes you will need to do it with script. You can make own script and use it with automatic mode viewtopic.php?f=32&t=913


Return to “Technical Support”

Who is online

Users browsing this forum: No registered users and 1 guest

cron