I'm trying to optimize my debugging performance and nothing I do seems to get my launch time down much under 30 seconds. That's for a repeated launch with no build and no new upload.
I'm using a P&E Cyclone ACP, which is generally faster than my LPC-Link2 and MCU-Link interfaces, but it's got a lot of hang time in there that I can't account for. Throwing more PC performance at it hasn't made it any better (this is on a Core i7-13700KF with 32 GB RAM for reference) and there's no significant load showing up on the CPU or disk during this process.
I'm particularly interested in what's happening between the time gdb says "Continuing." and when it stops at main(). I suspect that's mostly the load that happens after the breakpoint, to populate the debug views, but if I disable the "set breakpoint at main" option then I'm not able to debug at all - it won't let me pause, continue, or anything. I have to kill the debug process and then I get:
warning: Exception condition detected on fd 584
Remote communication error. Target disconnected.: Not a directory.
So that's no good. The Cyclone is connected with a 100 Mbps Ethernet connection. I feel like it ought to be possible to do this all near-instantaneously when there's no new data to be programmed, but it's spending at least 20 seconds doing I don't know what.
I know this isn't a huge deal but shaving 20 seconds off every debug run would make my day go that much smoother.
Video is attached.
Thanks,
Scott
