Windows: cannot start vcd peripheral

[alexian79]

I have an issue with starting and configuring vcd hw.

1. then set hw vcd[0] start command issued I am getting output.vcd: Invalid argument error all the time.
2. possible bug: then bits added to vcd, they are reported as full registers/ports in vcd info.
   set hw vcd[0] add SDAT
   set hw vcd[0] add CLK
   0> info var SDAT
   SDAT sfr[0x90].7 = 1,128U,128
   0> info var CLK
   CLK sfr[0xb0].7 = 1,128U,128
3. possible version bug, even though I am running version 0.9.6 it is reporting as 0.9.5

Thank you.

[alexian79]

UPDATE. I have built from source in WSL Ubuntu 18.04.06 and it creates vcd file from the same command line

but it still reports added signals as bytes

version is reported correctly.

[danieldrotos]

It is intentional, variable is always reported as bus with same width as the size of the memory cell. You can expand buses in vcd viewers and check bits of them.

You can report location of bit address space, it will be reported as logical variable instead of bus. For example, instead of P1.7, add bits 0x97 to vcd.

Note, that banging of port bits during uart simulation is not implented. Uart is simulated by reading/writing a file, and TXD/RXD port bits are not changed in the simulator.

[alexian79]

Thanks a lot for explanations. I was able to add my signals as bits to vcd,
but if firmware is touching Ports as bits and as sfr do I need to use external code/logic to join those signals? for example P3.7 and bit 0xB7?