Selectable Programmer Device / Device Overview / Selectable i2c Clock

[maverick3005]

Description

I use more then 1 CH341 on my System.

Is it possible to enhance the Code/Menu to an Option, to scan for all installed compatibles devices, show
there USB-Port/BUS, where the device is actualy connected and can we make a (savable?) Option to use a specific
Programmer - this is useful when more as one Instance is started - One for Reading and One For Writing, but use
2 Programmers at the same time .

The 2nd thing is, that the driver from the ch341 can support 4 different Speeds. It would be nice, when
we can switch the clock at runtime via a "device-menu" - with the Option to save the last used Setting.
Some devices like it very fast - and many older SFP like it very slow. A manual option can be helpful here.

Usage tips

• Please use the 👍 reaction to show that you are interested into this.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this.
• Subscribe to receive notifications on status change and new comments, you can do also without add comment.

[bigbigmdm]

Hello, @maverick3005 !
For the first question, I will think about it.
But for the second question, I can solve it very quickly. I have already built it in the IMSProg project.

Is that what you meant?

[bigbigmdm]

Today, I am only using the minimum CH341A bus speed of 100KHZ.

[maverick3005]

Yes, Absolutely. Make the 4 possible Speeds available, please :-)

The Option with more then one device is really useful, because i often have 2 Instances active - and they use booth the same device.

[bigbigmdm]

Hello, @maverick3005 !
I added the combobox of I2c bus speed to the main form. But I was not satisfied with the result. When changing the speed, the module dump was corrupted.

SFP-Master_bus_speed.zip

Please test this update.

[maverick3005]

That´s strange. As i know, there is a module re-init nesassary. When the driver for the ch341 is loaded there are options to set
the speed with the module loading. This works in my shell scripts basicly with rmmod / insmod.

Problems with Timing usualy comes from not existing or bad pull-ups. In my case i have a prototype board where i can go down to 2,2 Kohm at the pullups when i use higher speeds, like 400KHz. On the other side, the TX_ENABLE pin can often be a problem, when Laser is still on and consumes to much Power. And one more: When there is no 3,3 Volt Hardware MOD on the "Black" Programmer.
It all depends on the used SFP Module.

I will test your code over the weekend, thx for the affort.