guangzong/stm32-data
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

OCTOSPI: Fix "MAXTRAN was in wrong yaml".

Browse Source
This commit is contained in:
JackN 2023-10-12 18:52:50 -04:00
parent af1a5f5877
commit 019e802e27
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
data/registers/octospi_v1.yaml
View File

@ -294,6 +294,10 @@ fieldset/DCR2:
fieldset/DCR3: fieldset/DCR3:
description: device configuration register 3 description: device configuration register 3
fields: fields:
- name: MAXTRAN
description: Maximum transfer
bit_offset: 0
bit_size: 8
- name: CSBOUND - name: CSBOUND
description: 'NCS boundary. This field enables the transaction boundary feature. When active, a minimum value of 3 is recommended. The NCS is released on each boundary of 2CSBOUND bytes. others: NCS boundary set to 2CSBOUND bytes' description: 'NCS boundary. This field enables the transaction boundary feature. When active, a minimum value of 3 is recommended. The NCS is released on each boundary of 2CSBOUND bytes. others: NCS boundary set to 2CSBOUND bytes'
bit_offset: 16 bit_offset: 16

4
data/registers/octospi_v2.yaml
View File

@ -294,10 +294,6 @@ fieldset/DCR2:
fieldset/DCR3: fieldset/DCR3:
description: device configuration register 3 description: device configuration register 3
fields: fields:
- name: MAXTRAN
description: Maximum transfer
bit_offset: 0
bit_size: 8
- name: CSBOUND - name: CSBOUND
description: 'NCS boundary. This field enables the transaction boundary feature. When active, a minimum value of 3 is recommended. The NCS is released on each boundary of 2CSBOUND bytes. others: NCS boundary set to 2CSBOUND bytes' description: 'NCS boundary. This field enables the transaction boundary feature. When active, a minimum value of 3 is recommended. The NCS is released on each boundary of 2CSBOUND bytes. others: NCS boundary set to 2CSBOUND bytes'
bit_offset: 16 bit_offset: 16