BDD: Header1 on an Arduino Mega2560R3

Gallery
Tutorial
TRAIL: A SysMLv1.6+ model of the Arduino Mega2560Rev3 microcontroller board
Section
1: A Webel recipe for modelling microcontrollers in SysML
Topic level
INTERMEDIATE
UML keywords
custom Stereotype
icon
Stereotype:icon
SysML keywords
Block
Keywords
Slide kind
SysML Block Definition Diagram (BDD)

All pins on the 1st header of the Mega2560 only involve the ATmega2560 mcu chip (and ground GND net):

Click on the image to view it full size
MagicDraw/Cameo supports embedding images in diagrams

The mapping of the header pins to specific mcu chip pins is captured using Slots of instances of the same types as the Ports typed by the specific «pin» types we saw in the previous slide; these pin mapping values can optionally also be displayed as Context-Specific Values in Internal Block Diagrams, and can guide "wiring" connections made with Connectors in the context of the Mega2560 block.

Note how the keywords of the custom stereotypes applied to the pin types "shine through" on the instance symbols, which in this case is quite convenient because there is no way of showing this information on the lines in the ports compartment:

In MagicDraw/Cameo an assigned stereotype of a Classifier that types an instance-like element (such as a part Property) "shines through" unless it has an instance-level stereotype assigned. This is sometimes called a "secondary stereotype".

The pin ports in the header block have corresponding pin shared reference properties in the row block (and in the same order), but we won't be using the row blocks further in this trail.

Note also how the names of the pin ports "trust the type name" as far as possible and are just enough to distinguish their role.

A separate system-wide instance gnd:GND with a net value (rather than a mapping to a specific pin) is assigned as a context-specific value for a pin of type GND.

The SDA/SCL I2C pins are a special case. On the actual board digital pin 20 is marked as SDA and digital pin 21 is marked as SCL (at one end of the header). But there are is fact another pair of unmarked SDA/SCL beyond the AREF pin, and these map to the same mcu pins PD1 (for SDA) and PD0 (for SCL). In the SysML model these sets are indicated as pairs (d20_SDA_INT1_a, d21_SCL_INT0) and (d20_SDA_INT1_b, d21_SCL_INT0), and their pin mappings indicate both their SDA/SCL nets and their ultimate mcu pins PD1 and PD0.

The AREF pin is also part of a net, both the AREF header pin and the corresponding mcu pin connect to a net that passes to GND via a capacitor.

The header is modelled has having a single row. If you look closely a the board you'll see that the single "row" is in fact composed of 3 sub-rows end-to-end but with small gaps. We'll ignore that in this trail.

Up next
BDD: Header2 on an Arduino Mega2560R3
Notes
[CAPABILITY, FEATURE, TIP, TOOL] In MagicDraw/Cameo an assigned stereotype of a Classifier that types an instance-like element (such as a part Property) "shines through" unless it has an instance-level stereotype assigned. This is sometimes called a "secondary stereotype".
[NAMING, POLICY, STYLE]{STRONG} SysML: Webel: "Trust the Type!" - Often the name of the Type of an anonymous Property or instance-level element is completely sufficient to indicate its role - unless multiple Properties of the same Type have different roles within the same owner context!
[NAMING, POLICY, STYLE] "Trust the Port or Pin Type!" - Often the name of the Type of an anonymous Port or Pin is completely sufficient to indicate its role, unless a clear indication of its direction or unique role is required.
[CAPABILITY, FEATURE, TOOL]{INFORMATIVE} MagicDraw/Cameo supports embedding images in diagrams
Snippets (quotes/extracts)
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)
IBD: Header1 on an Arduino Mega2560R3 - connections