Archive for the ‘FAQ’ Category.

FT2232C, FT2232L, FT2232D

Час від часу зустрічаю запитання по відмінностях між цими мікросхемами. В описах чи відкритих проектах в інтернеті згадується FT2232C, а в продажу зараз є FT2232D. Виникають сумніви у сумісності програм та адаптерів.
Як це часто буває, всі ці сумніви розвіюються при перегляді сторінки опису FT2232D. Але чомусь багатьом легше не подивитися на сайті виробника, а спитати на форумі чи набрати рядок «різниця FT2232C та FT2232D» в пошуковику. Ну що ж, ось він, цей рядок для нього, хай йому буде легше :-)

Документації на старіші версії мікросхем на сайті вже немає, але безпосередньо на сторінці сказано:

The FT2232D is the 3rd generation of FTDI’s popular USB UART/FIFO IC. The FT2232D is an updated version of the FT2232C and its lead free version, the FT2232L. Please note that the FT2232D is not an new generation of device.

The FT2232D is lead free and pin compatible with the original FT2232C and FT2232L devices. All the original device features are supported with some additional features available including a CPU-style FIFO mode and an extended operating temperature range.

»»» І що ж все це означає?

avreal and LPT in Windows

From AVReAl‘s point of view there are two Windows families.

Windows 9X family OS like Windows 98 does not require LPT access driver. avreal uses direct IO access when working in it.

NT-line OS like Windows XP or Windows 7 requires a DLPortIO driver. Driver installation process for 32-bit and 64-bit OS has been described before.

For all Windows versions parallel port number or base address must be set in command line, for example -p1, -p378. Port number is just alias for standard address as it is noted in -p switch description. Fixed 378/278/3BC addresses are used for LPT1/2/3.

Non-standard base address for PCI-LPT extension board can be found on port properties tab in device manager.

»»» How to see the address of LPT in Windows

avreal and LPT in Linux

Unlike in NT-line Windows a DLPortIO.sys driver is not required for LPT port access in Linux/x86 (both 32- and 64-bit). Unlike in Windows 98 any program in Linux can’t access ports without permissions.

There are two ways — direct IO-port access and parport device usage. Direct access provides faster programming but requires root privileges when avreal is started.

Continue reading ‘avreal and LPT in Linux’ »

“A” and “not-A” AVRs

I have answered the question about differences between new “A-version” of tinyAVR/megaAVR mirocontrollers and their predecessors. Now I decided to compare the controllers more detailed from a programmer (as software writer) point of view. It is not an ultimate analysis of the differencies but not only Migration Notes were studied. Also microcontrollers datasheets were compared.

As it was mentioned earlier, A-versions work in all VCC and frequency range that was covered by both regular and V/L-versions of predcessors. Also in most cases max consumption currents became lower and typical ones much lower. In the rest new uCs are functionally identical replacement for old uCs. Except separate noted controllers device signatures where not changed.
But in some cases new abilities appeared, new SFR and control bits were added.

So, what is the difference between

Continue reading ‘“A” and “not-A” AVRs’ »

What is the difference between ATtiny2313A and ATtiny2313?

Questions about differences between new “A-version” of AVR mirocontrollers and their predecessors often are found in site log. People look for “what is the difference between atmega48p and atmega48pa” or “atmega8a and atmega8 programming distinction”.

The “microcontroller programming” sentence may have different meanings.

Continue reading ‘What is the difference between ATtiny2313A and ATtiny2313?’ »

avreal synchronisation lost

Everything you wanted to know about,
but were afraid to ask.

As can be found in site log phrase “synchronisation lost” is one of most popular in site search, but no one asks the question in comments.

“synchronisation lost” message means programmer-to-microcontroller communication fault. SPI interconnection between programming adapter and microcontroller works in the same manner as between two microcontrollers.

spi-loop

Continue reading ‘avreal synchronisation lost’ »

[flagcounter image]