On two of our board designs using the MSP430F1611, I get a "Can't identify
target device, no error" message when trying to connect the to the TI USB FET
(VCP COM30) using Crossworks - but it connects and programs OK using the
Elprotronic Lite FET-Pro430 programming software and at least one version of the
IAR package (used by another software engineer).
Is there is an interface parameter (timing or voltage???) that can be modified
to get the TI FET to work with Crossworks. I am using the exact same HIL.DLL and
MSP430.DLL files in both software packages.
I can use the exact same computer and softare packages to connect to a third
1611 design using both Crossworks and the FET-Pro430 and it works
perfectly...
FET430UIF Crossworks connection problems
Started by ●April 9, 2012
Reply by ●April 9, 20122012-04-09
Heh I got something similar this morning.
Are you sure Crossworks is looking for the particular model chip you are using? I know in IAR under Project>Options you have to set the specific chip # you are using or it won't recognize the target device(your chip). Sorry if this is no help...I don't have much experience in Crossworks but I imagine it's similar.
From: m... [mailto:m...] On Behalf Of s...@att.net
Sent: Monday, April 09, 2012 1:48 PM
To: m...
Subject: [msp430] FET430UIF Crossworks connection problems
On two of our board designs using the MSP430F1611, I get a "Can't identify target device, no error" message when trying to connect the to the TI USB FET (VCP COM30) using Crossworks - but it connects and programs OK using the Elprotronic Lite FET-Pro430 programming software and at least one version of the IAR package (used by another software engineer).
Is there is an interface parameter (timing or voltage???) that can be modified to get the TI FET to work with Crossworks. I am using the exact same HIL.DLL and MSP430.DLL files in both software packages.
I can use the exact same computer and softare packages to connect to a third 1611 design using both Crossworks and the FET-Pro430 and it works perfectly...
This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
Are you sure Crossworks is looking for the particular model chip you are using? I know in IAR under Project>Options you have to set the specific chip # you are using or it won't recognize the target device(your chip). Sorry if this is no help...I don't have much experience in Crossworks but I imagine it's similar.
From: m... [mailto:m...] On Behalf Of s...@att.net
Sent: Monday, April 09, 2012 1:48 PM
To: m...
Subject: [msp430] FET430UIF Crossworks connection problems
On two of our board designs using the MSP430F1611, I get a "Can't identify target device, no error" message when trying to connect the to the TI USB FET (VCP COM30) using Crossworks - but it connects and programs OK using the Elprotronic Lite FET-Pro430 programming software and at least one version of the IAR package (used by another software engineer).
Is there is an interface parameter (timing or voltage???) that can be modified to get the TI FET to work with Crossworks. I am using the exact same HIL.DLL and MSP430.DLL files in both software packages.
I can use the exact same computer and softare packages to connect to a third 1611 design using both Crossworks and the FET-Pro430 and it works perfectly...
This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
Reply by ●April 9, 20122012-04-09
As I said, all three designs use the same processor (1611), 2 don't connect
and the 3rd does. The processor is correctly defined in all three project
files.
Steve
----- Original Message -----
From: Brock
To: 'm...'
Sent: Monday, April 09, 2012 11:50
Subject: RE: [msp430] FET430UIF Crossworks connection problems
Heh I got something similar this morning.
Are you sure Crossworks is looking for the particular model chip you are using? I know in IAR under Project>Options you have to set the specific chip # you are using or it won't recognize the target device(your chip). Sorry if this is no help...I don't have much experience in Crossworks but I imagine it's similar.
From: m... [mailto:m...] On Behalf Of s...@att.net
Sent: Monday, April 09, 2012 1:48 PM
To: m...
Subject: [msp430] FET430UIF Crossworks connection problems
On two of our board designs using the MSP430F1611, I get a "Can't identify target device, no error" message when trying to connect the to the TI USB FET (VCP COM30) using Crossworks - but it connects and programs OK using the Elprotronic Lite FET-Pro430 programming software and at least one version of the IAR package (used by another software engineer).
Is there is an interface parameter (timing or voltage???) that can be modified to get the TI FET to work with Crossworks. I am using the exact same HIL.DLL and MSP430.DLL files in both software packages.
I can use the exact same computer and softare packages to connect to a third 1611 design using both Crossworks and the FET-Pro430 and it works perfectly...
This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
Steve
----- Original Message -----
From: Brock
To: 'm...'
Sent: Monday, April 09, 2012 11:50
Subject: RE: [msp430] FET430UIF Crossworks connection problems
Heh I got something similar this morning.
Are you sure Crossworks is looking for the particular model chip you are using? I know in IAR under Project>Options you have to set the specific chip # you are using or it won't recognize the target device(your chip). Sorry if this is no help...I don't have much experience in Crossworks but I imagine it's similar.
From: m... [mailto:m...] On Behalf Of s...@att.net
Sent: Monday, April 09, 2012 1:48 PM
To: m...
Subject: [msp430] FET430UIF Crossworks connection problems
On two of our board designs using the MSP430F1611, I get a "Can't identify target device, no error" message when trying to connect the to the TI USB FET (VCP COM30) using Crossworks - but it connects and programs OK using the Elprotronic Lite FET-Pro430 programming software and at least one version of the IAR package (used by another software engineer).
Is there is an interface parameter (timing or voltage???) that can be modified to get the TI FET to work with Crossworks. I am using the exact same HIL.DLL and MSP430.DLL files in both software packages.
I can use the exact same computer and softare packages to connect to a third 1611 design using both Crossworks and the FET-Pro430 and it works perfectly...
This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
