Skip to content

Development build

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 13 Oct 10:56

Development build of main, commit a454eeb (2026-11-22 17:20:47 +0000): not a release, for testing.
The latest release is under Releases; this one is replaced after every change that passes the tests.
In the browser: https://pmnmalo.github.io/Silinx/dev/

Not released yet

In short:

  • Phones: the Board Emulator fits the board to the phone's width, its switches and buttons repeated under it,
    large enough for a finger.
  • Phones: simulate and read the waves on a phone: Simulate's panel and the waves each take the whole screen,
    switched by the bar of panes; a finger places the cursor, two fingers scroll the time, a pinch zooms it.
  • Phones: documents open read only on a phone, with "Read-only on a phone" at the end of their toolbar: read,
    zoom, try them out and simulate there; edit on a tablet or a computer.
  • The simulation's lines in Portuguese: the Test Bench Wizard's line, Set as Top Module's, and the simulator's own
    (the wave configuration saved and loaded, a force removed, a run interrupted or stopped, Step, the stimuli's
    checks, the VCD export) in the interface's language, in the simulator's console and in the Console.
  • The HDL editor's indentation: Enter in a VHDL file indents by VHDL's blocks (one level after is, begin,
    then, else, loop, generate, a when; a port continued under the first port), and end, begin, elsif,
    else, when typed at the start of a line go back to their block's indentation, as Verilog's end, endmodule,
    endcase do; Enter after a keyword typed whole (is, then, begin) makes the new line even with the completion
    list open on it.
  • Phones: the main toolbar keeps Open Project, Undo, Redo and Find, the other tools in its More tools (⋯) menu;
    menus take the whole width and dialogs the whole screen.
  • Phones: under 600 px wide Silinx shows one pane at a time, the whole screen: the side panel, the document or the
    console, switched by a bar of three buttons at the bottom (Panels, Document, Console).
  • Co-design: an Arduino's firmware can be an .elf (avr-gcc's) in the page's Try it too, not only a .hex.
  • Co-design: the System editor's Try it (it was Simulate) opens the green Try it panel of the other drawing editors.
  • The Petri net's and the circuit's Check in Portuguese: their errors and warnings (a deadlock, a transition that
    never fires, a short circuit, a floating input, an IC not powered…) in the console and in its Errors and Warnings
    tabs in the interface's language, as the state diagram's.
  • ASM chart: a double click on a box selects its text in Properties to be typed over, instead of adding a new
    state where it was.
  • State diagram and ASM chart: one Undo step per action: two drags, two adds or two connects soon after each
    other are undone one at a time; only what is typed in one field is one step.
  • A truth table's input or output renamed in its Inputs or Outputs box keeps its column (an output) or its rows (an
    input), instead of a new one of 0s.
  • The Petri net, circuit and state diagram editors' messages in Portuguese: an arc that cannot be, a value
    refused, a wire drawn straight, Try it's short circuit: said in the console in the interface's language.
  • A breadboard turned or dragged onto the leads of the parts beside it, or a part dropped on another's leads, is
    refused, with a message in the console that names the parts in the way, instead of joining them in a short circuit.
  • Schematic: a gate's inputs changed in Properties (AND4 to AND2), Rotate and Mirror keep the symbol's wires on its
    pins; a net name on a moved symbol's pin goes with it; a wire's segment dragged onto another net's wire is moved clear
    of it; a change in Properties right after a wire was drawn is no longer lost.
  • Co-design projects: New Project ▸ Co-design makes a project of FPGA and microcontroller nodes linked in a
    System, empty or from the new example uart-avr (an Arduino Uno and the uart example's FPGA linked by UART), drawn in
    the System editor and simulated together (Simulate: the link inspector's bytes, a terminal, the waves).

In detail:

  • The UI test of View ▸ Interface's ISE style leaves out the phone's More tools button (#5244): it counts the main
    toolbar's buttons not shown in the ISE style (none: every tool kept), and since the phones' toolbar (#5121) that count
    took in its More tools button, shown under 600 px only, so the test failed on main in both interfaces.
  • The Board Emulator on a phone, the fifth phase of #5121 (#5238): under 600 px the board is fitted to the width
    (boardZoom of web/js/tasks-emu.js, a phone's floor 0.3 instead of a tablet's 0.7), with no sideways scroll, and
    its switches and buttons are repeated under it, 44 px at least, in the board's order, each with its name and the
    design's bit it drives (web/js/emulator-touch.js): a tap toggles the board's switch, a finger held on a button
    holds the board's button down until it is lifted, the strip following the board. The phone's pane follows what is
    opened on every screen, so a window turned into a phone's shows what the user was at (web/js/phone.js). UI tests at
    375 × 812 and 430 × 932 with touch, both interfaces, Portuguese (test/ui/phone-emu.test.js); boardZoom's phone
    cases (test/tasks.test.js).
  • Simulating on a phone, the fourth phase of #5121 (#5233): under 600 px Simulate's side panel is the Panels pane,
    the whole width (what to simulate, then SSim's Instances and Objects), and the waves the Document pane, the whole
    width (web/css/phone.css); in the ISE style interface SSim's window keeps its Instances and Objects, above its
    waves. The waves' names and values columns are narrower there (100 and 56 px, a wave configuration's widths win,
    web/js/isim.js). A task with no document yet (Simulate, Emulate) opens on its side panel (web/js/phone.js). UI
    tests at 375 × 812 and 430 × 932 with touch, both interfaces, the waves' cursor, scroll and pinch by touch
    (test/ui/phone-sim.test.js).
  • A phone's editors, the third phase of #5121 (#5229): under 600 px every editor opens read only, as a followed
    project's (web/js/phone-readonly.js): the HDL, C and constraints text, the schematic, the state diagram, the ASM
    chart, the Petri net, the truth table, the circuit, the System, the Symbol Editor. The read-only notice "Read-only on
    a phone" sits at the right end of the toolbar, its tip saying where to edit; the editing tools are hidden, the view
    and Try it kept. A followed project's, a generated file's or a newer Silinx's notice comes first. Opened again on a
    wider screen, the document edits. UI tests at 375 × 812 and 430 × 932 with touch on the lock example, in both
    interfaces and in Portuguese (test/ui/phone-readonly.test.js).
  • A read-only ASM chart or circuit (a followed project's, a C function's state machine, a phone's) no longer shows its
    editing tools: its toolbar's groups and buttons kept their display over the hidden they were given (#5228).
  • The simulation's application lines translated (#5223): SSim's console (web/js/isim-console.js) takes an
    application's line (logLine(text, kind, { app: true }): isim-wcfg.js, isim-run.js, isim-forces.js,
    isim-stimuli.js, isim-api.js, isim-toolbar.js) and draws it through t(), its tag kept, again when the
    language changes; its message keeps its English, and the Console's copy of it (web/js/messages.js) is drawn the
    same way. The Test Bench Wizard's line and Set as Top Module's are application lines of the Console (appLog). Their
    Portuguese in web/js/i18n-sim.js. The simulator's output (the design's reports, the commands' answers, its banner)
    stays as it is; the MCP server's messages stay in English.
  • VHDL's indentation (#5218): the editor's VHDL mode (CodeMirror's legacy one) indented as C does: a line after a
    declaration at column 0, after end if; deeper, end never brought back. core/vhdl/indent.js gives a line the
    indentation of its block (a scan of the lines before it as they are indented: entity, architecture, package,
    function, process, block, component, if, case and its whens, loops, generates, records), a statement continued one
    level deeper, an open ( under its first item (one level deeper when the ( ends its line, its ) back under it),
    end back to its block's opening, begin to its block's, elsif / else to their if's, when one level under
    its case; the editor's indentation service, and its words typed again at the start of a line (indentOnInput). It
    gives the examples' own indentation, but the continued statements aligned by hand. Test: vhdl-indent, the
    usability scenario of the indentation left as the editor gives it.
  • Verilog's closing words brought back (#5219): the HDL editor had no indentOnInput(), so the Verilog mode's
    electric words (end, endmodule, endcase…) stayed where Enter put them; the VHDL and Verilog editors have it,
    Verilog's on its closing words typed at the start of a line only (the legacy mode's also on a bracket typed anywhere
    in a line, which indented again a line the person had indented).
    Test: the usability scenario of Verilog's end and endmodule.
  • Enter after a word typed whole (#5220): the completion list open on a word already typed whole (the only or
    first word it offers, is, then, begin) took the Enter, and no new line was made; Enter then closes the list
    and makes the line (a completion that adds something is still taken). Test: the usability scenario of Enter after a
    keyword, and the others' Enter no longer closing the list with Esc first.
  • The System Emulator's core (core/system-emu.js): a co-design System's boards emulated through the scheduler, each FPGA
    node's board the Board Emulator's (its switches and buttons the inputs no link drives, its LEDs and display its
    outputs watched, shown as the Board Emulator shows them), an Arduino's pins and its LED L; the scheduler's watch of
    outputs no link reads; the System's worker's init { emulate }, set and the boards' state in each state (#5212).
  • A phone's header, the second phase of #5121 (#5210): under 600 px the main toolbar keeps Open Project, Undo, Redo
    and Find in Project and gathers the others, in their order and enabled as their buttons, in the menu of a More tools
    button (⋯) at its end (web/js/phone-toolbar.js), the ISE style's processes' buttons too; the ISE style's menu bar
    fits the width, in Portuguese too. A menu is the whole width, its items 40 px tall, no taller than the screen below
    where it opened; a dialog is the whole screen, a wizard's steps a line above its page (web/css/phone.css). At
    600 px and more nothing changes. UI tests at 375 × 812 and 430 × 932 with touch, in both interfaces and in
    Portuguese (test/ui/phone-toolbar.test.js).
  • A phone's layout, the first phase of #5121 (#5207): under 600 px (PHONE_QUERY of web/js/narrow.js) one pane at a
    time, the whole width and height (web/js/phone.js, web/css/phone.css): the side panel, the document in front or
    the console, switched by the bar of panes above the Silinx interface's task tabs. A project opened or closed shows the
    side panel, a document opened shows it, a task chosen (Simulate, Emulate, Implement) its document; a new error or
    warning marks the Console button until the console is shown. The narrow screen's drawer, the splitters and the
    Layout buttons give way to it; at 600 px and more nothing changes. Both interfaces, in Portuguese; UI tests at
    375 × 812 and 430 × 932 with touch (test/ui/phone.test.js).
  • Usability tests: the HDL editor and the simulation (#5206, its first phase): test/usability/hdl-edit.test.js: a
    4-bit counter typed from an empty file in VHDL and in Verilog, character by character (the brackets and quotes the
    editor closes, completions taken from its list, the indentation it gives corrected with Backspace and Tab), the text
    after every line the typing's model's (lib/hdl-typing.js); a ; left out on purpose, Check Syntax's lines exactly,
    its error's row clicked to its line, fixed, Check Syntax clean; Undo to the empty file and Redo to the end; the file
    saved as typed. hdl-sim.test.js: the Test Bench Wizard on that counter (random vectors, the expected values from the
    design), the bench passing; its waves zoomed, the cursor clicked, a marker, a signal of the counter added, a radix, the
    wave configuration saved, the simulation run again and the configuration loaded, the values at the cursor after every
    step the reference simulator's on the same files (lib/wave-kit.js). In both interfaces and in Portuguese; the bugs
    they found are todos: #5218, #5219, #5220, #5221, #5222, #5223.
  • Co-design is off in a release until it is stable: one switch (core/build-channel.js CODESIGN_IN_RELEASE), the
    build's channel told apart as the single-file edition does (server/build-commit.js: a commit tagged v, or no
    git, is a release), the local server and the MCP server too, and the server's page told by /build-channel.js. In a
    release New Project's Co-design card is disabled with its reason, the uart-avr example is not offered, the Design
    pane shows no System row, a .sys.json opened says so in the console, and the MCP server refuses new_project kind
    codesign, edit_system, check_system and simulate of a System with the same message; the development build, a
    checkout's server and the tests keep it. docs/CODESIGN.md says how to turn it on (#5202).
  • MCP: set_output_logic's schema of the kinds checked (#5201): its inputs and outputs (#5165) said
    minItems: 1, a keyword the MCP's schemas do not use (test/mcp-args.test.js failed on main); an empty list is
    refused by the tool itself, as the editor's boxes refuse it ("1 to 16 inputs", "At least 1 output"), nothing written.
  • docs/CODESIGN.md: the System and the circuit are one model in two views (the System the model, at the protocol level;
    the circuit the pin level, with the boards as its parts and a circuit as a System's node; a wiring view in the System
    editor), and the System's actions for every node at once and for each node alone (Check, Try it, Emulate,
    Implement, Program), in its phases and its decisions (#5200).
  • The page reads a project file's bytes (the local server's GET /projects/:p/file?bytes=1, server/projects.js
    readFileBytes, by a file's text's checks and messages; the browser edition's workspace folder: its file's bytes;
    the browser's own storage, which keeps text only, refuses it with a message that says so), and the System's Try it
    reads an .elf firmware so, as the MCP server's simulate of a System now does through the same readFileBytes
    (#5198).
  • The System editor's toolbar button is Try it, its bottom panel the green Try it panel titled "Try it", its body
    the lighter green, as the state diagram's, the ASM chart's and the Petri net's; docs/UI-GUIDELINES.md's Try it rule
    names every drawing editor's Try it (not Simulate, the project's test bench's) and its two looks, a bar or a bottom
    panel; the user's guide says Try it. The console's messages and the MCP tool keep Simulate System (simulate) (#5194).
  • The Petri net's and the circuit's Check messages translated (#5185): editorProblems (web/js/editor-problems.js)
    takes inLanguage: its Errors and Warnings tabs' messages and Check's console lines through t(), the tabs again
    when the language changes (the state diagram's, which did it in drawings.js, the Petri net's and the circuit's);
    the Portuguese of every message of core/circuit-check.js and its KiCad parts' (checkModels), and of
    core/petri.js validatePetri and core/petri-analysis.js checkPetri (web/js/i18n-circuit.js,
    web/js/i18n-petri.js). The MCP server's check_drawing says them in English, as before. A condition's own parse
    error stays in English (#5196).
  • The System document's edits (core/system-edit.js) check a node's id and an interface's name with the shared
    identifier rule (core/ident.js's isName) rather than a copy of their own; the same names are taken and refused
    (#5184).
  • UI test: "#4017 the browser edition: no Open in VS Code" no longer flaky (#5171): a new project's Design pane rows
    are drawn while the side panel still shows the Start page, and the Design page comes in front a moment later (10 to
    70 ms); the test right-clicked a row that existed but was not shown yet. Its row menu now waits for the row shown,
    and a regression step hides the pane for a moment before opening the menu.
  • CI: the Firefox / WebKit UI tests in a job per browser (#5170): both browsers in one job took 28 minutes, and
    40 on a slow runner (every test 1.44 times slower, none hanging), past the tests' step limit, failing the release
    silinx-fpga-v0.6.2. The browsers job is now a matrix, browsers (firefox) and browsers (webkit), each installing
    and caching its own browser, its tests' step limited to 30 minutes (15 normally) and the job to 60.
  • ASM chart editor: a double click on a box focuses its field (#5168): the svg captures the pointer, so the
    dblclick's target was the svg and a state was added; the box of the last press is used.
  • State diagram and ASM chart editors: separate edits no longer merged into one Undo step (#5167): a commit's
    merge key names the field being typed in and its object (cond:t3, sname:s2, the boxes nudged); a drag, an add, a
    connect, a delete, a paste, a choice in a list commit with no key, each its own step.
  • Truth table: a name changed in the Inputs or Outputs box is a rename (#5165): the boxes matched the columns by
    name, so a name changed there was one dropped and one added: a renamed output became 64 zeros (the lock's
    digit_ok), and a renamed input made every row where it is 1 a copy of its row at 0 (traffic's lamps). When the
    list has as many names as before and only one of them is different and new to it, that name is renamed: its column,
    expression, HDL logic and minimal solution (an output), or its rows and its name in the expressions (an input), are
    kept. Two names changed at once, a name added, removed or moved still follow their names. The MCP server's
    set_output_logic sets a table's inputs and outputs too (inputs, outputs), through the same function, with the
    editor's checks and messages.
  • The drawing editors' messages translated (#5164): the Petri net's, the circuit's and the state diagram's
    onMessage (web/js/drawings.js) log their text through t(), as the ASM chart's, the truth table's and the
    schematic's did (the state diagram's "(not applied)" too); the Portuguese of the circuit's messages that had none
    (Try it's short circuit, oscillation and "cannot be simulated", a wire drawn straight, a clock's frequency, a wire
    that joins one place) and of a PNML file refused.
  • Circuit: a part moved or turned onto other parts' leads refused (#5162): a breadboard turned (R) with its parts
    on it could put its holes under the leads of the parts beside it (the button's, the clock's, the switch's), joining
    them to its strips with no word (Check then said a short circuit). A move or a turn (core/circuit-edit.js, the
    editor's and the MCP server's edit_circuit's) is now refused when a lead it moves, or a breadboard's hole, would
    land on the lead of a part it does not carry: "BB1 cannot be turned: it would land on the leads of B1, joining
    them". A part dragged there stays at the last place it could, the message said on release; translated in
    Portuguese.
  • Schematic: a symbol's type changed in Properties keeps its wires (#5153): a gate's inputs (OR4 to OR2), its
    inverted inputs, a multiplexer's select bits and a flip-flop's inputs set the symbol's type and left the wires where
    its old pins were. They now re-pin it as a COMP's comparisons do (#1555, repinSymbol): the wires on the pins that stay
    follow them, those of the pins that go are dropped, in one Undo step.
  • Schematic: a net name on a moved symbol's pin moves with it (#5154): a gate whose output's wire carries its
    net's name at the pin (the gates example's or_sum, prime_sop) moved left the name behind, off every wire: the net
    lost its name and its connection by name. With Keep connections, the name now moves with the pin, on the wire's end.
  • Schematic: a segment dragged onto another net's wire is nudged clear of it (#5155): as a wire drawn there (#948),
    the wire is routed between its ends along the path dragged, leaving it only where it must; not when that would change
    the connections.
  • Schematic: Rotate and Mirror keep the wires on the symbol's pins (#5156): with Keep connections, the wires, I/O
    markers and net names on the pins of a symbol turned or flipped follow them (followPins, which now also follows a
    pin that moves both ways), routed around what they then run over.
  • Schematic: a Properties change after a wire was drawn is kept (#5159): drawing a wire replaced the document but
    left the Properties panel editing the selected symbol's old copy; the panel is now drawn again for the document's own.
  • Usability tests: the schematic's place step in Portuguese (#5187): the point clicked is measured once the symbol
    is chosen (its toolbar options move the sheet).
  • UI test of Convert to Schematic: a module that does not elaborate is refused in a console ERROR line, not a dialog
    (#4747), in English and Portuguese; the test waited for the dialog (#5149).
  • Usability tests: the breadboard (#5148, its third part): test/usability/circuit-build.test.js: an IC placed from
    the parts panel on the breadboard example, powered with two wires to the rails, linked to another IC's output (Check's
    warnings exactly); the breadboard dragged with all on it (the wires follow, the nets kept); a short circuit and a
    floating input made on purpose, said, undone; and circuit-random.test.js: random sequences of ICs placed, powered,
    linked, moved along the row and deleted, wires deleted, Undo and Redo, with a fixed seed. After every step the
    circuit's invariants (its check's errors, the wires still attached, the new wires' loose ends) and its HDL in VHDL and
    Verilog; Undo back to the start and Redo. The bug they found is an issue of its own: #5162 (a breadboard turned lands
    its holes under the leads of the parts beside it), its scenario marked to do.
  • Usability tests: the state diagram, the ASM chart, the truth table and the Petri net (#5148, its fourth part):
    test/usability/fsm.test.js (the traffic example's state diagram: a state added, named and wired with transitions
    drawn from its rim, states dragged with their transitions, a state renamed in place, a phase and a condition set in
    Properties, a transition and a state deleted), asm.test.js (the lock example's timer: a state, a decision and a
    conditional output added on free exits and connected, boxes dragged and nudged, names, conditions and outputs typed,
    a box and an arrow deleted and drawn again), truthtable.test.js (a new table, the traffic lamps and the lock's
    digit_ok: inputs and outputs added, cells clicked to 0, 1 and X, an expression, the Karnaugh map, a NAND form, an input
    removed) and petri.test.js (the lock's alarm net: a place and a transition added and linked, a guard and tokens,
    nodes dragged, a transition and an arc deleted, an arc's weight, an inhibitor arc, an arc refused). After every step
    the drawing's Check has no error and its HDL compiles and elaborates in VHDL and Verilog; Check's warnings exactly;
    Undo back to the start and Redo. The bugs they found are issues of their own: #5164, #5165, #5167, #5168 (their
    scenarios marked to do).
  • Usability tests: the flow, the Board Emulator and the wizards (#5148, its fifth part): test/usability/flow.test.js:
    the gates example implemented with the Silinx toolchain (no warnings), its schematic edited (a net renamed: the
    processes out of date) and implemented again; the Board Emulator on it, each of the switches' 16 numbers set and the
    LEDs read against the prime detector it is. wizards.test.js: a source of each kind made with its New Source wizard
    (module, schematic, state diagram, ASM chart, Boolean algebra, Petri net, digital circuit): in the project, its HDL
    compiled with no warnings, its drawing's check exactly. In both interfaces and in Portuguese.
  • Usability tests: the schematic's other edits (#5148, its second part): test/usability/schematic-edit.test.js:
    a net name and I/O markers added with their tools (their names typed in the box they ask with), two wired symbols
    copied and pasted (the copy wired the same), a wire and a wired symbol deleted (Check Schematic's warnings exactly:
    the net name left, the net with no driver), Rearrange Wires and Rearrange Schematic on the gates example (the nets
    kept, no clash), and a half adder drawn from the palette on an empty sheet; each with Undo back to the start and Redo.
    The random sequences name new wires' nets and delete new wires too.
  • Usability tests, every week (#5148, its first part): test/usability/ exercises Silinx as people use it, in long
    sessions of steps through the interface, each step checked: the drawing's invariants (no wire end left on nothing, no
    wire over a pin or through a body, no overlapping symbols, the junction dots), the wires that were attached still
    attached, the nets, the HDL made in VHDL and Verilog and elaborated, Check Schematic's warnings exactly, and Undo back
    to the start and Redo to the end. This part covers the schematic's wires on the gates example: wires drawn pin to pin
    and onto a wire (a T-junction), segments and symbols dragged with their wires, a symbol's width and a gate's inputs
    changed; and random sequences of those steps with a fixed seed (the week's seed too), a failing one shrunk to the
    steps that reproduce it. A new workflow, .github/workflows/usability.yml, runs them every Sunday and by hand on any
    branch (never on pull requests), in both interfaces and in Portuguese, in parts under 15 minutes
    (scripts/test-shard.mjs --usability); a scheduled run's failure opens an issue that quotes the scenario's report
    (its seed, its steps, what broke, the command that replays it: scripts/report-failure.mjs), its screenshots kept as
    the job's artifact. The bugs they found are issues of their own: #5153, #5154, #5155, #5156, #5159 (their scenarios
    marked to do until they are fixed).
  • The Tasks side panel's UI test waits for the project to be restored (#5147): after its reload,
    test/ui/tasks-side-resize.test.js clicked Simulate as soon as Implement was in front, while the project's documents
    and its task were still being restored; the restored task then took Implement back (the Design Summary in front), and
    the test timed out waiting for Simulate (the release CI of v15.30.0; every time with SILINX_UI_THROTTLE=6). It now
    waits until the project is open and restored.
  • The private-data check's history: the message of ece9afc, #5009's fix, names the two made-up home folders it allowed
    in their tests; their entries cover that message too (the release CI of v15.30.0 failed on it, #5142).
  • CI: test/s6-pad-paths.test.js among the heaviest unit tests (HEAVY), run on Linux only: nextpnr on the XC6SLX45 took
    its tests past their 600 s on a Windows runner (the release CI of v15.30.0, #5140).
  • Co-design's scheduler (core/system-sim.js) starts every link active for its hold, so that a run's first windows are
    fine ones: an AVR's D1, floating until its USART is on, no longer reaches the FPGA's receiver as a 100 µs start
    bit with the adaptive quantum, and the first byte is no longer lost (HiIjJk as with a fixed latency) (#5130).
  • Co-design projects made by New Project (#4702): its Co-design card is enabled: a co-design project has no board
    of its own (its settings page says why), its System document <name>.sys.json is made with it and opened; its Start
    from is Empty or a co-design example, the FPGA kind's has none (core/project-kind.js createRefusal, boardRefusal: the
    server's and the browser edition's stores, one rule). Design Properties of a co-design project says what stands for
    its board. The MCP server's new_project makes one (kind codesign: its System, no board). The example uart-avr: the
    uart example's FPGA module (the same sources), an Arduino Uno's firmware (firmware/hello.asm and its .hex: it sends
    "Hello from Arduino!", the FPGA echoes it) and their System. The user's guide has a page on co-design, in English and
    in Portuguese.
  • Co-design: Simulate System (#4701): the System editor's Simulate opens its simulation view under the canvas: Run,
    Pause, Run 100 ms and Restart run the whole System together, in a Web Worker (the FPGA nodes' modules compiled by
    Yosys for the compiled engine at their board's clock, the Arduino's firmware, a .hex, run by avr8js, a serial terminal
    for each terminal node, its line typed sent with Enter); the link inspector shows each wire's decoded bytes (a UART's
    at its baud and frame) with their times, Waves the whole System's waves in the waveform viewer (a scope a node, and the
    links). The nodes' and the decoders' warnings are in the console. The MCP server's simulate runs a System (top: its
    .sys.json, a co-design project's by default) for a time and gives each wire's bytes, the terminals' text and the warnings, its waves written to build/<name>.vcd
    (core/system-build.js, core/system-run.js, core/system-host.js, core/system-sim-terminal.js). avr8js is served to the
    page and the worker, and bundled in the browser edition.
  • Co-design: the System editor (#4700): a co-design project's System document (.sys.json) opens in an editor of
    its own, in the schematic editor's style: an FPGA node (a module of the project on a board), an Arduino Uno or Nano and
    a serial terminal placed on its canvas; a UART or GPIO interface added to an FPGA node, its ports and their pins of the
    board, a microcontroller's board and firmware set in its properties; the interfaces linked with the Link tool (a link
    joins two interfaces of one kind, each joining one link: an edit refused says why in the console). Its check's errors
    and warnings are in the console as it is edited (a 5 V output on a 3.3 V FPGA input, a node that joins nothing), and
    Check's lines in the Console, as when it is saved. The Design pane shows the System's row, <name> [System], in place
    of the device, with its FPGA nodes' modules under it. The MCP server's edit_system edits the System as the editor
    does (core/system-edit.js), then checks it; check_system describes it before its check. Co-design projects themselves come
    with the uart-avr example (#4702).
  • Co-design's link decoders and the system's waves (#4699, roadmap #4695): core/system-decode.js decodes a link's
    traffic from the pins the co-simulation scheduler exchanges: a UART's bytes at its baud and frame (data bits 5 to 8,
    parity N, E or O, stop bits 1 or 2), each at its start bit's time, with a framing error and a parity error as
    warnings (a wrong baud gives garbage, as on a real board). core/system-waves.js makes one set of waves for the whole
    system, a scope per node with its linked pins and a scope links with each link's named signal (uart_avr_tx), in
    the simulator's shape (the waveform viewer's) and as a VCD (the simulator's toVCD). core/vcd.js reads a VCD back
    (its scopes, signals and changes). The System's simulation view (#4701) and the MCP's simulate_system (#4702) show
    them.