Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Has anyone worked with Cygnal MCUs?

Status
Not open for further replies.

Z80

Full Member level 1
Joined
Feb 20, 2004
Messages
96
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,288
Activity points
1,257
1.8 volt arm7

Hi

I want to start a new project and I need a really fast MCU. After some searches I have run across Cygnal MCUs, up to 100 MIPS with a C51 core! I was curious if anyone has worked with any of these chips, maybe he/she could share some experiences. Thank you.
 

ejtag 1.11 driwer

Hi Z80,

I use the C8051F120 since some mouth.
The 8051 products of Cygnal (Silicon lab, now)
is very very cool.

But caution, for the UARTs of F120, the IDE constructor
"Config2 1.11" has some bug. see only the forum.

But micropross work perfectly..

Z80 said:
Hi

I want to start a new project and I need a really fast MCU. After some searches I have run across Cygnal MCUs, up to 100 MIPS with a C51 core! I was curious if anyone has worked with any of these chips, maybe he/she could share some experiences. Thank you.
 

HI .. I have used those chips since their early days . thouhg i haven't used the lastest 100 mips . But i have used the 50 mips ..Which is more that enough raw power for most applications .. I designed several tcp/ip based servers and they are really fast .. I did design a tiny text scanner
that could fit on a RING . and used the F300 with buiil in ADC capability and to get the data out i used the internal UART runnning at 25 Mhz !
it was a blast ! this is impossible with other chips ! the fact that this little chip (MP11 package ) has a built a high speed signal generation capability makes it imbeatable !. This chips were in my arsenal as my second most lethal weapon after now defunct TRISCEND ..
 

yodathegreat said:
But caution, for the UARTs of F120, the IDE constructor
"Config2 1.11" has some bug. see only the forum.

Wow, do they have hardware suport for IDE? This is exactly what I need. I admit I have only looked "on the run" through the datasheets, I'll really have to check them thoroughly.
 

yup,
an peripheral builder..( a peripheral configurer for assembly)
it also come with a driver support for keil and reisonance downloadable at www.cygnal.com ..
good speed, run it at full speed.. never tried over clocking though but..
got super response for adc and dacs with filters
sam
 

I prefer to use avr mega series at now,because they have a lot of RAM and Flash compared to classic 8051 and is 12 times faster,AVR can work up to 24MHZ and the core and ASM instructions is better than 8051,

The 100MHZ cygnal does not give you 100 MIPS ,it gives you about 30MIPS,and the instruction of 8051 is not powerful compared to avr,

I heared from a person that worked with cygnal ,That it have noises and problems in high frequency and he does not have these problems with AVR at all.

I suggest forget limited stack size 8051(stack is critical for large applications and RTOS)

8051 is only usable for very small embedded application ,for higher code size and speed switch to AVR ,then ARM7,.....


bye
 

Hi 7rots51 ,,Oh i see what you mean .you know every time a manufacturer mention MIPS is always PEAK misp .. The cyganl chip has a third of it's instructions that execute at 1 cycle per clock .. another third take 2 cycles and some more complex instructions execute at 3 per cycle
so in the worst case yes it will execute at 33mips and in the PEAK at 100 mips .. Which is NOT BAD ,, NOT BAD The avr is also a good chip but it should not be compared to the original 51 The gentleman that open this topic asked about the CYGNAL .chip ..and that chip comes with a lot of RAM too and is a new generation of chips just as AVR are .They only kept the same instruction set .but the implementation is as RISC as in the AVR .
So basically is a matter of flavor .. to me BOTH are very good chips ..I used more the cygnal because is NOT JUST A MICROCONTROLLER but is can be catalogued as a SOC chip because it comes with much more peripherals options . Those chips have much more advanced PERIPHERALS .The lastest has a USB 2 interface
So here is the datail of each one



AVR
Device Description
AT90S1200 1-Kbyte In-System programmable Flash Program Memory,
64-Byte EEPROM, 32-Byte Register File, Up to 12 MIPS
throughput at 12 MHz.

AT90S2313 2-Kbyte In-System programmable Flash Program Memory,
160 byte SRAM, 128 Byte EEPROM, Up to 10 MIPS throughput at 10
Mhz.

megaAVR
Device Description
ATmega128 128-Kbyte self-programming Flash Program Memory,
4-Kbyte SRAM, 4-Kbyte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. Up to 16 MIPS throughput at
16 Mhz.

ATmega128L 128-Kbyte self-programming Flash Program Memory,
4-Kbyte SRAM, 4-Kbyte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. Up to 8 MIPS throughput at 8
Mhz. 3 Volt Operation.

