USB232 E-Block issue - programmer problem when USB connected
Posted: Sun Oct 11, 2009 6:37 pm
Hi All,
There is an issue with the programmer EB006 Rev7 when used in conjunction with the USB232 eblock - Flowcode cannot obtain the CHIP ID when the USB232 eblock is powered from USB. Removing the USB cable from the USB232 eblock resolves the issue but the root cause is unknown so far - it is definately electrical though (not a SW issue).
If I were to guess what the problem is I would say that one or both of the outputs from the USB232 eblock are idling high causing the PIC inserted into the EB006 to be back powered via its internal protection diodes on the USART lines. This could cause some issues since the PIC will still be powered even if the EB006 power supply and USB cable are both pulled (this does assume that the USB232 eblock is connected and ITS USB cable connected to a PC).
I guess I will need to get my scope out to find out whats up for sure but if you guys at Matrix MM know of a fix please let us know.
Many thanks.
There is an issue with the programmer EB006 Rev7 when used in conjunction with the USB232 eblock - Flowcode cannot obtain the CHIP ID when the USB232 eblock is powered from USB. Removing the USB cable from the USB232 eblock resolves the issue but the root cause is unknown so far - it is definately electrical though (not a SW issue).
If I were to guess what the problem is I would say that one or both of the outputs from the USB232 eblock are idling high causing the PIC inserted into the EB006 to be back powered via its internal protection diodes on the USART lines. This could cause some issues since the PIC will still be powered even if the EB006 power supply and USB cable are both pulled (this does assume that the USB232 eblock is connected and ITS USB cable connected to a PC).
I guess I will need to get my scope out to find out whats up for sure but if you guys at Matrix MM know of a fix please let us know.
Many thanks.