The GNU MCU Eclipse ARM build plug-in is highly configurable in terms of executable names and location, so you can use any 32/64-bit ARM GNU toolchain you prefer, but, for better results, the recommended toolchains for bare metal target applications are GNU MCU Eclipse ARM Embedded GCC and GNU ARM Embedded Toolchain (formerly GNU Tools for ARM Embedded Processors); for GNU/Linux target applications, the Linaro toolchains provide a large selection of choices, for various specific needs. And I wanted to use the Mac OS X toolchain that is provided with Xcode. I am running OS X (10.7.4) Xcode 4.3.2, and I checked, and I do have Command Line Tools installed. When I go to Eclipse - Preferences - New CDT Project Wizard - Toolchains: all I see is GNU Autotools Toolchain I don't see the 'Mac OS X GCC toolchain'. Toolchains for eclipse macbook pro.

Following operation checks performed with this version at Canon, we have confirmed a USB connection issue with “EOS Utility 3.11.1 for Mac OS X” and 'Picture Style File Registration Tool 1.0.0 for Mac OS X' whereby the functions enabled.

@coinsarefun said:

@Davideo said:
The latest versions of EOS Utility, EOS Utility 2, and EOS Utility 3 all report as 64 bit applications on my Mac. I did not update to Catalina, but I assume it is just a 32/64 bit compatibility issue. If you haven't updated in years, you likely just need to download an update.

Of note, it is not the camera that is 32 or 64 bit.

.
.
.
Eyemax dvr client download for mac. Yes, sorry about that. I have updated to the newest and they only recognize 64bit and
no longer 32 bit apps such as EOS 2 for my CannonT2i

Yes, I understand this. You seem to not understand my point that the latest EOS Utility 2 version does indeed show as a 64 bit application. What version of EOS Utility are you using? Please see the attached screenshot from the Applications section in the System Information and note the 64-Bit column all listed as 'Yes'.

EDIT: I re-read your initial post and it does not sound like an 32/64 bit issue. If it was, then EOS Utility would have stopped worked immediately upon updating to Catalina, not with a later point upgrade. It sounds like a different incompatibility/issue with EOS Utility. I would recommend contacting Canon. Though they are likely already aware of the issue and working on a fix.