ATmega16 16-Kbyte self-programming Flash Program Memory,
1-Kbyte SRAM, 512 Byte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. Up to 16 MIPS throughput at
16 Mhz.

ATmega162 16-Kbyte self-programming Flash Program Memory,
1-Kbyte SRAM, 512 Byte EEPROM, JTAG interface for
on-chip-debug. Up to 16 MIPS throughput at 16 MHz.

ATmega162L 16-Kbyte self-programming Flash Program Memory,
1-Kbyte SRAM, 512 Byte EEPROM, JTAG interface for
on-chip-debug. Up to 8 MIPS throughput at 8 MHz. 3 Volt
Operation.

ATmega162V 16-Kbyte self-programming Flash Program Memory,
1-Kbyte SRAM, 512 Byte EEPROM, JTAG interface for
on-chip-debug. Up to 1 MIPS throughput at 1 MHz.

ATmega165 16-Kbyte self-programming Flash Program Memory,
1-Kbyte SRAM, 512 Byte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. Up to 16 MIPS throughput at
16 MHz. 5 Volt Operation.
1.8V version: ATmega165V

ATmega165V 16-Kbyte self-programming Flash Program Memory,
1-Kbyte SRAM, 512 Byte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. Up to 8 MIPS throughput at 8
MHz. 5 Volt Operation.
4.5V version: ATmega165

ATmega168 16K Byte self-programming Flash Program Memory, 1K
Byte SRAM, 512 Bytes EEPROM, 8 Channel 10-bit
A/D-converter(TQFP/MLF). debugWIRE On-chip Debug System. Up to
20 MIPS throughput at 20 MHz. 1.8 - 5.5 Volt Operation
(ATmega168V).
4K Byte version: ATmega48
8K Byte version: ATmega88

ATmega169 16-Kbyte self-programming Flash Program Memory,
1-Kbyte SRAM, 512 Byte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. 4 X 25 Segment LCD Driver.
Up to 16 MIPS throughput at 16 MHz. 5 Volt Operation.
1.8V version: ATmega169V

ATmega169V 16-Kbyte self-programming Flash Program Memory,
1-Kbyte SRAM, 512 Byte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. 4 X 25 Segment LCD Driver.
Up to 1 MIPS throughput at 1 MHz.
4.5V version: ATmega169

ATmega16L 16-Kbyte self-programming Flash Program Memory,
1-Kbyte SRAM, 512 Byte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. Up to 8 MIPS throughput at 8
Mhz. 3 Volt Operation

ATmega32 32-Kbyte self-programming Flash Program Memory,
2-Kbyte SRAM, 1-Kbyte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. Up to 16 MIPS throughput at
16 Mhz.

ATmega32L 32-Kbyte self-programming Flash Program Memory,
2-Kbyte SRAM, 1-Kbyte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. Up to 8 MIPS throughput at 8
MHz. 3 Volt Operation.

ATmega48 4K byte self-programming Flash Program Memory, 512
byte SRAM, 256 Byte EEPROM, 8 Channel 10-bit
A/D-converter(TQFP/MLF). debugWIRE On-chip Debug System. Up to
20 MIPS throughput at 20 MHz. 1.8 - 5.5 Volt Operation
(ATmega48V).
8K Byte version: ATmega88
16K Byte version: ATmega168

ATmega64 64-Kbyte self-programming Flash Program Memory,
4-Kbyte SRAM, 2-Kbyte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. Up to 16 MIPS throughput at
16 Mhz.

ATmega64L 64-Kbyte self-programming Flash Program Memory,
4-Kbyte SRAM, 2-Kbyte EEPROM, 8 Channel 10-bit A/D-converter.
JTAG interface for on-chip-debug. Up to 8 MIPS throughput at 8
Mhz. 3 Volt Operation.

ATmega8 8-Kbyte self-programming Flash Program Memory, 1-Kbyte
SRAM, 512 Byte EEPROM, 6 or 8 Channel 10-bit A/D-converter. Up
to 16 MIPS throughput at 16 Mhz.

ATmega8515 8-Kbyte self-programming Flash Program Memory, 544
Byte internal + up to 64 Kbyte external SRAM, 512 Byte EEPROM.
Up to 16 MIPS throughput at 16 Mhz.

ATmega8515L 8-Kbyte self-programming Flash Program Memory, 544
Byte internal + up to 64 Kbyte external SRAM, 512 Byte EEPROM.
Up to 8 MIPS throughput at 8 Mhz. 3 Volt Operation

