EmbSIM (EmbLinkOs) errors

4 recurring problems engineers report in EmbSIM (EmbLinkOs), ranked by impact.

#124 by errors trackedPLMVerificationFirmware

Recurring EmbSIM (EmbLinkOs) errors, by impact

  1. 1A saved library version label let changes to Lua models, register data and symbols pass unnoticed, so the same label hid different parts underneath.PLM · Agent failure · 1 report74
  2. 2Explicit part and library version requests previously did not constrain what ran, so the loader could simulate against revisions other than the one selected.PLM · Agent failure · 1 report74
  3. 3Engineering output used to count only root symbols and could not show inherited model configurations, so an LM358P's two op-amps were miscounted against its one package.Verification · Agent failure · 1 report66
  4. 4Real firmware projects build with CMake or make, so the simulator points at their build output, and 'it's easy to simulate a stale ELF after editing the code.' The ask is a pre-run build hook or at least a warning when the image is older than its sources, found on an STM32 FreeRTOS access-control board.Firmware · Agent failure · 1 report66

How it fails

  1. Agent failure4

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.