What is TOTR in “Chapter 33 Cyclic Redundancy Check (CRC)” section of Vybrid Reference Manual?

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

What is TOTR in “Chapter 33 Cyclic Redundancy Check (CRC)” section of Vybrid Reference Manual?

ソリューションへジャンプ
1,892件の閲覧回数
naoumgitnik
Senior Contributor V

On behalf of LilyZhang:

"It is present on the block diagram, but not mentioned on the register descriptions. May you comment on that, please?"

I'll look into it; it will take several days to clarify it.

Regards, Naoum Gitnik.

ラベル(5)
0 件の賞賛
返信
1 解決策
1,499件の閲覧回数
naoumgitnik
Senior Contributor V

On behalf of Lily Zhang:

Thanks for your help, Edward!

According to the reply from the Vybrid IC design team, "this feature is not used on Vybrid", and we will have to fix our documentation.

Regards, Naoum Gitnik.

元の投稿で解決策を見る

0 件の賞賛
返信
2 返答(返信)
1,499件の閲覧回数
kef2
Senior Contributor V

Naoum,

DS-5 debugger shows TOT and TOTR bits defined in CRC_CTRL register. According to descriptions provided in DS-5 debugger registers view and according to Figure 33-1 in Vybrid RM Rev 5, these bits should control byte and/or bits transposition on input side (TOT) and output side (TOTR) of CRC block. According to DS-5 5.16, TOT are CTRL bits 31:30 and TOTR are CTRL bits 29:28.

I tried toggling TOT and TOTR bits in debugger but didn't notice any change in resulting CRC. I guess TOT and TOTR blocks are removed, at least in 1N02G maskset. It seems Figure 33-1 need an update.

BTW output registers are in low endian format, which is fine for me. Input requires byte reversal, TOT bits could help here.

IMO TCRC bit also could be removed. TCRC=0 is 16-bit mode, TCRC=1 is 32-bit mode. On 32-bit CPU I think it is much better to feed CRC unit with 4 bytes at once, even when calculating 16-bit CRC. See attached source for CRC16 CCIT (poly=1021).

1,500件の閲覧回数
naoumgitnik
Senior Contributor V

On behalf of Lily Zhang:

Thanks for your help, Edward!

According to the reply from the Vybrid IC design team, "this feature is not used on Vybrid", and we will have to fix our documentation.

Regards, Naoum Gitnik.

0 件の賞賛
返信