Closed KurtE closed 2 years ago
I've pushed a new build that should do just this. I haven't tested it :) Here: https://koromix.dev/files/tytools/
Appears to work great!
Thanks
New TyCommander works.
@KurtE - not seeing a change in startup time? Does that help with something else? Or need a follow on change in CORES?
... just getting to forum to read more ...
Yes, suppose I have up mtp sketch and do a reset… The one I had some serial outputs:
+++ before MTP.begin() 352
Start Interval Timer
+++ before wait on !Serial 352
ERROR: intervaltimer received command with 65535 bytes
ERROR: intervaltimer received command with 65535 bytes
ERROR: intervaltimer received command with 65535 bytes
ERROR: intervaltimer received command with 65535 bytes
timer:652 CMD: 1002(OPEN_SESSION)l: 16 T:0 : 1
652 RESP:2001(RSP:OK)l: 12 T:0
timer:702 CMD: 1001(GET_DEVICE_INFO)l: 12 T:1
GetDeviceInfo size=211
702 RESP:2001(RSP:OK)l: 12 T:1
timer:752 CMD: 1014(GET_DEVICE_PROP_DESC)l: 16 T:2 : d402
752 RESP:2001(RSP:OK)l: 12 T:2
+++ after wait on !Serial 900
That last one 900 was after the while (!Serial && millis() < 5000) ;
And before it would always be > 5000
From: Defragster @.***>
@KurtE https://github.com/KurtE - not seeing a change in startup time? Does that help with something else? Or need a follow on change in CORES?
— Reply to this email directly, view it on GitHub https://github.com/Koromix/tytools/issues/86#issuecomment-1014819536 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AAL4MQC7ZJCD42FJ4CLJIPDUWRRYXANCNFSM5MFB5G6Q . You are receiving this because you were mentioned. https://github.com/notifications/beacon/AAL4MQGHJ6TZ5URNU6QSJA3UWRRYXA5CNFSM5MFB5G62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHR6OVUA.gif Message ID: @. @.> >
@Koromix @defragster -
Would be great if TyCommander would send the Magic message to SEREMU when it is logically connected up to a Teensy that is using SEREMU as the serial communications.
I don't know how to explain the best place for it, but it should be sent as soon as you are connected up to that Interface and you are ready to do communications with the endpoints.
The message that needs to be sent is almost identical to the one you send to do the reboot: (seremu_magic except that the last two bytes are different...
That is if you look at the teensy code:
Anything but the c2 6b...
Thanks Kurt