test_cluster_inheritance_via_derived_from
For this feature, test cases cover scenarios where a derived cluster inherits properties from a base cluster, ensuring correct behavior when values are inherited.
test_alternate_cluster
This test case assesses the correct handling of the alternateCluster
feature in the SVD file, which allows
one cluster to act as an alternate version of another. In this scenario, ClusterB
is derived from ClusterA
and is marked as an alternate cluster by specifying ClusterA
in the <alternateCluster>
tag. Both clusters
share the same address offset (0x0
), implying that they can be used interchangeably, depending on the use
case.
Expected Outcome: The parser should correctly interpret ClusterB
as an alternate of ClusterA
. It should
process the derivedFrom
attribute, allowing ClusterB
to inherit all characteristics from ClusterA
.
Additionally, the parser should recognize the <alternateCluster>
tag and confirm that ClusterB
is
designated as an alternate of ClusterA
. Both clusters should be treated as residing at the same address
offset (0x0
), with ClusterA
having no alternateCluster
association, while ClusterB
explicitly
references ClusterA
. The parsing process should proceed without errors or warnings, consistent with the
behavior of svdconv
, which correctly handles this feature.
Processable with svdconv: yes
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 |
|
SVD file: cluster_inheritance_via_derivedfrom/alternate_cluster.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 |
|
test_circular_inheritance
This test case examines how the parser handles scenarios where clusters are involved in circular inheritance.
In this setup, ClusterA
, which is defined first in the SVD file, is set to inherit from ClusterB
.
Conversely, ClusterB
is also configured to inherit from ClusterA
. This creates a loop of inheritance,
which is logically invalid and should not be allowed. Proper parsing should identify this circular reference
and raise an error, preventing further processing. Circular inheritance could lead to infinite loops or
unresolved dependencies if not handled correctly.
Expected Outcome: The parser should detect the circular inheritance between ClusterA
and ClusterB
and
raise an appropriate error, indicating that circular references are not supported. Unlike some other complex
inheritance scenarios, where forward or backward references might be resolved by proper linkage, circular
inheritance represents a fundamental logical flaw.
Processable with svdconv: no
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 |
|
SVD file: cluster_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 47 48 |
|
test_cluster_overlap
This test case evaluates how the parser handles overlapping clusters within a peripheral, where ClusterB
is
derived from ClusterA
but is assigned an address offset that causes an overlap. In the SVD file, ClusterA
is defined at address offset 0x0
with a size of 16
, and ClusterB
, derived from ClusterA
, is placed at
address offset 0x1
with a size of 8
. This configuration leads to overlapping address ranges for these
clusters. While svdconv
processes this file without detecting the overlap, this behavior appears to be a
bug. Ideally, a parser should issue a warning to alert the user of the overlap, ensuring that any unintended
address conflicts are recognized and can be corrected.
Expected Outcome: The parser should correctly process the SVD file, identifying both ClusterA
and ClusterB
while issuing a warning to indicate that their address ranges overlap. Specifically, ClusterA
occupies the
range starting at 0x0
for 16
bytes, and ClusterB
starts at 0x1
with a size of 8
, causing the two
clusters to share overlapping addresses. The warning should provide clear information about which clusters are
affected and the nature of the overlap, giving users the necessary insights to address any configuration
issues in their SVD definitions.
Processable with svdconv: yes
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 |
|
SVD file: cluster_inheritance_via_derivedfrom/cluster_overlap.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 cluster attempts to derive from itself, creating an invalid
configuration. In the SVD file, ClusterA
is defined with a derivedFrom
attribute pointing to its own name.
Such configurations should be detected as erroneous because a cluster 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 cluster 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_cluster_inheritance_via_derived_from.py
801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 |
|
SVD file: cluster_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 |
|
test_multiple_inheritance_backward_reference
This test case evaluates how the parser handles multiple levels of inheritance using the derivedFrom
attribute. The scenario consists of three clusters: ClusterA
, defined as the base cluster; ClusterB
, which
derives from ClusterA
; and ClusterC
, which in turn derives from ClusterB
. The SVD file defines these
clusters in a backward-compatible order, starting with ClusterA
and then progressively building upon it with
ClusterB
and ClusterC
. This setup tests the parser's ability to correctly inherit properties across
multiple layers of derivation, ensuring that each derived cluster appropriately inherits all relevant
attributes from its predecessors.
Expected Outcome: The parser should successfully process the multiple inheritance chain, maintaining the
correct properties throughout each level. ClusterA
should be recognized as the base, with all its defined
properties and a register named RegisterA
. ClusterB
, derived from ClusterA
, should inherit all the base
attributes and the RegisterA
structure, located at a new offset, demonstrating that it has extended the
base. Finally, ClusterC
should inherit the cumulative properties from both ClusterA
and ClusterB
,
further verifying the parser's capability to manage complex inheritance patterns across multiple derived
entities. This behavior should mirror svdconv
's processing and ensure consistent, hierarchical inheritance.
Processable with svdconv: yes
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
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 |
|
SVD file: cluster_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 |
|
test_multiple_inheritance_forward_reference
This test case assesses the parser's handling of complex inheritance structures where the base cluster
(ClusterC
) is referenced by derived clusters (ClusterB
and ClusterA
) in a forward manner. In this setup,
the SVD file defines ClusterA
first, followed by ClusterB
, and finally ClusterC
, which serves as the
base for the other clusters. The derivedFrom
attribute is used to create a chain of inheritance starting
from ClusterC
as the base, with ClusterB
inheriting from it, and ClusterA
inheriting from ClusterB
.
This configuration challenges the parser to correctly resolve references even when the base entity appears
later in the file.
Expected Outcome: The parser should be able to process the forward references correctly, linking each derived
cluster back to its base cluster despite the forward order of definition. ClusterA
, appearing first in the
SVD file, should correctly inherit properties from ClusterB
, which in turn inherits from ClusterC
. Each
derived cluster should maintain the properties defined in its base and apply them consistently. ClusterA
,
ClusterB
, and ClusterC
should all include the expected attributes, registers, and configurations inherited
through the chain, confirming that the parser effectively handles forward inheritance. This contrasts with
svdconv
, which fails to process such forward references, making robust support for this feature a valuable
enhancement in the parser.
Processable with svdconv: no
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 |
|
SVD file: cluster_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 |
|
test_nested_cluster_inheritance
This test case explores the scenario where a cluster contains another cluster, and the inner cluster attempts
to inherit properties from its parent using the derivedFrom
attribute. In the provided SVD file, ClusterB
is nested within ClusterA
, and it is set to inherit from ClusterA
. This creates a situation where a
cluster is attempting to derive from its own parent, forming a nested inheritance pattern that is logically
flawed. Proper parsing should recognize that this setup is invalid because nested clusters should not inherit
from their parent clusters in this manner. Attempting to resolve such inheritance could lead to recursive
loops or other unintended behavior, making it essential for the parser to detect and handle this case
appropriately.
Expected Outcome: The parser should raise an error upon encountering this nested inheritance, clearly
indicating that this pattern is not supported. The parser's robustness should ensure that it does not attempt
to process the inheritance further, as doing so could result in a circular dependency or recursive issues.
Unlike svdconv
, which crashes with a segmentation fault (SigSegV) when encountering such a configuration, a
well-implemented parser should gracefully handle this invalid setup by issuing a clear error message,
preventing further processing of the file.
Processable with svdconv: no
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 |
|
SVD file: cluster_inheritance_via_derivedfrom/nested_cluster_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 |
|
test_override_behavior
This test case examines how derived clusters can override specific properties inherited from their base
cluster using the derivedFrom
attribute. When a derived cluster redefines certain attributes, it should
effectively replace the values that would otherwise be inherited.
Expected Outcome: The parser should correctly handle scenarios where a derived cluster overrides properties
inherited from a base cluster. For ClusterA
, all attributes should match those defined in the base
configuration, reflecting typical inheritance. However, ClusterB
, while still inheriting from a similar
base, should show overridden properties where explicitly defined. Attributes such as alternate_cluster
,
header_struct_name
, and protection
should reflect the customizations specified within ClusterB
.
Moreover, registers within ClusterB
should inherit general properties but may also have some overridden
settings, such as size
or access
. The parser must correctly interpret both inherited and redefined values,
ensuring that ClusterB
retains a consistent but modified behavior compared to ClusterA
. This behavior
mirrors what svdconv
processes, ensuring that derived configurations accurately apply the specified
overrides without causing any inconsistencies.
Processable with svdconv: yes
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
274 275 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 353 354 355 356 357 358 |
|
SVD file: cluster_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 |
|
test_register_inheritance_overlap_address
This test case evaluates how a derived cluster manages address space conflicts when it inherits registers from
a base cluster and defines additional registers that cause overlapping addresses. In the provided SVD file,
ClusterA
defines RegisterA
at address offset 0x0
with a size of 32 bits, while ClusterB
, which is
derived from ClusterA
, also defines RegisterB
at address offset 0x2
with a size of 16 bits. Because of
their sizes, RegisterB
ends up overlapping with the address space occupied by RegisterA
. Older versions of
svdconv
did not recognize this behavior and therefore, newer versions issue a warning instead of an error to
inform users of the potential address conflict. A parser that aims to maintain compatibility with older SVD
files should similarly allow registers with overlapping addresses while issuing a clear warning to alert users
of the overlap. This approach ensures that backward compatibility is maintained, but it also makes developers
aware of potential problems that could arise from such configurations.
Expected Outcome: The parser should successfully process the SVD file, but it must issue a warning indicating
that RegisterB
overlaps with RegisterA
within ClusterB
. The warning should clearly state the address
conflict and provide details about the overlapping addresses and sizes. This behavior mirrors that of
svdconv
, ensuring that the parser maintains backward compatibility while still alerting developers to
potential configuration issues that could cause unexpected behavior in hardware interaction.
Processable with svdconv: yes
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 |
|
SVD file: cluster_inheritance_via_derivedfrom/register_inheritance_overlap_address.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 |
|
test_register_inheritance_same_address
This test scenario evaluates how a derived cluster handles cases where it inherits a register from a base
cluster, and the derived cluster also defines another register at the same address offset. In the SVD file,
ClusterA
defines RegisterA
at address offset 0x0
, and ClusterB
, which is derived from ClusterA
, also
defines RegisterB
at the same address offset 0x0
. As a result, both RegisterA
(inherited from
ClusterA
) and RegisterB
(defined within ClusterB
) occupy the same address space within ClusterB
.
svdconv
processes this case without raising a hard error but issues a warning to highlight the overlap,
because of compatibility reasons. For a parser designed to work with both new
and old SVD files, it is recommended to allow registers with the same addresses but issue a warning to the
user.
Expected Outcome: The parser should process the file successfully but must issue a warning indicating that
RegisterB
is assigned the same address as RegisterA
due to inheritance. The warning should explicitly
state the address conflict, providing enough information for developers to recognize and address any
unintended overlaps in the register configurations.
Processable with svdconv: yes
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
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 |
|
SVD file: cluster_inheritance_via_derivedfrom/register_inheritance_same_address.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 |
|
test_register_inheritance_same_name
This test case addresses a situation where a derived cluster attempts to inherit a register from a base
cluster, but there is a naming conflict because the derived cluster defines a register with the same name as
the one it is inheriting. In the SVD file, ClusterA
defines a register named RegisterA
, and ClusterB
,
which is derived from ClusterA
, also defines its own RegisterA
. Since ClusterB
inherits from ClusterA
,
this results in a conflict where RegisterA
is effectively defined twice within ClusterB
. While svdconv
correctly identifies this issue and raises an error, a robust parser must also handle this case by issuing an
appropriate error message.
Expected Outcome: The parser should raise an error indicating that RegisterA
is already defined in
ClusterA
, and therefore cannot be inherited by ClusterB
because it has the same name. The error should be
explicit, preventing further processing and avoiding any ambiguity around the derived cluster's register
structure.
Processable with svdconv: no
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 |
|
SVD file: cluster_inheritance_via_derivedfrom/register_inheritance_same_name.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 |
|
test_same_address
This test case examines how the parser handles situations where two clusters, ClusterA
and ClusterB
, are
defined at the same address offset within a peripheral. In the provided SVD file, both clusters are located at
address offset 0x0
, which leads to potential address conflicts. Older versions of svdconv
did not
recognize this behavior and for compatibility, newer versions issue a warning instead of an error to inform
users of the potential address conflict. A modern parser should replicate this behavior by allowing the SVD
file to be processed but should issue a warning to alert the user of the address overlap.
Expected Outcome: The parser should successfully parse the SVD file, identifying both ClusterA
and
ClusterB
at the same address offset (0x0
). However, a warning should be issued to inform the user that
ClusterB
shares the same address as ClusterA
, indicating a potential conflict.
Processable with svdconv: yes
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 |
|
SVD file: cluster_inheritance_via_derivedfrom/same_address.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 |
|
test_simple_inheritance_backward_reference_different_scope
This test case evaluates how a parser handles cluster inheritance via the derivedFrom
attribute when the
derived cluster refers to a base cluster that is defined within a different peripheral. In this scenario,
ClusterA
from one peripheral acts as the base cluster, while a similarly named ClusterA
in another
peripheral inherits its properties. This setup is intended to confirm that cross-scope inheritance works
correctly, ensuring that the derived cluster can access and copy properties from a base cluster, even when
they reside within different scopes or peripherals.
Expected Outcome: The parser should accurately resolve the derivedFrom
reference across different scopes,
allowing ClusterA
in the second peripheral to inherit all the properties from ClusterA
in the first
peripheral. This includes settings such as size and any registers defined within the original cluster. The
implementation should validate that properties are correctly inherited and applied to the derived cluster,
ensuring consistency and accuracy. The parser's ability to handle this cross-scope inheritance efficiently is
crucial, as svdconv
processes these scenarios without issues.
Processable with svdconv: yes
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
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 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 |
|
SVD file: cluster_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 |
|
test_simple_inheritance_backward_reference_same_scope
This test case examines the functionality of cluster inheritance using the derivedFrom
attribute,
specifically when a derived cluster references a base cluster that has been defined earlier within the same
scope. The SVD file contains two clusters: ClusterA
, which serves as the base, and ClusterB
, which derives
its properties from ClusterA
. The test verifies that ClusterB
correctly inherits the settings of
ClusterA
, such as address offsets and register definitions, without requiring explicit redefinition. This
allows for efficient reuse of configurations and consistency across similar clusters.
Expected Outcome: The parser should successfully interpret the SVD file, recognizing ClusterB
as a
derivative of ClusterA
. ClusterB
should inherit all properties from ClusterA
, including the register
within it. The test should confirm that the derived cluster behaves exactly as if it were fully defined on its
own, ensuring no loss of information or incorrect settings. The implementation must accurately parse and apply
the inheritance mechanism, consistent with how svdconv
processes the file.
Processable with svdconv: yes
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
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 |
|
SVD file: cluster_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 |
|
test_simple_inheritance_forward_reference_different_scope
This test case explores how a parser manages cluster inheritance using the derivedFrom
attribute when a
derived cluster refers to a base cluster defined later within a different peripheral. Unlike backward
references, forward references imply that the parser must anticipate and correctly resolve a reference to a
cluster that has not yet been defined, adding complexity to the inheritance mechanism. This setup checks
whether the parser can seamlessly link the derived cluster to its base cluster, even when the base cluster
appears later and exists within a different peripheral scope. svdconv
cannot handle forward references
within a different scope, leading to an error, but a robust parser should be capable of managing such cases
without issues.
Expected Outcome: The parser should successfully handle the derivedFrom
reference, allowing ClusterA
in
the first peripheral to inherit from ClusterA
defined in the second peripheral. It must accurately inherit
all properties, including sizes and register definitions. The parser should ensure that cross-scope and
forward references do not disrupt the resolution of inherited properties, maintaining consistent and accurate
behavior.
Processable with svdconv: no
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
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: cluster_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 |
|
test_simple_inheritance_forward_reference_same_scope
This test case evaluates the functionality of cluster inheritance via the derivedFrom
attribute when a
derived cluster refers to a base cluster that is defined later in the same scope. Unlike backward references,
this scenario involves the base cluster being declared after the derived cluster. This setup is used to ensure
that the parser can correctly resolve forward references, allowing ClusterA
to derive from ClusterB
, even
though ClusterB
is defined later in the SVD file. svdconv
cannot handle forward references within the same
scope, leading to an error, but a robust parser should be capable of managing such cases without issues.
Expected Outcome: The parser should successfully process the SVD file, correctly handling the forward
reference so that ClusterA
inherits all properties from ClusterB
. This includes the register defined
within the base cluster. The test should confirm that ClusterA
behaves as though it were explicitly defined
with the same settings as ClusterB
, ensuring consistency and accurate inheritance. The implementation must
be able to parse these forward references efficiently, overcoming the limitations observed in svdconv
.
Processable with svdconv: no
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
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 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 |
|
SVD file: cluster_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 |
|
test_size_inheritance
This test case verifies that the size
attribute is correctly inherited when using derivedFrom
on clusters
and registers. In the provided setup, ClusterB
is derived from ClusterA
, which has a specified size
of 8
for RegisterA
. Since RegisterB
in ClusterB
does not define its own size
, it should inherit the size
attribute from RegisterA
in ClusterA
. This test confirms that the parser correctly applies this
inheritance, ensuring consistent size
values across derived elements without explicit redefinition.
Expected Outcome: The parser should successfully inherit the size
attribute for RegisterB
, resulting in
ClusterB
and its registers having the same size attributes as the elements in ClusterA
. Specifically,
RegisterB
in ClusterB
should inherit a size
of 8.
Processable with svdconv: yes
Source code in tests/test_process/test_cluster_inheritance_via_derived_from.py
819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 |
|
SVD file: cluster_inheritance_via_derivedfrom/size_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 |
|
test_value_inheritance
This test case focuses on the inheritance of properties within clusters when utilizing the derivedFrom
attribute. Specifically, it examines how a derived cluster can inherit various attributes—such as description,
alternate clusters, header structure names, access permissions, and reset configurations—from a base cluster.
The goal is to ensure that the parser accurately handles the propagation of these values, maintaining
consistency across derived clusters without requiring them to redefine attributes that are already specified
in their base counterparts.
Expected Outcome: The parser should successfully interpret the derivedFrom
attribute and apply all the
relevant properties from the base cluster to the derived cluster. For instance, ClusterB
should inherit
settings from ClusterA
, including but not limited to description, access permissions, protection level, and
reset values. The properties like alternateCluster
, headerStructName
, and size should also be correctly
propagated, ensuring ClusterB
maintains the same effective behavior as ClusterA
unless explicitly
overridden. Furthermore, nested structures within the clusters, such as registers, should also reflect
inherited attributes, demonstrating the parser’s ability to resolve and apply complex inheritance patterns.
This behavior mirrors the expected output of svdconv
, which processes these scenarios correctly, reinforcing
the parser's robustness in dealing with value inheritance via derivedFrom
.
Processable with svdconv: yes
Source code in tests/test_process/test_cluster_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 |
|
SVD file: cluster_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 |
|