Question about Silicon Motion XOR modified by Bad bytes?

[Gregory]

Feedback about VNR 8.2 and SM XOR mod by BB:

It looks like it works but there is one problem - determining the structure in which BBs occur, i.e. the automatic key options XOR structure does not work because we cannot determine different lengths of "as Data area" for sectors.

This has to be done manually

There are several ways to fix this - you could allow different sector lengths to be specified for "set as Data area" or, to avoid damaging the integrity of the VNR software, add a new "set as XOR Data area" option with different sector lengths.

Anyway, this new features is good improvment.

[Sasha Sheremetov]

there is one problem - determining the structure in which BBs occur, i.e. the automatic key options XOR structure does not work because we cannot determine different lengths of "as Data area" for sectors.

This has to be done manually

Thanks a lot for a very useful feedback!
I'll show this to my teammates and we brainstorm how/if to improve this.

[Igor_Loskutov]

I'm not quite sure if I understood correctly, but it seems you use it not right. There will be a webinar next week, we'll show how it works.
In short, you do not need to define any custom structure here. You firstly remove bad columns with BCR, structure has not to be defined there. Then, after bad columns are removed, you set the normal correct structure. And later you connect the AI SM XOR. The XOR will be generated taking into account bad columns specified one step before.

[Gregory]

In short, you do not need to define any custom structure here. You firstly remove bad columns with BCR, structure has not to be defined there. Then, after bad columns are removed, you set the normal correct structure. And later you connect the AI SM XOR.

You write differently on the Rusolut website "The AI SM XOR generator can now automatically generate XOR key onto the bad columns, when connected before Bad Column Remover (BCR) element." ??

I think I did that too after BCR, but I don't remember whether the XOR was bad then or whether it was generating very slowly. My method generated the correct XOR and did it lightning fast, and case was sucesfully done. I'll check tomorrow and let you know.

Attachments

[Gregory]

In short, you do not need to define any custom structure here. You firstly remove bad columns with BCR, structure has not to be defined there. Then, after bad columns are removed, you set the normal correct structure. And later you connect the AI SM XOR. The XOR will be generated taking into account bad columns specified one step before.

OK, it also works, so you have the wrong description on the website I suggested.

[Igor_Loskutov]

In short, you do not need to define any custom structure here. You firstly remove bad columns with BCR, structure has not to be defined there. Then, after bad columns are removed, you set the normal correct structure. And later you connect the AI SM XOR. The XOR will be generated taking into account bad columns specified one step before.

OK, it also works, so you have the wrong description on the website I suggested.

ooops
This is what happens when a person writes description in the last day before vacation Thank you for the input, it is fixed.