VS Code / Redundant path in `wokwi.toml`

[Semnodime]

wokwi refuses to simulate the project when one of firmware vs elf is omitted while they are identical.
I propose the option to merge them / ignore the missing one by assuming it as being redundant.

wokwi-docs/i18n/pt-BR/docusaurus-plugin-content-docs/current/vscode/project-config.md

Lines 18 to 19 in cf32894

	firmware = 'path-to-your-firmware.hex'
	elf = 'path-to-your-firmware.elf'

---

This only happens when deleting the whole line within the .toml file….

[urish]

Good suggestion! May make sense to remove elf when firmware and elf are they same.

[thubalek]

I'm totally confused with documentation. What is the meaning of those two entries? I didn't find any explanation for them. And Visual Studio extension complains that both options have to be strings.

[urish]

These entries point to the compiled firmware files. You need to compile your project into a binary firmware file, the same way you'd if you used a physical device.

[thubalek]

These entries point to the compiled firmware files. You need to compile your project into a binary firmware file, the same way you'd if you used a physical device.

I know that it is binary firmware. But I guess that firmware and elf are different forms of binary, right? Why Visual Studio core requires both? It is so confusing...

[urish]

Indeed, .elf contains some extra debugging information. The reason for requiring both is that sometimes the extra debugging information can help speed up the simulation.

However, we understand that this is confusing and plan to make the "elf" property optional.

[urish]

Released version 2.7.0 of the VS Code extension, and the elf field is now optional as suggested.