test_field_inheritance_via_derived_from
For this feature, test cases cover scenarios where a derived field inherits properties from a base field, ensuring correct behavior when values are inherited.
test_circular_inheritance
This test case examines a scenario where circular inheritance occurs between two fields within the same
register (FieldA
and FieldB
). In the SVD file, FieldA
is defined to derive from FieldB
, and FieldB
is set to derive from FieldA
. This creates a circular dependency, which a robust parser should detect and
prevent from causing infinite loops or incorrect behavior. Circular inheritance should be considered invalid
and should raise an appropriate error during processing.
Expected Outcome: The parser should identify the circular dependency between FieldA
and FieldB
and raise
an error, indicating that circular inheritance is not supported. This ensures that the system correctly
handles such invalid configurations by stopping further processing and notifying the user of the issue.
Processable with svdconv: no
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 |
|
SVD file: field_inheritance_via_derivedfrom/circular_inheritance.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 |
|
test_derive_from_self
This test case evaluates a scenario where a field attempts to derive from itself, creating an invalid
configuration. In the SVD file, FieldA
is defined with a derivedFrom
attribute pointing to its own name.
Such configurations should be detected as erroneous because a field cannot logically inherit properties from
itself. This kind of self-reference should lead to a parsing error.
Expected Outcome: The parser should detect the invalid self-referential inheritance and raise an error, indicating that a field cannot derive from itself. This ensures that the system handles such configurations correctly by stopping further processing and informing the user of the issue.
Processable with svdconv: no
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 |
|
SVD file: field_inheritance_via_derivedfrom/derive_from_self.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 |
|
test_enumerated_value_inheritance_error
This test case examines a situation where a derived field (FieldB
) inherits properties from a base field
(FieldA
) but also attempts to redefine enumerated values that are incompatible with the inherited ones. The
SVD file presents FieldB
using the derivedFrom
attribute to inherit from FieldA
, but it adds a new set
of enumerated values under the same usage type (read-write
), which causes a conflict.
Expected Outcome: The parser should detect the conflict and raise an error because FieldB
is attempting to
redefine enumerated values that already exist under the read-write
usage inherited from FieldA
. svdconv
correctly identifies this issue and generates an error, stating that the enumerated value container for read-
write
is already defined. A robust parser should replicate this behavior, ensuring that redefinition of
inherited enumerated values does not occur without explicitly overriding the existing container.
Processable with svdconv: no
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 |
|
SVD file: field_inheritance_via_derivedfrom/enumerated_value_inheritance_error.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 |
|
test_multiple_inheritance_backward_reference
This test case focuses on a scenario where multiple fields (FieldB
and FieldC
) inherit properties from a
base field (FieldA
) within the same register, using the derivedFrom
attribute. FieldB
is derived from
FieldA
, and FieldC
is further derived from FieldB
. The purpose is to verify that the parser correctly
handles this chain of inheritance, ensuring that inherited attributes, such as enumerated values, are properly
applied.
Expected Outcome: The parser should correctly process the SVD file, allowing FieldB
to inherit attributes
from FieldA
and FieldC
to inherit from FieldB
. Each of the fields (FieldA
, FieldB
, and FieldC
)
should have the same enumerated value container as defined in FieldA
. The attributes such as bitOffset
and
bitWidth
should be overridden as defined for each field. The parser should handle this without issues,
consistent with svdconv
, which successfully processes this file.
Processable with svdconv: yes
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 |
|
SVD file: field_inheritance_via_derivedfrom/multiple_inheritance_backward_reference.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 |
|
test_multiple_inheritance_forward_reference
This test case involves multiple fields (FieldA
, FieldB
, FieldC
) where FieldA
is derived from
FieldB
, and FieldB
is derived from FieldC
, using forward references within the same register. Despite
svdconv
's inability to handle forward references, a robust parser should correctly resolve these references
and apply the inherited properties as expected. The goal is to ensure that the parser can accurately manage
such chains of inheritance and still process the register and its fields without errors.
Expected Outcome: The parser should successfully handle the forward references, allowing FieldA
to inherit
attributes from FieldB
, and FieldB
to inherit from FieldC
. All three fields should ultimately share the
same enumerated value container, defined in FieldC
. Each field should also correctly override attributes
like bitOffset
as specified in the SVD file. This ensures compatibility and robustness beyond svdconv
's
current limitations.
Processable with svdconv: no
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 |
|
SVD file: field_inheritance_via_derivedfrom/multiple_inheritance_forward_reference.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 |
|
test_overlap_bit_range
This test case examines a scenario where two fields within a register are defined to have overlapping bit
ranges. In the SVD file provided, FieldA
is explicitly defined with a bit offset of 0
and a width of 2
,
while FieldB
is derived from FieldA
but is redefined with a bit offset of 1
and a width of 1
. This
configuration causes FieldB
to overlap with the range occupied by FieldA
, leading to an invalid layout.
Expected Outcome: The parser should detect the overlapping bit ranges between FieldA
and FieldB
and raise
an error. This behavior ensures that fields are uniquely positioned within a register, preventing any
conflicts in field interpretation or usage. Notably, svdconv
exhibits the same behavior, issuing an error
when it encounters this type of overlap.
Processable with svdconv: no
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 |
|
SVD file: field_inheritance_via_derivedfrom/overlap_bit_range.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 |
|
test_override_behavior
This test case evaluates the behavior of field inheritance where a derived field (FieldB
) inherits
properties from a base field (FieldA
) and overrides certain attributes. The SVD file illustrates how
FieldB
utilizes the derivedFrom
attribute to inherit from FieldA
while customizing some of its
properties such as the description, access type, and enumerated values.
Expected Outcome: The parser should correctly handle the inheritance, allowing FieldB
to override the
specified attributes without affecting the inherited properties. The test verifies that FieldB
successfully
overrides the required fields and adds its own enumerated value set without duplicating or conflicting with
those of FieldA
. This behavior is consistent with svdconv
. The parsing should complete without errors, and
the attributes should match the expected results based on the SVD definitions.
Processable with svdconv: yes
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 |
|
SVD file: field_inheritance_via_derivedfrom/override_behavior.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 |
|
test_same_bit_range
This test case addresses a scenario where two fields in a register are defined to occupy the same bit range.
In the provided SVD file, FieldA
is explicitly defined with a bit offset of 0
and a width of 1
, and
FieldB
is derived from FieldA
, also attempting to use the same bit offset and width. This creates an
overlap, which is not allowed as it leads to conflicting field definitions within the same register.
Expected Outcome: The parser should detect the overlap between FieldA
and FieldB
and raise an error,
indicating that both fields are trying to occupy the same bit range. This behavior aligns with svdconv
,
which also detects and reports such conflicts as error.
Processable with svdconv: no
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 |
|
SVD file: field_inheritance_via_derivedfrom/same_bit_range.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 |
|
test_simple_inheritance_backward_reference_different_scope
This test case examines field inheritance using the derivedFrom
attribute, where the field being inherited
from (FieldA
) is defined within a different register (RegisterA
) scope, but in the same peripheral, which
requires the full qualifying path (PeripheralA.RegisterA.FieldA
). In the SVD file, RegisterA
explicitly
defines FieldA
with bit properties and enumerated values. RegisterB
defines a field also named FieldA
,
which uses the derivedFrom
attribute to inherit properties from the previously defined FieldA
in
RegisterA
.
Expected Outcome: The parser should correctly process the SVD file, allowing RegisterB.FieldA
to inherit all
properties, including enumerated values, from RegisterA.FieldA
. This should include identical bit
positioning, usage, and enumerated values. Parsing should complete without any issues, consistent with the
expected behavior of svdconv
, which successfully handles backward references across different registers in
the same peripheral scope.
Processable with svdconv: yes
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 |
|
SVD file: field_inheritance_via_derivedfrom/simple_inheritance_backward_reference_different_scope.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 |
|
test_simple_inheritance_backward_reference_same_scope
This test case focuses on field inheritance using the derivedFrom
attribute within the same register. Here,
FieldB
inherits properties from FieldA
, which is defined earlier within the same register. In the SVD
file, FieldA
is explicitly set up with bit offset 0
and width 1
, along with enumerated values for read-
write
usage. FieldB
is derived from FieldA
, meaning it should inherit all attributes, including the
enumerated values, while being positioned at a different bit offset (1
).
Expected Outcome: The parser should correctly interpret the inheritance, processing FieldB
as a field that
inherits all attributes from FieldA
, including its enumerated values. The result should show FieldA
at bit
offset 0
and FieldB
at bit offset 1
, both sharing the same enumerated value containers. Parsing should
complete without issues, consistent with svdconv
, which handles this scenario correctly.
Processable with svdconv: yes
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 |
|
SVD file: field_inheritance_via_derivedfrom/simple_inheritance_backward_reference_same_scope.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 |
|
test_simple_inheritance_forward_reference_different_scope
This test case evaluates field inheritance using the derivedFrom
attribute, where the field being inherited
(FieldA
) is defined in a different register (RegisterB
) within the same peripheral. However, the field in
RegisterA
uses a forward reference, meaning it tries to derive properties from RegisterB.FieldA
before
RegisterB
is defined. In the provided SVD file, RegisterB.FieldA
is explicitly defined with bit properties
and enumerated values. RegisterA.FieldA
attempts to inherit these properties via a forward reference.
Expected Outcome: The parser should inherit successfully from RegisterB.FieldA
. svdconv
does not handle
forward references and raises an error.
Processable with svdconv: no
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 |
|
SVD file: field_inheritance_via_derivedfrom/simple_inheritance_forward_reference_different_scope.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 |
|
test_simple_inheritance_forward_reference_same_scope
This test case examines field inheritance using the derivedFrom
attribute within the same register, where
the field being inherited from (FieldB
) is defined later in the register than the derived field (FieldA
).
In the SVD file, FieldA
uses the derivedFrom
attribute to reference FieldB
, which is defined afterward,
with its enumerated values and other attributes.
Expected Outcome: The parser should correctly resolve the forward reference, allowing FieldA
to inherit all
properties from FieldB
, including enumerated values. Both FieldA
and FieldB
should be processed, with
FieldA
at bit offset 0
and FieldB
at bit offset 1
, sharing the same enumerated value containers.
Parsing should proceed without issues if the parser handles forward references properly. Unlike svdconv
,
which raises an error due to its inability to handle such cases, a more robust parser should accommodate this
scenario seamlessly.
Processable with svdconv: no
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 |
|
SVD file: field_inheritance_via_derivedfrom/simple_inheritance_forward_reference_same_scope.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 |
|
test_value_inheritance
This test case examines field inheritance through the derivedFrom
attribute, ensuring that all the
properties from a base field (FieldA
) are correctly inherited by a derived field (FieldB
). In the provided
SVD file, FieldA
is defined with various attributes, including description, access type, write constraint,
and enumerated value. FieldB
is set to inherit all these properties from FieldA
, while adjusting its
position within the register.
Expected Outcome: The parser should correctly process the SVD file, allowing FieldB
to inherit all
properties from FieldA
, such as the description, access type, modified write value, write constraint, and
enumerated value. The only changes should be the bitOffset
and bitWidth
adjustments as specified for
FieldB
. This behavior is consistent with svdconv
, which successfully handles such backward inheritance
cases within the same register scope. The parsing should complete without errors, and the inherited properties
should be accurately reflected in FieldB
.
Processable with svdconv: yes
Source code in tests/test_process/test_field_inheritance_via_derived_from.py
276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 |
|
SVD file: field_inheritance_via_derivedfrom/value_inheritance.svd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 |
|