Bosch HDS8055U/01 resets display on Convection Bake setting, does not heat, how to diagnose the issue?

[dennismv]

Model: Bosch HDS8055U/01

Problems:

• With time set, I turn the oven knob from default position to Convection Bake => the display is reset by temporarily showing ALL LEDs turned on (see photo).  No heat is generated, previously-set time is reset, and the reset time starts flashing indicating time is not set.
• When I turn the oven knob to Bake, in just a few seconds oven indicates that it reached temperature (i.e. 350F degrees) by a beep and displaying the reached-full-heat temperature indicator with red bars lit up on the display.  The oven Does Not heat up.

I suspect that the display board (the part Bosch calls Time selector) may be at fault.
But also, could another part be at fault, for example Power Supply Unit or another part?  How would I know?  What can I do to test this out and confirm?

Is there a manual on what each of the pins are on the circuit board where power connects to it?

How can I fix this issue?

[dennismv]

Update - Bosch HDS8055U range Time Selector circuit went bad, so I got a new one and replaced it.

When I got the NEW time selector (the one you see in the video above), it appears to work great when I touch the exposed metal buttons on the circuit itself, but as soon as I install the time selector board back into its front panel enclosure (where it is supposed to go), the buttons are NOT responsive through the front panel glass.

Why? What do I need to do to get them working? Time Selector part appears to be working , so what am I missing when installing it back?  The touch screen used to work before I removed the old time selector.

Time Selector part I got was this: https://www.bosch-home.com/us/shop-productlist/12039501

[dennismv]

Update:  apparently ALL I HAD TO DO was turn power off, turn power on.
I don't know why or how, but after doing that, display started to work through the glass.

If there is an engineering-electrical reason for this, please let me know.
Otherwise, this issue has been fixed, thanks everyone for reading.