I am trying to develop a system on MSP430 launchpad. It should do ADC from F2013
and then transfer data through USB from the Launchpad to PC.
With that's in mind, I reprogrammed the MSP430F1612 in the emulator side
(by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it
works like a bridge.
However, I am now have a problem with the TUSB. I tried to download the driver
(TUSBWINVCP) but it could not recognized the USB. So I tried another method that
using EEPROM burner. Here are the steps I did:
1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step
similar to isolating step in the EEPROM burner user guide - just disconnect
their SCL pins).
2. Install the EEPROM burner.
3. After the EEPROM burner finished, I connected the Launchpad to the PC.
However, my PC still does not recognize the USB... I even tried to Update Driver
through the Device manager but it still doesnt work. I am using Windows 7.
Should it be a problem? Any suggestions or recommendations?
Best Regards,
Launchpad USB
Started by ●July 21, 2010
Reply by ●July 21, 20102010-07-21
I do not have a LaunchPad.
I think the emulator side of the LaunchPad already has a user UART to PC VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is implemented in the TUSB chip, not in the F1612 chip. It should work for you without any change.
If you do want to change the firmware in the TUSB chip, be aware that there is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in reset. It waits for its own 12MHz crystal to start and stabilize. It then suppless that clock to the TUSB chip and releases the reset. Without this, the TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
-- OCY
--- In m..., "Hoai Anh" wrote:
>
> I am trying to develop a system on MSP430 launchpad. It should do ADC from F2013 and then transfer data through USB from the Launchpad to PC.
>
> With that's in mind, I reprogrammed the MSP430F1612 in the emulator side (by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it works like a bridge.
>
> However, I am now have a problem with the TUSB. I tried to download the driver (TUSBWINVCP) but it could not recognized the USB. So I tried another method that using EEPROM burner. Here are the steps I did:
>
> 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step similar to isolating step in the EEPROM burner user guide - just disconnect their SCL pins).
> 2. Install the EEPROM burner.
> 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
>
> However, my PC still does not recognize the USB... I even tried to Update Driver through the Device manager but it still doesnt work. I am using Windows 7. Should it be a problem? Any suggestions or recommendations?
>
> Best Regards,
>
I think the emulator side of the LaunchPad already has a user UART to PC VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is implemented in the TUSB chip, not in the F1612 chip. It should work for you without any change.
If you do want to change the firmware in the TUSB chip, be aware that there is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in reset. It waits for its own 12MHz crystal to start and stabilize. It then suppless that clock to the TUSB chip and releases the reset. Without this, the TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
-- OCY
--- In m..., "Hoai Anh" wrote:
>
> I am trying to develop a system on MSP430 launchpad. It should do ADC from F2013 and then transfer data through USB from the Launchpad to PC.
>
> With that's in mind, I reprogrammed the MSP430F1612 in the emulator side (by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it works like a bridge.
>
> However, I am now have a problem with the TUSB. I tried to download the driver (TUSBWINVCP) but it could not recognized the USB. So I tried another method that using EEPROM burner. Here are the steps I did:
>
> 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step similar to isolating step in the EEPROM burner user guide - just disconnect their SCL pins).
> 2. Install the EEPROM burner.
> 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
>
> However, my PC still does not recognize the USB... I even tried to Update Driver through the Device manager but it still doesnt work. I am using Windows 7. Should it be a problem? Any suggestions or recommendations?
>
> Best Regards,
>
Reply by ●July 21, 20102010-07-21
Interesting, I did not know that TUSB has to use F1612 clock... I reprogrammed
F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB
individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1
respectively), right?
Can it be used without EEPROM? I read the user guide on VCP firmware, it said it can load firmware from the host (my PC) to the USB. So what is the point of using EEPROM while you can ignore it to reduce cost? There are reasons that are stated in the user guide but I am not clear:
"Storing firmware in EEPROM in TUSB3410 applications has the advantage of automatically using the 3410's unique device ID as the USB serial number. If storing on the host, the only way to achieve a
unique serial number is to serialize the EEPROM."
As the USB serial number - what does it mean? and if storing on the host, what does it mean by serializing the EEPROM? Does it not need to use EEPROM in the "storing in the host" case?
Regards,
--- In m..., "old_cow_yellow" wrote:
>
> I do not have a LaunchPad.
>
> I think the emulator side of the LaunchPad already has a user UART to PC VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is implemented in the TUSB chip, not in the F1612 chip. It should work for you without any change.
>
> If you do want to change the firmware in the TUSB chip, be aware that there is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in reset. It waits for its own 12MHz crystal to start and stabilize. It then suppless that clock to the TUSB chip and releases the reset. Without this, the TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
>
> -- OCY
>
> --- In m..., "Hoai Anh" wrote:
> >
> > I am trying to develop a system on MSP430 launchpad. It should do ADC from F2013 and then transfer data through USB from the Launchpad to PC.
> >
> > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side (by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it works like a bridge.
> >
> > However, I am now have a problem with the TUSB. I tried to download the driver (TUSBWINVCP) but it could not recognized the USB. So I tried another method that using EEPROM burner. Here are the steps I did:
> >
> > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step similar to isolating step in the EEPROM burner user guide - just disconnect their SCL pins).
> > 2. Install the EEPROM burner.
> > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> >
> > However, my PC still does not recognize the USB... I even tried to Update Driver through the Device manager but it still doesnt work. I am using Windows 7. Should it be a problem? Any suggestions or recommendations?
> >
> > Best Regards,
>
Can it be used without EEPROM? I read the user guide on VCP firmware, it said it can load firmware from the host (my PC) to the USB. So what is the point of using EEPROM while you can ignore it to reduce cost? There are reasons that are stated in the user guide but I am not clear:
"Storing firmware in EEPROM in TUSB3410 applications has the advantage of automatically using the 3410's unique device ID as the USB serial number. If storing on the host, the only way to achieve a
unique serial number is to serialize the EEPROM."
As the USB serial number - what does it mean? and if storing on the host, what does it mean by serializing the EEPROM? Does it not need to use EEPROM in the "storing in the host" case?
Regards,
--- In m..., "old_cow_yellow" wrote:
>
> I do not have a LaunchPad.
>
> I think the emulator side of the LaunchPad already has a user UART to PC VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is implemented in the TUSB chip, not in the F1612 chip. It should work for you without any change.
>
> If you do want to change the firmware in the TUSB chip, be aware that there is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in reset. It waits for its own 12MHz crystal to start and stabilize. It then suppless that clock to the TUSB chip and releases the reset. Without this, the TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
>
> -- OCY
>
> --- In m..., "Hoai Anh" wrote:
> >
> > I am trying to develop a system on MSP430 launchpad. It should do ADC from F2013 and then transfer data through USB from the Launchpad to PC.
> >
> > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side (by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it works like a bridge.
> >
> > However, I am now have a problem with the TUSB. I tried to download the driver (TUSBWINVCP) but it could not recognized the USB. So I tried another method that using EEPROM burner. Here are the steps I did:
> >
> > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step similar to isolating step in the EEPROM burner user guide - just disconnect their SCL pins).
> > 2. Install the EEPROM burner.
> > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> >
> > However, my PC still does not recognize the USB... I even tried to Update Driver through the Device manager but it still doesnt work. I am using Windows 7. Should it be a problem? Any suggestions or recommendations?
> >
> > Best Regards,
>
Reply by ●July 21, 20102010-07-21
--- In m..., "Hoai Anh" wrote:
>
> Interesting, I did not know that TUSB has to use F1612 clock... I reprogrammed F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1 respectively), right?
P27 of TUSB is connected to R19, R22, and P49 of F1612.
You probably need to remove R19, R22, and disconnect it from P49 of F1612 before you add a 12MHz crystal.
You probably also need to add load capacitors.
P9 of TUSB is connected to some RC and P42 of F1612.
You probably need to keep the RC but disconnect from P42 of F1612.
>
> Can it be used without EEPROM? I read the user guide on VCP firmware, it said it can load firmware from the host (my PC) to the USB. So what is the point of using EEPROM while you can ignore it to reduce cost? There are reasons that are stated in the user guide but I am not clear:
> "Storing firmware in EEPROM in TUSB3410 applications has the advantage of automatically using the 3410's unique device ID as the USB serial number. If storing on the host, the only way to achieve a
> unique serial number is to serialize the EEPROM."
>
> As the USB serial number - what does it mean? and if storing on the host, what does it mean by serializing the EEPROM? Does it not need to use EEPROM in the "storing in the host" case?
Yes, you can store the firmware for the TUSB inside the PC and do not provide an EEPROM. But I do not think it is practical to make a product that way -- unless you are the only one that does it that way and you only produce one product.
The USB serial number is an additional information for the HOST to recognize each individual device amongst all the devices with the same Vendor ID and same Device ID.
>
> Regards,
> --- In m..., "old_cow_yellow" wrote:
> >
> > I do not have a LaunchPad.
> >
> > I think the emulator side of the LaunchPad already has a user UART to PC VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is implemented in the TUSB chip, not in the F1612 chip. It should work for you without any change.
> >
> > If you do want to change the firmware in the TUSB chip, be aware that there is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in reset. It waits for its own 12MHz crystal to start and stabilize. It then suppless that clock to the TUSB chip and releases the reset. Without this, the TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> >
> > -- OCY
> >
> > --- In m..., "Hoai Anh" wrote:
> > >
> > > I am trying to develop a system on MSP430 launchpad. It should do ADC from F2013 and then transfer data through USB from the Launchpad to PC.
> > >
> > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side (by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it works like a bridge.
> > >
> > > However, I am now have a problem with the TUSB. I tried to download the driver (TUSBWINVCP) but it could not recognized the USB. So I tried another method that using EEPROM burner. Here are the steps I did:
> > >
> > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step similar to isolating step in the EEPROM burner user guide - just disconnect their SCL pins).
> > > 2. Install the EEPROM burner.
> > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> > >
> > > However, my PC still does not recognize the USB... I even tried to Update Driver through the Device manager but it still doesnt work. I am using Windows 7. Should it be a problem? Any suggestions or recommendations?
> > >
> > > Best Regards,
> > >
>
>
> Interesting, I did not know that TUSB has to use F1612 clock... I reprogrammed F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1 respectively), right?
P27 of TUSB is connected to R19, R22, and P49 of F1612.
You probably need to remove R19, R22, and disconnect it from P49 of F1612 before you add a 12MHz crystal.
You probably also need to add load capacitors.
P9 of TUSB is connected to some RC and P42 of F1612.
You probably need to keep the RC but disconnect from P42 of F1612.
>
> Can it be used without EEPROM? I read the user guide on VCP firmware, it said it can load firmware from the host (my PC) to the USB. So what is the point of using EEPROM while you can ignore it to reduce cost? There are reasons that are stated in the user guide but I am not clear:
> "Storing firmware in EEPROM in TUSB3410 applications has the advantage of automatically using the 3410's unique device ID as the USB serial number. If storing on the host, the only way to achieve a
> unique serial number is to serialize the EEPROM."
>
> As the USB serial number - what does it mean? and if storing on the host, what does it mean by serializing the EEPROM? Does it not need to use EEPROM in the "storing in the host" case?
Yes, you can store the firmware for the TUSB inside the PC and do not provide an EEPROM. But I do not think it is practical to make a product that way -- unless you are the only one that does it that way and you only produce one product.
The USB serial number is an additional information for the HOST to recognize each individual device amongst all the devices with the same Vendor ID and same Device ID.
>
> Regards,
> --- In m..., "old_cow_yellow" wrote:
> >
> > I do not have a LaunchPad.
> >
> > I think the emulator side of the LaunchPad already has a user UART to PC VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is implemented in the TUSB chip, not in the F1612 chip. It should work for you without any change.
> >
> > If you do want to change the firmware in the TUSB chip, be aware that there is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in reset. It waits for its own 12MHz crystal to start and stabilize. It then suppless that clock to the TUSB chip and releases the reset. Without this, the TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> >
> > -- OCY
> >
> > --- In m..., "Hoai Anh" wrote:
> > >
> > > I am trying to develop a system on MSP430 launchpad. It should do ADC from F2013 and then transfer data through USB from the Launchpad to PC.
> > >
> > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side (by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it works like a bridge.
> > >
> > > However, I am now have a problem with the TUSB. I tried to download the driver (TUSBWINVCP) but it could not recognized the USB. So I tried another method that using EEPROM burner. Here are the steps I did:
> > >
> > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step similar to isolating step in the EEPROM burner user guide - just disconnect their SCL pins).
> > > 2. Install the EEPROM burner.
> > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> > >
> > > However, my PC still does not recognize the USB... I even tried to Update Driver through the Device manager but it still doesnt work. I am using Windows 7. Should it be a problem? Any suggestions or recommendations?
> > >
> > > Best Regards,
> > >
>
Reply by ●July 21, 20102010-07-21
I got it... I reprogrammed the F1612 to set it provide the TUSB with 12Mhz speed
from SMCLK, but it seems does not work. The PC still could not see the USB. How
can I reprogram the F1612 from the factory default? Is there any where I can
download the code for emulator part for F1612 launchpad?
Regards,
________________________________
From: old_cow_yellow
To: m...
Sent: Wed, July 21, 2010 6:04:49 PM
Subject: [msp430] Re: Launchpad USB
--- In m..., "Hoai Anh" wrote:
>
> Interesting, I did not know that TUSB has to use F1612 clock... I reprogrammed
>F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB
>individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1
>respectively), right?
P27 of TUSB is connected to R19, R22, and P49 of F1612.
You probably need to remove R19, R22, and disconnect it from P49 of F1612 before
you add a 12MHz crystal.
You probably also need to add load capacitors.
P9 of TUSB is connected to some RC and P42 of F1612.
You probably need to keep the RC but disconnect from P42 of F1612.
>
> Can it be used without EEPROM? I read the user guide on VCP firmware, it said
>it can load firmware from the host (my PC) to the USB. So what is the point of
>using EEPROM while you can ignore it to reduce cost? There are reasons that are
>stated in the user guide but I am not clear:
> "Storing firmware in EEPROM in TUSB3410 applications has the advantage of
>automatically using the 3410's unique device ID as the USB serial number. If
>storing on the host, the only way to achieve a
> unique serial number is to serialize the EEPROM."
>
> As the USB serial number - what does it mean? and if storing on the host, what
>does it mean by serializing the EEPROM? Does it not need to use EEPROM in the
>"storing in the host" case?
Yes, you can store the firmware for the TUSB inside the PC and do not provide an
EEPROM. But I do not think it is practical to make a product that way -- unless
you are the only one that does it that way and you only produce one product.
The USB serial number is an additional information for the HOST to recognize
each individual device amongst all the devices with the same Vendor ID and same
Device ID.
>
> Regards,
> --- In m..., "old_cow_yellow" wrote:
> >
> > I do not have a LaunchPad.
> >
> > I think the emulator side of the LaunchPad already has a user UART to PC
>VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is
>implemented in the TUSB chip, not in the F1612 chip. It should work for you
>without any change.
> >
> > If you do want to change the firmware in the TUSB chip, be aware that there
>is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in
>reset. It waits for its own 12MHz crystal to start and stabilize. It then
>suppless that clock to the TUSB chip and releases the reset. Without this, the
>TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> >
> > -- OCY
> >
> > --- In m..., "Hoai Anh" wrote:
> > >
> > > I am trying to develop a system on MSP430 launchpad. It should do ADC from
>F2013 and then transfer data through USB from the Launchpad to PC.
> > >
> > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side
>(by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it
>works like a bridge.
> > >
> > > However, I am now have a problem with the TUSB. I tried to download the
>driver (TUSBWINVCP) but it could not recognized the USB. So I tried another
>method that using EEPROM burner. Here are the steps I did:
> > >
> > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step
>similar to isolating step in the EEPROM burner user guide - just disconnect
>their SCL pins).
> > > 2. Install the EEPROM burner.
> > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> > >
> > > However, my PC still does not recognize the USB... I even tried to Update
>Driver through the Device manager but it still doesnt work. I am using Windows
>7. Should it be a problem? Any suggestions or recommendations?
> > >
> > > Best Regards,
> > >
>
from SMCLK, but it seems does not work. The PC still could not see the USB. How
can I reprogram the F1612 from the factory default? Is there any where I can
download the code for emulator part for F1612 launchpad?
Regards,
________________________________
From: old_cow_yellow
To: m...
Sent: Wed, July 21, 2010 6:04:49 PM
Subject: [msp430] Re: Launchpad USB
--- In m..., "Hoai Anh" wrote:
>
> Interesting, I did not know that TUSB has to use F1612 clock... I reprogrammed
>F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB
>individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1
>respectively), right?
P27 of TUSB is connected to R19, R22, and P49 of F1612.
You probably need to remove R19, R22, and disconnect it from P49 of F1612 before
you add a 12MHz crystal.
You probably also need to add load capacitors.
P9 of TUSB is connected to some RC and P42 of F1612.
You probably need to keep the RC but disconnect from P42 of F1612.
>
> Can it be used without EEPROM? I read the user guide on VCP firmware, it said
>it can load firmware from the host (my PC) to the USB. So what is the point of
>using EEPROM while you can ignore it to reduce cost? There are reasons that are
>stated in the user guide but I am not clear:
> "Storing firmware in EEPROM in TUSB3410 applications has the advantage of
>automatically using the 3410's unique device ID as the USB serial number. If
>storing on the host, the only way to achieve a
> unique serial number is to serialize the EEPROM."
>
> As the USB serial number - what does it mean? and if storing on the host, what
>does it mean by serializing the EEPROM? Does it not need to use EEPROM in the
>"storing in the host" case?
Yes, you can store the firmware for the TUSB inside the PC and do not provide an
EEPROM. But I do not think it is practical to make a product that way -- unless
you are the only one that does it that way and you only produce one product.
The USB serial number is an additional information for the HOST to recognize
each individual device amongst all the devices with the same Vendor ID and same
Device ID.
>
> Regards,
> --- In m..., "old_cow_yellow" wrote:
> >
> > I do not have a LaunchPad.
> >
> > I think the emulator side of the LaunchPad already has a user UART to PC
>VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is
>implemented in the TUSB chip, not in the F1612 chip. It should work for you
>without any change.
> >
> > If you do want to change the firmware in the TUSB chip, be aware that there
>is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in
>reset. It waits for its own 12MHz crystal to start and stabilize. It then
>suppless that clock to the TUSB chip and releases the reset. Without this, the
>TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> >
> > -- OCY
> >
> > --- In m..., "Hoai Anh" wrote:
> > >
> > > I am trying to develop a system on MSP430 launchpad. It should do ADC from
>F2013 and then transfer data through USB from the Launchpad to PC.
> > >
> > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side
>(by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it
>works like a bridge.
> > >
> > > However, I am now have a problem with the TUSB. I tried to download the
>driver (TUSBWINVCP) but it could not recognized the USB. So I tried another
>method that using EEPROM burner. Here are the steps I did:
> > >
> > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step
>similar to isolating step in the EEPROM burner user guide - just disconnect
>their SCL pins).
> > > 2. Install the EEPROM burner.
> > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> > >
> > > However, my PC still does not recognize the USB... I even tried to Update
>Driver through the Device manager but it still doesnt work. I am using Windows
>7. Should it be a problem? Any suggestions or recommendations?
> > >
> > > Best Regards,
> > >
>
Reply by ●July 21, 20102010-07-21
On Wed, Jul 21, 2010 at 7:31 PM, Hoai Anh wrote:
> I got it... I reprogrammed the F1612 to set it provide the TUSB with 12Mhz speed
> from SMCLK, but it seems does not work. The PC still could not see the USB. How
> can I reprogram the F1612 from the factory default? Is there any where I can
> download the code for emulator part for F1612 launchpad?
>
> Regards,
>
You can replace that turkey of a USB->serial chip with an FTDI cable
or a CP210x device. I have done this and it works fine under Linux at
least.
Regards,
Mark
markrages@gmail
--
Mark Rages, Engineer
Midwest Telecine LLC
m...@midwesttelecine.com
> I got it... I reprogrammed the F1612 to set it provide the TUSB with 12Mhz speed
> from SMCLK, but it seems does not work. The PC still could not see the USB. How
> can I reprogram the F1612 from the factory default? Is there any where I can
> download the code for emulator part for F1612 launchpad?
>
> Regards,
>
You can replace that turkey of a USB->serial chip with an FTDI cable
or a CP210x device. I have done this and it works fine under Linux at
least.
Regards,
Mark
markrages@gmail
--
Mark Rages, Engineer
Midwest Telecine LLC
m...@midwesttelecine.com
Reply by ●July 22, 20102010-07-22
Did you not save the original flash image before you re-programmed it?
Gerlich, Sebastian may be able to help you.
I am still waiting for my LaunchPad. Once I get it, that is the second thing I do. (The first thing is to see if it works at all.)
-- OCY
--- In m..., Hoai Anh wrote:
>
> I got it... I reprogrammed the F1612 to set it provide the TUSB with 12Mhz speed
> from SMCLK, but it seems does not work. The PC still could not see the USB. How
> can I reprogram the F1612 from the factory default? Is there any where I can
> download the code for emulator part for F1612 launchpad?
>
> Regards,
>
> ________________________________
> From: old_cow_yellow
> To: m...
> Sent: Wed, July 21, 2010 6:04:49 PM
> Subject: [msp430] Re: Launchpad USB
>
>
> --- In m..., "Hoai Anh" wrote:
> >
> > Interesting, I did not know that TUSB has to use F1612 clock... I reprogrammed
> >F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB
> >individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1
> >respectively), right?
>
> P27 of TUSB is connected to R19, R22, and P49 of F1612.
> You probably need to remove R19, R22, and disconnect it from P49 of F1612 before
> you add a 12MHz crystal.
> You probably also need to add load capacitors.
>
> P9 of TUSB is connected to some RC and P42 of F1612.
> You probably need to keep the RC but disconnect from P42 of F1612.
>
> >
> > Can it be used without EEPROM? I read the user guide on VCP firmware, it said
> >it can load firmware from the host (my PC) to the USB. So what is the point of
> >using EEPROM while you can ignore it to reduce cost? There are reasons that are
> >stated in the user guide but I am not clear:
> > "Storing firmware in EEPROM in TUSB3410 applications has the advantage of
> >automatically using the 3410's unique device ID as the USB serial number. If
> >storing on the host, the only way to achieve a
> > unique serial number is to serialize the EEPROM."
> >
> > As the USB serial number - what does it mean? and if storing on the host, what
> >does it mean by serializing the EEPROM? Does it not need to use EEPROM in the
> >"storing in the host" case?
>
> Yes, you can store the firmware for the TUSB inside the PC and do not provide an
> EEPROM. But I do not think it is practical to make a product that way -- unless
> you are the only one that does it that way and you only produce one product.
>
> The USB serial number is an additional information for the HOST to recognize
> each individual device amongst all the devices with the same Vendor ID and same
> Device ID.
>
> >
> > Regards,
> >
> >
> > --- In m..., "old_cow_yellow" wrote:
> > >
> > > I do not have a LaunchPad.
> > >
> > > I think the emulator side of the LaunchPad already has a user UART to PC
> >VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is
> >implemented in the TUSB chip, not in the F1612 chip. It should work for you
> >without any change.
> > >
> > > If you do want to change the firmware in the TUSB chip, be aware that there
> >is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in
> >reset. It waits for its own 12MHz crystal to start and stabilize. It then
> >suppless that clock to the TUSB chip and releases the reset. Without this, the
> >TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> > >
> > > -- OCY
> > >
> > > --- In m..., "Hoai Anh" wrote:
> > > >
> > > > I am trying to develop a system on MSP430 launchpad. It should do ADC from
> >F2013 and then transfer data through USB from the Launchpad to PC.
> > > >
> > > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side
> >(by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it
> >works like a bridge.
> > > >
> > > > However, I am now have a problem with the TUSB. I tried to download the
> >driver (TUSBWINVCP) but it could not recognized the USB. So I tried another
> >method that using EEPROM burner. Here are the steps I did:
> > > >
> > > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step
> >similar to isolating step in the EEPROM burner user guide - just disconnect
> >their SCL pins).
> > > > 2. Install the EEPROM burner.
> > > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> > > >
> > > > However, my PC still does not recognize the USB... I even tried to Update
> >Driver through the Device manager but it still doesnt work. I am using Windows
> >7. Should it be a problem? Any suggestions or recommendations?
> > > >
> > > > Best Regards,
> > > >
> > >
> >
>
>
>
>
>
Gerlich, Sebastian may be able to help you.
I am still waiting for my LaunchPad. Once I get it, that is the second thing I do. (The first thing is to see if it works at all.)
-- OCY
--- In m..., Hoai Anh wrote:
>
> I got it... I reprogrammed the F1612 to set it provide the TUSB with 12Mhz speed
> from SMCLK, but it seems does not work. The PC still could not see the USB. How
> can I reprogram the F1612 from the factory default? Is there any where I can
> download the code for emulator part for F1612 launchpad?
>
> Regards,
>
> ________________________________
> From: old_cow_yellow
> To: m...
> Sent: Wed, July 21, 2010 6:04:49 PM
> Subject: [msp430] Re: Launchpad USB
>
>
> --- In m..., "Hoai Anh" wrote:
> >
> > Interesting, I did not know that TUSB has to use F1612 clock... I reprogrammed
> >F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB
> >individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1
> >respectively), right?
>
> P27 of TUSB is connected to R19, R22, and P49 of F1612.
> You probably need to remove R19, R22, and disconnect it from P49 of F1612 before
> you add a 12MHz crystal.
> You probably also need to add load capacitors.
>
> P9 of TUSB is connected to some RC and P42 of F1612.
> You probably need to keep the RC but disconnect from P42 of F1612.
>
> >
> > Can it be used without EEPROM? I read the user guide on VCP firmware, it said
> >it can load firmware from the host (my PC) to the USB. So what is the point of
> >using EEPROM while you can ignore it to reduce cost? There are reasons that are
> >stated in the user guide but I am not clear:
> > "Storing firmware in EEPROM in TUSB3410 applications has the advantage of
> >automatically using the 3410's unique device ID as the USB serial number. If
> >storing on the host, the only way to achieve a
> > unique serial number is to serialize the EEPROM."
> >
> > As the USB serial number - what does it mean? and if storing on the host, what
> >does it mean by serializing the EEPROM? Does it not need to use EEPROM in the
> >"storing in the host" case?
>
> Yes, you can store the firmware for the TUSB inside the PC and do not provide an
> EEPROM. But I do not think it is practical to make a product that way -- unless
> you are the only one that does it that way and you only produce one product.
>
> The USB serial number is an additional information for the HOST to recognize
> each individual device amongst all the devices with the same Vendor ID and same
> Device ID.
>
> >
> > Regards,
> >
> >
> > --- In m..., "old_cow_yellow" wrote:
> > >
> > > I do not have a LaunchPad.
> > >
> > > I think the emulator side of the LaunchPad already has a user UART to PC
> >VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is
> >implemented in the TUSB chip, not in the F1612 chip. It should work for you
> >without any change.
> > >
> > > If you do want to change the firmware in the TUSB chip, be aware that there
> >is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in
> >reset. It waits for its own 12MHz crystal to start and stabilize. It then
> >suppless that clock to the TUSB chip and releases the reset. Without this, the
> >TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> > >
> > > -- OCY
> > >
> > > --- In m..., "Hoai Anh" wrote:
> > > >
> > > > I am trying to develop a system on MSP430 launchpad. It should do ADC from
> >F2013 and then transfer data through USB from the Launchpad to PC.
> > > >
> > > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side
> >(by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it
> >works like a bridge.
> > > >
> > > > However, I am now have a problem with the TUSB. I tried to download the
> >driver (TUSBWINVCP) but it could not recognized the USB. So I tried another
> >method that using EEPROM burner. Here are the steps I did:
> > > >
> > > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step
> >similar to isolating step in the EEPROM burner user guide - just disconnect
> >their SCL pins).
> > > > 2. Install the EEPROM burner.
> > > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> > > >
> > > > However, my PC still does not recognize the USB... I even tried to Update
> >Driver through the Device manager but it still doesnt work. I am using Windows
> >7. Should it be a problem? Any suggestions or recommendations?
> > > >
> > > > Best Regards,
> > > >
> > >
> >
>
>
>
>
>
Reply by ●July 22, 20102010-07-22
Hi OCY,
Unfortunately, I dont know how to save the original flash image... Can you show
me how to do that? I am using IAR. That is going to be a very good experience
for me... Is there any way that I contact Gerlich and Sebastian so I can ask for
the image. First thing first, please tell me how to save the original flash
image. Very eager to know how. I dont know how to read the pre-program firmware
in MCU!!!
Thank you very much for your help
________________________________
From: old_cow_yellow
To: m...
Sent: Wed, July 21, 2010 9:57:07 PM
Subject: [msp430] Re: Launchpad USB
Did you not save the original flash image before you re-programmed it?
Gerlich, Sebastian may be able to help you.
I am still waiting for my LaunchPad. Once I get it, that is the second thing I
do. (The first thing is to see if it works at all.)
-- OCY
--- In m..., Hoai Anh wrote:
>
> I got it... I reprogrammed the F1612 to set it provide the TUSB with 12Mhz
>speed
>
> from SMCLK, but it seems does not work. The PC still could not see the USB. How
>
> can I reprogram the F1612 from the factory default? Is there any where I can
> download the code for emulator part for F1612 launchpad?
>
> Regards,
>
> ________________________________
> From: old_cow_yellow
> To: m...
> Sent: Wed, July 21, 2010 6:04:49 PM
> Subject: [msp430] Re: Launchpad USB
> --- In m..., "Hoai Anh" wrote:
> >
> > Interesting, I did not know that TUSB has to use F1612 clock... I
>reprogrammed
>
> >F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB
> >individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1
> >respectively), right?
>
> P27 of TUSB is connected to R19, R22, and P49 of F1612.
> You probably need to remove R19, R22, and disconnect it from P49 of F1612
>before
>
> you add a 12MHz crystal.
> You probably also need to add load capacitors.
>
> P9 of TUSB is connected to some RC and P42 of F1612.
> You probably need to keep the RC but disconnect from P42 of F1612.
>
> >
> > Can it be used without EEPROM? I read the user guide on VCP firmware, it said
>
> >it can load firmware from the host (my PC) to the USB. So what is the point of
>
> >using EEPROM while you can ignore it to reduce cost? There are reasons that
>are
>
> >stated in the user guide but I am not clear:
> > "Storing firmware in EEPROM in TUSB3410 applications has the advantage of
> >automatically using the 3410's unique device ID as the USB serial number. If
> >storing on the host, the only way to achieve a
> > unique serial number is to serialize the EEPROM."
> >
> > As the USB serial number - what does it mean? and if storing on the host,
>what
>
> >does it mean by serializing the EEPROM? Does it not need to use EEPROM in the
> >"storing in the host" case?
>
> Yes, you can store the firmware for the TUSB inside the PC and do not provide
>an
>
> EEPROM. But I do not think it is practical to make a product that way -- unless
>
> you are the only one that does it that way and you only produce one product.
>
> The USB serial number is an additional information for the HOST to recognize
> each individual device amongst all the devices with the same Vendor ID and same
>
> Device ID.
>
> >
> > Regards,
> >
> >
> > --- In m..., "old_cow_yellow" wrote:
> > >
> > > I do not have a LaunchPad.
> > >
> > > I think the emulator side of the LaunchPad already has a user UART to PC
> >VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is
> >implemented in the TUSB chip, not in the F1612 chip. It should work for you
> >without any change.
> > >
> > > If you do want to change the firmware in the TUSB chip, be aware that there
>
> >is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in
>
> >reset. It waits for its own 12MHz crystal to start and stabilize. It then
> >suppless that clock to the TUSB chip and releases the reset. Without this, the
>
> >TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> > >
> > > -- OCY
> > >
> > > --- In m..., "Hoai Anh" wrote:
> > > >
> > > > I am trying to develop a system on MSP430 launchpad. It should do ADC
>from
>
> >F2013 and then transfer data through USB from the Launchpad to PC.
> > > >
> > > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side
> >(by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make
>it
>
> >works like a bridge.
> > > >
> > > > However, I am now have a problem with the TUSB. I tried to download the
> >driver (TUSBWINVCP) but it could not recognized the USB. So I tried another
> >method that using EEPROM burner. Here are the steps I did:
> > > >
> > > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this
>step
>
> >similar to isolating step in the EEPROM burner user guide - just disconnect
> >their SCL pins).
> > > > 2. Install the EEPROM burner.
> > > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
>
> > > >
> > > > However, my PC still does not recognize the USB... I even tried to Update
>
> >Driver through the Device manager but it still doesnt work. I am using Windows
>
> >7. Should it be a problem? Any suggestions or recommendations?
> > > >
> > > > Best Regards,
> > > >
> > >
> >
>
Unfortunately, I dont know how to save the original flash image... Can you show
me how to do that? I am using IAR. That is going to be a very good experience
for me... Is there any way that I contact Gerlich and Sebastian so I can ask for
the image. First thing first, please tell me how to save the original flash
image. Very eager to know how. I dont know how to read the pre-program firmware
in MCU!!!
Thank you very much for your help
________________________________
From: old_cow_yellow
To: m...
Sent: Wed, July 21, 2010 9:57:07 PM
Subject: [msp430] Re: Launchpad USB
Did you not save the original flash image before you re-programmed it?
Gerlich, Sebastian may be able to help you.
I am still waiting for my LaunchPad. Once I get it, that is the second thing I
do. (The first thing is to see if it works at all.)
-- OCY
--- In m..., Hoai Anh wrote:
>
> I got it... I reprogrammed the F1612 to set it provide the TUSB with 12Mhz
>speed
>
> from SMCLK, but it seems does not work. The PC still could not see the USB. How
>
> can I reprogram the F1612 from the factory default? Is there any where I can
> download the code for emulator part for F1612 launchpad?
>
> Regards,
>
> ________________________________
> From: old_cow_yellow
> To: m...
> Sent: Wed, July 21, 2010 6:04:49 PM
> Subject: [msp430] Re: Launchpad USB
> --- In m..., "Hoai Anh" wrote:
> >
> > Interesting, I did not know that TUSB has to use F1612 clock... I
>reprogrammed
>
> >F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB
> >individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1
> >respectively), right?
>
> P27 of TUSB is connected to R19, R22, and P49 of F1612.
> You probably need to remove R19, R22, and disconnect it from P49 of F1612
>before
>
> you add a 12MHz crystal.
> You probably also need to add load capacitors.
>
> P9 of TUSB is connected to some RC and P42 of F1612.
> You probably need to keep the RC but disconnect from P42 of F1612.
>
> >
> > Can it be used without EEPROM? I read the user guide on VCP firmware, it said
>
> >it can load firmware from the host (my PC) to the USB. So what is the point of
>
> >using EEPROM while you can ignore it to reduce cost? There are reasons that
>are
>
> >stated in the user guide but I am not clear:
> > "Storing firmware in EEPROM in TUSB3410 applications has the advantage of
> >automatically using the 3410's unique device ID as the USB serial number. If
> >storing on the host, the only way to achieve a
> > unique serial number is to serialize the EEPROM."
> >
> > As the USB serial number - what does it mean? and if storing on the host,
>what
>
> >does it mean by serializing the EEPROM? Does it not need to use EEPROM in the
> >"storing in the host" case?
>
> Yes, you can store the firmware for the TUSB inside the PC and do not provide
>an
>
> EEPROM. But I do not think it is practical to make a product that way -- unless
>
> you are the only one that does it that way and you only produce one product.
>
> The USB serial number is an additional information for the HOST to recognize
> each individual device amongst all the devices with the same Vendor ID and same
>
> Device ID.
>
> >
> > Regards,
> >
> >
> > --- In m..., "old_cow_yellow" wrote:
> > >
> > > I do not have a LaunchPad.
> > >
> > > I think the emulator side of the LaunchPad already has a user UART to PC
> >VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is
> >implemented in the TUSB chip, not in the F1612 chip. It should work for you
> >without any change.
> > >
> > > If you do want to change the firmware in the TUSB chip, be aware that there
>
> >is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in
>
> >reset. It waits for its own 12MHz crystal to start and stabilize. It then
> >suppless that clock to the TUSB chip and releases the reset. Without this, the
>
> >TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> > >
> > > -- OCY
> > >
> > > --- In m..., "Hoai Anh" wrote:
> > > >
> > > > I am trying to develop a system on MSP430 launchpad. It should do ADC
>from
>
> >F2013 and then transfer data through USB from the Launchpad to PC.
> > > >
> > > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side
> >(by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make
>it
>
> >works like a bridge.
> > > >
> > > > However, I am now have a problem with the TUSB. I tried to download the
> >driver (TUSBWINVCP) but it could not recognized the USB. So I tried another
> >method that using EEPROM burner. Here are the steps I did:
> > > >
> > > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this
>step
>
> >similar to isolating step in the EEPROM burner user guide - just disconnect
> >their SCL pins).
> > > > 2. Install the EEPROM burner.
> > > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
>
> > > >
> > > > However, my PC still does not recognize the USB... I even tried to Update
>
> >Driver through the Device manager but it still doesnt work. I am using Windows
>
> >7. Should it be a problem? Any suggestions or recommendations?
> > > >
> > > > Best Regards,
> > > >
> > >
> >
>
Reply by ●July 22, 20102010-07-22
YES !YES !YES!!! I made it works!!! Just turn on the XT2CLK and pass through the
SMCLK pin...I made a mistakes that I assigned the wrong pin of SMCLK...
However, OCY, you still need to show me how to save the pre-program software in the MCU. Look forward hearing from you. You're the life saver :D!
Thank you
--- In m..., Hoai Anh wrote:
>
> Hi OCY,
>
> Unfortunately, I dont know how to save the original flash image... Can you show
> me how to do that? I am using IAR. That is going to be a very good experience
> for me... Is there any way that I contact Gerlich and Sebastian so I can ask for
> the image. First thing first, please tell me how to save the original flash
> image. Very eager to know how. I dont know how to read the pre-program firmware
> in MCU!!!
>
> Thank you very much for your help
>
> ________________________________
> From: old_cow_yellow
> To: m...
> Sent: Wed, July 21, 2010 9:57:07 PM
> Subject: [msp430] Re: Launchpad USB
>
>
> Did you not save the original flash image before you re-programmed it?
>
> Gerlich, Sebastian may be able to help you.
>
> I am still waiting for my LaunchPad. Once I get it, that is the second thing I
> do. (The first thing is to see if it works at all.)
>
> -- OCY
>
> --- In m..., Hoai Anh wrote:
> >
> > I got it... I reprogrammed the F1612 to set it provide the TUSB with 12Mhz
> >speed
> >
> > from SMCLK, but it seems does not work. The PC still could not see the USB. How
> >
> > can I reprogram the F1612 from the factory default? Is there any where I can
> > download the code for emulator part for F1612 launchpad?
> >
> > Regards,
> >
> >
> >
> >
> >
> > ________________________________
> > From: old_cow_yellow
> > To: m...
> > Sent: Wed, July 21, 2010 6:04:49 PM
> > Subject: [msp430] Re: Launchpad USB
> >
> >
> >
> >
> > --- In m..., "Hoai Anh" wrote:
> > >
> > > Interesting, I did not know that TUSB has to use F1612 clock... I
> >reprogrammed
> >
> > >F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB
> > >individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1
> > >respectively), right?
> >
> > P27 of TUSB is connected to R19, R22, and P49 of F1612.
> > You probably need to remove R19, R22, and disconnect it from P49 of F1612
> >before
> >
> > you add a 12MHz crystal.
> > You probably also need to add load capacitors.
> >
> > P9 of TUSB is connected to some RC and P42 of F1612.
> > You probably need to keep the RC but disconnect from P42 of F1612.
> >
> > >
> > > Can it be used without EEPROM? I read the user guide on VCP firmware, it said
> >
> > >it can load firmware from the host (my PC) to the USB. So what is the point of
> >
> > >using EEPROM while you can ignore it to reduce cost? There are reasons that
> >are
> >
> > >stated in the user guide but I am not clear:
> > > "Storing firmware in EEPROM in TUSB3410 applications has the advantage of
> > >automatically using the 3410's unique device ID as the USB serial number. If
> > >storing on the host, the only way to achieve a
> > > unique serial number is to serialize the EEPROM."
> > >
> > > As the USB serial number - what does it mean? and if storing on the host,
> >what
> >
> > >does it mean by serializing the EEPROM? Does it not need to use EEPROM in the
>
> > >"storing in the host" case?
> >
> > Yes, you can store the firmware for the TUSB inside the PC and do not provide
> >an
> >
> > EEPROM. But I do not think it is practical to make a product that way -- unless
> >
> > you are the only one that does it that way and you only produce one product.
> >
> > The USB serial number is an additional information for the HOST to recognize
> > each individual device amongst all the devices with the same Vendor ID and same
> >
> > Device ID.
> >
> > >
> > > Regards,
> > >
> > >
> > > --- In m..., "old_cow_yellow" wrote:
> > > >
> > > > I do not have a LaunchPad.
> > > >
> > > > I think the emulator side of the LaunchPad already has a user UART to PC
> > >VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is
>
> > >implemented in the TUSB chip, not in the F1612 chip. It should work for you
> > >without any change.
> > > >
> > > > If you do want to change the firmware in the TUSB chip, be aware that there
> >
> > >is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in
> >
> > >reset. It waits for its own 12MHz crystal to start and stabilize. It then
> > >suppless that clock to the TUSB chip and releases the reset. Without this, the
> >
> > >TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> > > >
> > > > -- OCY
> > > >
> > > > --- In m..., "Hoai Anh" wrote:
> > > > >
> > > > > I am trying to develop a system on MSP430 launchpad. It should do ADC
> >from
> >
> > >F2013 and then transfer data through USB from the Launchpad to PC.
> > > > >
> > > > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side
>
> > >(by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make
> >it
> >
> > >works like a bridge.
> > > > >
> > > > > However, I am now have a problem with the TUSB. I tried to download the
> > >driver (TUSBWINVCP) but it could not recognized the USB. So I tried another
> > >method that using EEPROM burner. Here are the steps I did:
> > > > >
> > > > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this
> >step
> >
> > >similar to isolating step in the EEPROM burner user guide - just disconnect
> > >their SCL pins).
> > > > > 2. Install the EEPROM burner.
> > > > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> >
> > > > >
> > > > > However, my PC still does not recognize the USB... I even tried to Update
> >
> > >Driver through the Device manager but it still doesnt work. I am using Windows
> >
> > >7. Should it be a problem? Any suggestions or recommendations?
> > > > >
> > > > > Best Regards,
> > > > >
> > > >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
However, OCY, you still need to show me how to save the pre-program software in the MCU. Look forward hearing from you. You're the life saver :D!
Thank you
--- In m..., Hoai Anh wrote:
>
> Hi OCY,
>
> Unfortunately, I dont know how to save the original flash image... Can you show
> me how to do that? I am using IAR. That is going to be a very good experience
> for me... Is there any way that I contact Gerlich and Sebastian so I can ask for
> the image. First thing first, please tell me how to save the original flash
> image. Very eager to know how. I dont know how to read the pre-program firmware
> in MCU!!!
>
> Thank you very much for your help
>
> ________________________________
> From: old_cow_yellow
> To: m...
> Sent: Wed, July 21, 2010 9:57:07 PM
> Subject: [msp430] Re: Launchpad USB
>
>
> Did you not save the original flash image before you re-programmed it?
>
> Gerlich, Sebastian may be able to help you.
>
> I am still waiting for my LaunchPad. Once I get it, that is the second thing I
> do. (The first thing is to see if it works at all.)
>
> -- OCY
>
> --- In m..., Hoai Anh wrote:
> >
> > I got it... I reprogrammed the F1612 to set it provide the TUSB with 12Mhz
> >speed
> >
> > from SMCLK, but it seems does not work. The PC still could not see the USB. How
> >
> > can I reprogram the F1612 from the factory default? Is there any where I can
> > download the code for emulator part for F1612 launchpad?
> >
> > Regards,
> >
> >
> >
> >
> >
> > ________________________________
> > From: old_cow_yellow
> > To: m...
> > Sent: Wed, July 21, 2010 6:04:49 PM
> > Subject: [msp430] Re: Launchpad USB
> >
> >
> >
> >
> > --- In m..., "Hoai Anh" wrote:
> > >
> > > Interesting, I did not know that TUSB has to use F1612 clock... I
> >reprogrammed
> >
> > >F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB
> > >individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1
> > >respectively), right?
> >
> > P27 of TUSB is connected to R19, R22, and P49 of F1612.
> > You probably need to remove R19, R22, and disconnect it from P49 of F1612
> >before
> >
> > you add a 12MHz crystal.
> > You probably also need to add load capacitors.
> >
> > P9 of TUSB is connected to some RC and P42 of F1612.
> > You probably need to keep the RC but disconnect from P42 of F1612.
> >
> > >
> > > Can it be used without EEPROM? I read the user guide on VCP firmware, it said
> >
> > >it can load firmware from the host (my PC) to the USB. So what is the point of
> >
> > >using EEPROM while you can ignore it to reduce cost? There are reasons that
> >are
> >
> > >stated in the user guide but I am not clear:
> > > "Storing firmware in EEPROM in TUSB3410 applications has the advantage of
> > >automatically using the 3410's unique device ID as the USB serial number. If
> > >storing on the host, the only way to achieve a
> > > unique serial number is to serialize the EEPROM."
> > >
> > > As the USB serial number - what does it mean? and if storing on the host,
> >what
> >
> > >does it mean by serializing the EEPROM? Does it not need to use EEPROM in the
>
> > >"storing in the host" case?
> >
> > Yes, you can store the firmware for the TUSB inside the PC and do not provide
> >an
> >
> > EEPROM. But I do not think it is practical to make a product that way -- unless
> >
> > you are the only one that does it that way and you only produce one product.
> >
> > The USB serial number is an additional information for the HOST to recognize
> > each individual device amongst all the devices with the same Vendor ID and same
> >
> > Device ID.
> >
> > >
> > > Regards,
> > >
> > >
> > > --- In m..., "old_cow_yellow" wrote:
> > > >
> > > > I do not have a LaunchPad.
> > > >
> > > > I think the emulator side of the LaunchPad already has a user UART to PC
> > >VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is
>
> > >implemented in the TUSB chip, not in the F1612 chip. It should work for you
> > >without any change.
> > > >
> > > > If you do want to change the firmware in the TUSB chip, be aware that there
> >
> > >is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in
> >
> > >reset. It waits for its own 12MHz crystal to start and stabilize. It then
> > >suppless that clock to the TUSB chip and releases the reset. Without this, the
> >
> > >TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> > > >
> > > > -- OCY
> > > >
> > > > --- In m..., "Hoai Anh" wrote:
> > > > >
> > > > > I am trying to develop a system on MSP430 launchpad. It should do ADC
> >from
> >
> > >F2013 and then transfer data through USB from the Launchpad to PC.
> > > > >
> > > > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side
>
> > >(by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make
> >it
> >
> > >works like a bridge.
> > > > >
> > > > > However, I am now have a problem with the TUSB. I tried to download the
> > >driver (TUSBWINVCP) but it could not recognized the USB. So I tried another
> > >method that using EEPROM burner. Here are the steps I did:
> > > > >
> > > > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this
> >step
> >
> > >similar to isolating step in the EEPROM burner user guide - just disconnect
> > >their SCL pins).
> > > > > 2. Install the EEPROM burner.
> > > > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> >
> > > > >
> > > > > However, my PC still does not recognize the USB... I even tried to Update
> >
> > >Driver through the Device manager but it still doesnt work. I am using Windows
> >
> > >7. Should it be a problem? Any suggestions or recommendations?
> > > > >
> > > > > Best Regards,
> > > > >
> > > >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
Reply by ●July 22, 20102010-07-22
Sebastian Gerlich is the first and last name of one guy.
He watches and answers question here. Very helpful guy.
For example, see msg #46095 (July 20, 2010).
He may be watching right this moment and show up to help you.
If not, write to: s...@ti.com
I use FET-Pro430-Lite (Free from Elprotronic Inc) to read or restore Flash. This is a software for PC. It needs either the TI FET-UIF hardware or a number of other similar hardware to accomplish read/restor.
--- In m..., "Hoai Anh" wrote:
>
> YES !YES !YES!!! I made it works!!! Just turn on the XT2CLK and pass through the SMCLK pin...I made a mistakes that I assigned the wrong pin of SMCLK...
>
> However, OCY, you still need to show me how to save the pre-program software in the MCU. Look forward hearing from you. You're the life saver :D!
>
> Thank you
> --- In m..., Hoai Anh wrote:
> >
> > Hi OCY,
> >
> > Unfortunately, I dont know how to save the original flash image... Can you show
> > me how to do that? I am using IAR. That is going to be a very good experience
> > for me... Is there any way that I contact Gerlich and Sebastian so I can ask for
> > the image. First thing first, please tell me how to save the original flash
> > image. Very eager to know how. I dont know how to read the pre-program firmware
> > in MCU!!!
> >
> > Thank you very much for your help
> >
> >
> >
> >
> >
> > ________________________________
> > From: old_cow_yellow
> > To: m...
> > Sent: Wed, July 21, 2010 9:57:07 PM
> > Subject: [msp430] Re: Launchpad USB
> >
> >
> > Did you not save the original flash image before you re-programmed it?
> >
> > Gerlich, Sebastian may be able to help you.
> >
> > I am still waiting for my LaunchPad. Once I get it, that is the second thing I
> > do. (The first thing is to see if it works at all.)
> >
> > -- OCY
> >
> > --- In m..., Hoai Anh wrote:
> > >
> > > I got it... I reprogrammed the F1612 to set it provide the TUSB with 12Mhz
> > >speed
> > >
> > > from SMCLK, but it seems does not work. The PC still could not see the USB. How
> > >
> > > can I reprogram the F1612 from the factory default? Is there any where I can
> > > download the code for emulator part for F1612 launchpad?
> > >
> > > Regards,
> > >
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: old_cow_yellow
> > > To: m...
> > > Sent: Wed, July 21, 2010 6:04:49 PM
> > > Subject: [msp430] Re: Launchpad USB
> > >
> > >
> > >
> > >
> > > --- In m..., "Hoai Anh" wrote:
> > > >
> > > > Interesting, I did not know that TUSB has to use F1612 clock... I
> > >reprogrammed
> > >
> > > >F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB
> > > >individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1
> > > >respectively), right?
> > >
> > > P27 of TUSB is connected to R19, R22, and P49 of F1612.
> > > You probably need to remove R19, R22, and disconnect it from P49 of F1612
> > >before
> > >
> > > you add a 12MHz crystal.
> > > You probably also need to add load capacitors.
> > >
> > > P9 of TUSB is connected to some RC and P42 of F1612.
> > > You probably need to keep the RC but disconnect from P42 of F1612.
> > >
> > > >
> > > > Can it be used without EEPROM? I read the user guide on VCP firmware, it said
> > >
> > > >it can load firmware from the host (my PC) to the USB. So what is the point of
> > >
> > > >using EEPROM while you can ignore it to reduce cost? There are reasons that
> > >are
> > >
> > > >stated in the user guide but I am not clear:
> > > > "Storing firmware in EEPROM in TUSB3410 applications has the advantage of
> > > >automatically using the 3410's unique device ID as the USB serial number. If
> > > >storing on the host, the only way to achieve a
> > > > unique serial number is to serialize the EEPROM."
> > > >
> > > > As the USB serial number - what does it mean? and if storing on the host,
> > >what
> > >
> > > >does it mean by serializing the EEPROM? Does it not need to use EEPROM in the
> >
> > > >"storing in the host" case?
> > >
> > > Yes, you can store the firmware for the TUSB inside the PC and do not provide
> > >an
> > >
> > > EEPROM. But I do not think it is practical to make a product that way -- unless
> > >
> > > you are the only one that does it that way and you only produce one product.
> > >
> > > The USB serial number is an additional information for the HOST to recognize
> > > each individual device amongst all the devices with the same Vendor ID and same
> > >
> > > Device ID.
> > >
> > > >
> > > > Regards,
> > > >
> > > >
> > > > --- In m..., "old_cow_yellow" wrote:
> > > > >
> > > > > I do not have a LaunchPad.
> > > > >
> > > > > I think the emulator side of the LaunchPad already has a user UART to PC
> > > >VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is
> >
> > > >implemented in the TUSB chip, not in the F1612 chip. It should work for you
> > > >without any change.
> > > > >
> > > > > If you do want to change the firmware in the TUSB chip, be aware that there
> > >
> > > >is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in
> > >
> > > >reset. It waits for its own 12MHz crystal to start and stabilize. It then
> > > >suppless that clock to the TUSB chip and releases the reset. Without this, the
> > >
> > > >TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> > > > >
> > > > > -- OCY
> > > > >
> > > > > --- In m..., "Hoai Anh" wrote:
> > > > > >
> > > > > > I am trying to develop a system on MSP430 launchpad. It should do ADC
> > >from
> > >
> > > >F2013 and then transfer data through USB from the Launchpad to PC.
> > > > > >
> > > > > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side
> >
> > > >(by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make
> > >it
> > >
> > > >works like a bridge.
> > > > > >
> > > > > > However, I am now have a problem with the TUSB. I tried to download the
> > > >driver (TUSBWINVCP) but it could not recognized the USB. So I tried another
> > > >method that using EEPROM burner. Here are the steps I did:
> > > > > >
> > > > > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this
> > >step
> > >
> > > >similar to isolating step in the EEPROM burner user guide - just disconnect
> > > >their SCL pins).
> > > > > > 2. Install the EEPROM burner.
> > > > > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> > >
> > > > > >
> > > > > > However, my PC still does not recognize the USB... I even tried to Update
> > >
> > > >Driver through the Device manager but it still doesnt work. I am using Windows
> > >
> > > >7. Should it be a problem? Any suggestions or recommendations?
> > > > > >
> > > > > > Best Regards,
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
>
He watches and answers question here. Very helpful guy.
For example, see msg #46095 (July 20, 2010).
He may be watching right this moment and show up to help you.
If not, write to: s...@ti.com
I use FET-Pro430-Lite (Free from Elprotronic Inc) to read or restore Flash. This is a software for PC. It needs either the TI FET-UIF hardware or a number of other similar hardware to accomplish read/restor.
--- In m..., "Hoai Anh" wrote:
>
> YES !YES !YES!!! I made it works!!! Just turn on the XT2CLK and pass through the SMCLK pin...I made a mistakes that I assigned the wrong pin of SMCLK...
>
> However, OCY, you still need to show me how to save the pre-program software in the MCU. Look forward hearing from you. You're the life saver :D!
>
> Thank you
> --- In m..., Hoai Anh wrote:
> >
> > Hi OCY,
> >
> > Unfortunately, I dont know how to save the original flash image... Can you show
> > me how to do that? I am using IAR. That is going to be a very good experience
> > for me... Is there any way that I contact Gerlich and Sebastian so I can ask for
> > the image. First thing first, please tell me how to save the original flash
> > image. Very eager to know how. I dont know how to read the pre-program firmware
> > in MCU!!!
> >
> > Thank you very much for your help
> >
> >
> >
> >
> >
> > ________________________________
> > From: old_cow_yellow
> > To: m...
> > Sent: Wed, July 21, 2010 9:57:07 PM
> > Subject: [msp430] Re: Launchpad USB
> >
> >
> > Did you not save the original flash image before you re-programmed it?
> >
> > Gerlich, Sebastian may be able to help you.
> >
> > I am still waiting for my LaunchPad. Once I get it, that is the second thing I
> > do. (The first thing is to see if it works at all.)
> >
> > -- OCY
> >
> > --- In m..., Hoai Anh wrote:
> > >
> > > I got it... I reprogrammed the F1612 to set it provide the TUSB with 12Mhz
> > >speed
> > >
> > > from SMCLK, but it seems does not work. The PC still could not see the USB. How
> > >
> > > can I reprogram the F1612 from the factory default? Is there any where I can
> > > download the code for emulator part for F1612 launchpad?
> > >
> > > Regards,
> > >
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: old_cow_yellow
> > > To: m...
> > > Sent: Wed, July 21, 2010 6:04:49 PM
> > > Subject: [msp430] Re: Launchpad USB
> > >
> > >
> > >
> > >
> > > --- In m..., "Hoai Anh" wrote:
> > > >
> > > > Interesting, I did not know that TUSB has to use F1612 clock... I
> > >reprogrammed
> > >
> > > >F1612 so maybe that's the reason the TUSB could not work!!! So to use TUSB
> > > >individually, I just need to connect a 12Mhz crystal to pin 26-27 (X2-X1
> > > >respectively), right?
> > >
> > > P27 of TUSB is connected to R19, R22, and P49 of F1612.
> > > You probably need to remove R19, R22, and disconnect it from P49 of F1612
> > >before
> > >
> > > you add a 12MHz crystal.
> > > You probably also need to add load capacitors.
> > >
> > > P9 of TUSB is connected to some RC and P42 of F1612.
> > > You probably need to keep the RC but disconnect from P42 of F1612.
> > >
> > > >
> > > > Can it be used without EEPROM? I read the user guide on VCP firmware, it said
> > >
> > > >it can load firmware from the host (my PC) to the USB. So what is the point of
> > >
> > > >using EEPROM while you can ignore it to reduce cost? There are reasons that
> > >are
> > >
> > > >stated in the user guide but I am not clear:
> > > > "Storing firmware in EEPROM in TUSB3410 applications has the advantage of
> > > >automatically using the 3410's unique device ID as the USB serial number. If
> > > >storing on the host, the only way to achieve a
> > > > unique serial number is to serialize the EEPROM."
> > > >
> > > > As the USB serial number - what does it mean? and if storing on the host,
> > >what
> > >
> > > >does it mean by serializing the EEPROM? Does it not need to use EEPROM in the
> >
> > > >"storing in the host" case?
> > >
> > > Yes, you can store the firmware for the TUSB inside the PC and do not provide
> > >an
> > >
> > > EEPROM. But I do not think it is practical to make a product that way -- unless
> > >
> > > you are the only one that does it that way and you only produce one product.
> > >
> > > The USB serial number is an additional information for the HOST to recognize
> > > each individual device amongst all the devices with the same Vendor ID and same
> > >
> > > Device ID.
> > >
> > > >
> > > > Regards,
> > > >
> > > >
> > > > --- In m..., "old_cow_yellow" wrote:
> > > > >
> > > > > I do not have a LaunchPad.
> > > > >
> > > > > I think the emulator side of the LaunchPad already has a user UART to PC
> > > >VCOM. I think it has only RXD and TXD signals and works up to 9600 b/s. It is
> >
> > > >implemented in the TUSB chip, not in the F1612 chip. It should work for you
> > > >without any change.
> > > > >
> > > > > If you do want to change the firmware in the TUSB chip, be aware that there
> > >
> > > >is no 12MHz crystal for the TUSB. At power-up, the F1612 hold the TUSB chip in
> > >
> > > >reset. It waits for its own 12MHz crystal to start and stabilize. It then
> > > >suppless that clock to the TUSB chip and releases the reset. Without this, the
> > >
> > > >TUSB chip cannot do anything and the PC cannot even enumerate the TUSB chip.
> > > > >
> > > > > -- OCY
> > > > >
> > > > > --- In m..., "Hoai Anh" wrote:
> > > > > >
> > > > > > I am trying to develop a system on MSP430 launchpad. It should do ADC
> > >from
> > >
> > > >F2013 and then transfer data through USB from the Launchpad to PC.
> > > > > >
> > > > > > With that's in mind, I reprogrammed the MSP430F1612 in the emulator side
> >
> > > >(by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make
> > >it
> > >
> > > >works like a bridge.
> > > > > >
> > > > > > However, I am now have a problem with the TUSB. I tried to download the
> > > >driver (TUSBWINVCP) but it could not recognized the USB. So I tried another
> > > >method that using EEPROM burner. Here are the steps I did:
> > > > > >
> > > > > > 1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this
> > >step
> > >
> > > >similar to isolating step in the EEPROM burner user guide - just disconnect
> > > >their SCL pins).
> > > > > > 2. Install the EEPROM burner.
> > > > > > 3. After the EEPROM burner finished, I connected the Launchpad to the PC.
> > >
> > > > > >
> > > > > > However, my PC still does not recognize the USB... I even tried to Update
> > >
> > > >Driver through the Device manager but it still doesnt work. I am using Windows
> > >
> > > >7. Should it be a problem? Any suggestions or recommendations?
> > > > > >
> > > > > > Best Regards,
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
>
