AVR 32 Chip Creator|生產應用線上App不用買-HotApp4Game

Did you know that the AVR32 chip is constructed with slightly more than 85% of its signals available as General Purpose I/O (GPIO)? Of the roughly 15% of the remaining signals dedicated to functions other than GPIO, only nine signals are not for Power, Ground, Reset, and Non-Connection purposes.

The AVR32 is well known as a powerful system on a chip that also features complete peripheral sub-systems such as Ethernet, Universal Synchronous/Asynchronous Receiver/Transmitters (USART), Analog to Digital Converters (ADC), Digital to Analog Converters (DAC), External Memory Bus Controllers, USB 2.0, Real-Time Clock, and a number of others, depending upon the chip variation. These peripherals only need to be activated in code, and connected to interface devices on your board, then you are off to the races.

However, as powerful as these chips are, there is no denying that coming up with the right configuration for your chip's target environment can be a real head-scratcher. All of those pins are GPIO by default, and each pin has up to three other tasks it can be assigned to beyond generic I/O. For example, GPIO 3 can be any one of I/O bit, USART0.RTS, EIM.EXTINT[4], or DAC.DATA[0], depending on how you set the GPIO multiplex control register. As you know, some peripherals require a complete set of signals to function properly, while some, such as GPIO itself, can be implemented as a series of single-bit mix and match signals. In this series, though, some signals can be selected from multiple GPIO signal table entries, but then again, some only have one choice, and you must commit to it, such as in the case of MACB.CRS, which can not be selected if you have already decided you want to use four Chip Selects on EIB. In other words, the need for one signal can change your entire chip layout.

I created the AVR32 Chip Creator because I prefer my processor to tell me up front what it is going to be, instead of making me guess. Simply tell the app what processor you are starting with, what peripherals you want to activate, including the number of selectable pins you need to use such as number of external interrupts available, number of GPIO pins available, size of external memory to support, and other parameters, then let it calculate the layout for you.

From your requirements information, a view is produced containing information about which control registers to set to which value, which bits of various data and control registers to write to when handling your direct and peripheral IO, and finally, how to enumerate your chip's pins during electrical layout. In essence, you can create an entire custom microprocessor-based system on a chip in a few minutes, and be ready to use that configuration right away.

In some cases, a non-resolvable conflict will be found due to too many inter-signal dependencies, but you can typically overcome this by reducing the count of IO pins, or other multi-channel capabilities such as ADC, EIM, etc. The conflict report will often lead you to discovering which type of other peripheral activities to reduce when solving your design. When attempting to avoid a non resolvable conflict it is helpful to consult the 32-bit Atmel AVR Microcontroller Datasheet (Complete Edition).

Permissions

This app uses Read and Write to External Storage, to give you access to the HTML files created from each session.

Notices

AVR is a registered trademark of Atmel.

About the Author

This app, associated artwork, and all related material, was created and published by Daniel Patterson.

Daniel has more than 30 years of experience in Embedded Systems development, is a Microsoft Certified Solution Developer, and is proficient at ASM, C, C++, C#, Java, Verilog, VHDL, .NET, Android, Atmel, Intel, MicroChip, Parallax, Xilinx, Zilog, as well as Electronics Design, Prototyping, and Production.