TychoVrahe

Implemented fix in 9490acf814c0d030da4d15a79613b82b90aad9c3 .

and added a mask to account for reserved bits in the register https://github.com/trezor/trezor-firmware/commit/f4e56df5d69465522c7b135b1457b311221a036e

yeah i noticed, working on a fix

pushed: https://github.com/trezor/trezor-firmware/pull/2444/commits/7cc20b08fe28c3967204b49b70c55bd2846b636e fixed heap end setting fixed T1 core build - stack is also moved to the beginning @hiviah please recheck this, with regard to how the last 8 bytes...

I get the warning even when USB is properly connected, until suite/trezorctl tries to interact with the device. Therefore i consider the warning misleading. Also when drawing/removing the header warning,...

Turns out that the device enters 'configured' state, but after few seconds it enters 'suspended' state, if there is no communication - as per 9.1.1.6 of the referred document. So...

On my PC, i found that the device enters suspended mode after 2s, which is if configured in this file: `/sys/bus/usb/devices/3-4.1/power/autosuspend_delay_ms` with value 2000. The 3-4.1 is some device id...

Given that: - standard says that our devices need to support suspension (and we probably don't have a reliable way to disable it for our device on all hosts anyway)...

i actually had something ready to mitigate this, made a PR: https://github.com/trezor/trezor-firmware/pull/2523

pushed some fixes requested in review and also: fixed a off by one bug in a8634321339c29bdf3221cc46e7ff16f4ce3a428 removed confusing comment: 33c770c2048082dec46aab8ee2d41296a5440267 removed unnecessary casting: 60127ff66a5973465d727917a942fd51c83cc590