[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #61626] jtagmkii_pdi improvements for jtag2updi use
From: |
Joerg Wunsch |
Subject: |
[bug #61626] jtagmkii_pdi improvements for jtag2updi use |
Date: |
Mon, 6 Dec 2021 17:16:42 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; FreeBSD amd64; rv:93.0) Gecko/20100101 Firefox/93.0 |
Follow-up Comment #5, bug #61626 (project avrdude):
[comment #4 comment #4:]
> Would be great if the essence could be scissored out and added to the docs.
A link to the repo is probably also a good idea.
>
Please do ;-)
I welcome diffs, also for documentation updates.
> Ah, the PDIUSBD12 chip!
Right.
> So if I understand you correctly, pulling DTR/RTS low before "hello" and
releasing after "goodbye" shouldn't cause any harm/compatibility issues with
existing hardware. Excellent!
>
Seems so.
> But there is nothing in the protocol that limits the speed to a maximum baud
rate of 115200? Heck, could we theoretically use 230400, 250000, 460800 or
500000, 921600 or even 1M if Avrdude supported it (in function
jtagmkII_get_baud())?
>
I'm not so sure why these baudrate checks are even necessary in that code.
Maybe we could as well leave it up to the underlying OS (and driver) whether
it can accept a certain baudrate.
But that needs to be verified/tested.
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/bugs/?61626>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/