You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

Notification title

TE USB FX2 Technology Stack Generation 3 released.

Notification type

Firmware release, device driver release, API release, application code release.

Notification entity

Major change.

Products affected

  • Trenz Electronic TE0300 series
  • Trenz Electronic TE0320 series
  • Trenz Electronic TE0630 series
Trenz Electronic
series
Trenz Electronic
part number
base
serial number
TE0300TE0300-01BM 
TE0300TE0300-01BMLP 
TE0300TE0300-01I 
TE0300TE0300-01IBM 
TE0300TE0300-01IBMLP 
TE0300TE0300-01M 
   
TE0320TE0320-00-EV02 
TE0320TE0320-00-EV02B 
TE0320TE0320-00-EV02I 
TE0320TE0320-00-EV02IB 
   
TE0630TE0630-00I438891
TE0630TE0630-00IBF438903
TE0630TE0630-00IV438874

Description of change

  • changed USB VID/PID from DEWEsoft's to Trenz Electronic's
  • changed device driver from DEWEsoft's to Trenz Electronic's based on Cypress Semiconductor's
  • certified Trenz Electronic's device driver
  • changed C++ API from DEWEsoft's to Trenz Electronic's based on Cypress Semiconductor's
  • added Trenz Electronic's .NET API based on Cypress Semiconductor's
  • changed C++ sample applications from DEWEsoft's to Trenz Electronic's based on Trenz Electronic's API
  • added Trenz Electronic's .NET sample applications based on Trenz Electronic's API

Reason for change

  • USB VID was a generic third-party's; it is now the official Trenz Electronic's vendor ID (0x0BD0)
  • device drivers were proprietary DEWESoft's; they are now Trenz Electronic's based on mainstream Cypress Semiconductor's
  • device driver were uncertified DEWESoft's; they are now certified Trenz Electronic's
  • C++ API were proprietary DEWESoft's; they are now proprietary Trenz Electronic's based on the mainstream Cypress Semiconductor's C++ API
  • proprietary Trenz Electronic's .NET API are based on the mainstream Cypress Semiconductor's .NET API

Impact

Firmware, device driver, API and application code are incompatible between generations.

Proposed countermeasures

Firmware, device driver, API and application code shall belong to the same generation.

After determining what generation your module belongs to, you have to migrate firmware, device driver, API and application code to the other generation.

1) What generation does my module belong to?

Start OpenFutNet.exe. The FX2 microcontroller firmware major version corresponds to your generation.

You might have to press the "Refresh" button.

Open Device Manager and check if your operating system registered the device consistently with the generation determined by OpenFutNet.

generationDevice ManagerVID/PID

FX2 firmware
major version

remarks
1nd

0x0547/0x10022Discontinued (no longer supported)
2nd0x0547/0x10023Discontinued (no longer supported)
3rd0x0BD0/0x03003Recommended

2) How do I migrate my firmware module back and forth from one technology stack generation to the other?

Download the FX2 microcontroller firmware file corresponding to the generation you want to migrate to. Start OpenFutNet.exe. Press the "Select *.iic file" button and browse to the firmware file. Press the "Program USB" button.

3) How do I migrate the device driver back and forth from one technology stack generation to the other?

Just install the device driver  corresponding to the generation you want to migrate to.

4) How do I migrate the API back and forth from one technology stack generation to the other?

5) How do I migrate my application code back and forth from one technology stack generation to the other?

Please consult our detailed  porting guides.

6) Something went wrong, what now?

Please read our Technology Stack Overview and follow our recommendations. Sill in trouble? Then please contact us.

Expected production availability date

2nd.September 2013

PCN representative

Mr Thorsten Trenz
Trenz Electronic GmbH
support%trenz-electronic.de

  • No labels