tt.shuttle.enabled shows incorrect project

[mattvenn]

after selecting a design (7 segment seconds verilog), the design starts working, but tt.shuttle.enable shows the factory test

[psychogenic]

This issue needs to go in tt-commander-app. It is rebooting or otherwise getting a fresh and independent DemoBoard. In (a single) REPL:

>>> tt.shuttle.wokwi_2bit_alu_dice.enable()
ttboard.project_mux: Enable design wokwi_2bit_alu_dice
ttboard.demoboard: Resetting system clock to default 1.25e+08Hz
ttboard.demoboard: First time loading: Toggling project reset
ttboard.demoboard: Changing reset to output mode
>>> tt.shuttle.enabled
<Design 298: wokwi_2bit_alu_dice>
>>> 

[psychogenic]

@urish how and when is this REPL activated? It should happen in a way that doesn't reset, and expose the DemoBoard singleton object it gets from DemoBoard.get() to sync up with stuff that happens in the GUI.

[urish]

It doesn't reset - all it does is sending Ctrl+B to exit the raw REPL mode:

https://github.com/TinyTapeout/tt-commander-app/blob/0a3cdd63bfacb2c8e961ed0f5097c34060c74c16/src/ttcontrol/TTBoardDevice.ts#L102

[psychogenic]

Hi,

It doesn't reset - all it does is sending Ctrl+B to exit the raw REPL mode:

Hm... ok. I used the REPL, this one time, and there was no tt object present, so I added a

tt = DemoBoard.get()

to ttcontrol.py. Maybe that was hasty and the source of the issue. Will play around with a local copy.