ATmega8535 8-Kbyte self-programming Flash Program Memory, 544
Byte SRAM, 512 Byte EEPROM, 8-channel 10-bit A/D Converter. Up
to 16 MIPS throughput at 16 MHz.

ATmega8535L 8-Kbyte self-programming Flash Program Memory, 544
Byte SRAM, 512 Byte EEPROM, 8-channel 10-bit A/D Converter. Up
to 8 MIPS throughput at 8 MHz. 3 Volt Operation

ATmega88 8K Byte self-programming Flash Program Memory, 1K
Byte SRAM, 512 Bytes EEPROM, 8 Channel 10-bit
A/D-converter(TQFP/MLF). debugWIRE On-chip Debug System. Up to
20 MIPS throughput at 20 MHz. 1.8 - 5.5 Volt Operation
(ATmega88V).
4K Byte version: ATmega48
16K Byte version: ATmega168

ATmega8L 8-Kbyte self-programming Flash Program Memory,
1-Kbyte SRAM, 512 Byte EEPROM, 6 or 8 Channel 10-bit
A/D-converter. Up to 8 MIPS throughput at 8 Mhz. 3 Volt
Operation

tinyAVR
Device Description
ATtiny11 1-Kbyte In-System programmable Flash Program Memory,
32 byte SRAM, Up to 6 MIPS throughput at 6 Mhz.

ATtiny12 1-Kbyte In-System programmable Flash Program Memory,
32 byte SRAM, 64 Byte EEPROM, Up to 8 MIPS throughput at 8
Mhz.

ATtiny13 1-Kbyte In-System programmable Flash Program Memory,
64-Byte SRAM, 64-Byte EEPROM, 32-Byte Register File, 4-channel
10-bit A/D, Up to 20 MIPS throughput at 20 MHz, 5 Volts. 1.8 -
5.5 Volt Operation.

ATtiny15L 1-Kbyte In-System programmable Flash Program Memory,
64-Byte EEPROM, 32-Byte Register File, 4-channel 10-bit A/D,
Up to 1.6 MIPS throughput at 1.6 MHz. 3-volt operation

ATtiny2313 2K Bytes of In-System Self-Programmable Flash, 128
Bytes In-System Programmable EEPROM, 128 Bytes Internal SRAM.
USI--Universal Serial Interface, Full Duplex UART. debugWIRE
for on-chip-debug. Up to 20 MIPS throughput at 20 MHz.

ATtiny26 2K Flash Program Memory, 128 Bytes SRAM, 128-Byte
EEPROM, 11-Channel 10-bit A/D converter. Universal Serial
Interface. High Frequency PWM. Up to 16 MIPS throughput at 16
MHz

ATtiny26L 2K Flash Program Memory, 128 Bytes SRAM, 128 Bytes
EEPROM, 11 Channel 10-bit A/D converter. Universal Serial
Interface. High Frequency PWM. Up to 8 MIPS throughput at 8
MHz. 3-volt operation

ATtiny28L 2K Flash Program Memory, 128 Bytes SRAM (+32bytes
register file), Keyboard interrupt. Up to 4 MIPS throughput at
4 MHz

ATtiny28V 2K Flash Program Memory, 128 Bytes SRAM (+32bytes
register file), Keyboard interrupt. Up to 1 MIPS throughput at
1 MHz. 1.8 Volt operation



To compare the cygnal chip with the AVR is not posible because The cygnal chips is Belongs to another category .Once again these are system on a chip capable architectures and MIXED signal MCU
Take a look at **broken link removed**

On the speed factor the Cygnal has much faster products , on the ram side the cygnal win on the flash both have up to 128kb
But on the peripherals . No question the cygnal is a real winner
I use both but when i need something special i use the Cygnal
with just one circuit i can do so much!
 

Since this thread seems to generate a debate, I thought I should give you some details about my project.
I want to build an audio CD player that uses a CD-ROM. What is special about my project is that the audio doesn't come from the CD-ROM's analog output, nor its S/PDIF output, but it is extracted digitally through the IDE interface. Why do this? Don't ask, it's just something that CAN"T be changed. Since the MCU that will do this will also have to do other things meanwhile (scan a keyboard, send some data to a dispaly, etc), I need a fast MCU. And I really don't want to end up seeing that the chip I chose can't satisfy the demands. So I thought I should use the fastest MCU that I can afford. Looking for it, I have come accross Cygnal MCUs. That's about it. Any comments?
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top