The Synthetic PIC
Verion 1.1
This a VHDL synthesizable model of a simple PIC 16C5x microcontroller.
It is not, and is not intended as, a high fidelity circuit simulation.
This package includes the following files. Note that the license agreement
is stated in the main VHDL file, PICCPU.VHD and common questions are answered
in the file SYNTHPIC.TXT
Files:
README.TXT This file..
SYNTHPIC.TXT Questions and Answers
PICCPU.VHD Main processor VHDL file
PICALU.VHD ALU for the PICCPU
PICREGS.VHD Data memory
PICROM.VHD Program memory (created by HEX2VHDL utility)
PICTEST.VHD Simple test bench I used to do testing (optional)
PICTEST.CMD My Viewlogic ViewSim command file (again, optional)
TEST1.ASM First program I assembled and ran on it.
TEST2.ASM Another test program..
TEST3.ASM Yet another..
TEST4.ASM Yet another..
TEST5.ASM Yet another..
TEST6.ASM Yet another..
HEX2VHDL.CPP Utility for converting
Custom Visual Basic Packager and Installer for Visual Basic Developers. This is a group of standard exe projects
1. Packager 2. Setup1
The packager works like Visual basic Application deployment Wizard. And the setup1 project is used for the installation of the package. This project demonstrates how to compile visual basic project without launching the Vb6 kit and retrieving the dependency
Files of any Visual basic project (although roughly done without any specific algorithm), Somebody can help me with this. I don’ t have time for the project, so I don’ t want any comment on the code indentation or arrangement and variable scoping.
Comments are in the code therefore it would not be a problem to understand the code. If anyone wants to vote, I will like it
Oh! I found some of the setup1 code and modify it with new features, so i have no or less credit for the setup1 project
I felt like sharing code with PSCites. Thats why I made it
MCPU is a minimal cpu aimed to fit into a 32 Macrocell CPLD - one of the smallest available programmable logic devices. While this CPU is not powerful enough for real world applications it has proven itself as a valuable educational tool. The source code is just a single page and easily understood. Both VHDL and Verilog versions are supplied. The package comes with assembler, emulator and extensive documentation.
VxWorks 6.6 BSP開發執導
This document describes, in general terms, the elements that make up a board
support package [BSP], the requirements for a VxWorks BSP, and the general
behavior of a BSP during the boot process. This document outlines the steps
needed to port an existing BSP to a new hardware platform or to write a new
VxWorks BSP for custom hardware using a reference BSP or template BSP as a
starting point. It provides hints and tips for debugging a BSP and solving common
BSP development problems. It also provides information on the BSP validation test
suite [BSP VTS] that is used to assess the functionality of a VxWorks BSP.
This document contains a detailed description of the usage and configuration of the JSVM [Joint Scalable Video Model] software for the Scalable Video Coding [SVC] project of the Joint Video Team [JVT] of the ISO/IEC Moving Pictures Experts Group [MPEG] and the ITU-T Video Coding Experts Group [VCEG].
It provides information how to build the software on Windows32 and Linux platforms. It contains a description of the usage and configuration for the binaries built from the software package, including examples for spatial, SNR and combined scalability scenarios.
Guidelines for the integration and validation of new tools in the software are provided.
Java has become a confusing world. Five years ago, there were few decisions to make once
you started programming in Java—you used AWT for graphical user interfaces, sockets for
network programming, and hacked together everything else you needed. Since then, though,
the APIs available for the Java language have grown, and grown. . . and grown. Now you can
dabble in Swing, servlets, Enterprise JavaBeans (EJB), JavaMail, and more. Additionally,
there are now packages of APIs, like the Java 2 Micro Edition (J2ME) and Java 2 Enterprise
Edition (J2EE). While these packages seem to be nicely wrapped bundles of useful APIs, they
don t help the average developer figure out how to piece together the APIs contained in these
packages. Though it s simple to find documentation on the individual APIs, getting the "big
picture" is difficult, at best. One of the most interesting, but difficult, aspects of Java today is
building Java enterprise applications using the J2EE package.
Generate Possion Dis.
step1:Generate a random number between [0,1]
step2:Let u=F(x)=1-[(1/e)x]
step3:Slove x=1/F(u)
step4:Repeat Step1~Step3 by using different u,you can get x1,x2,x3,...,xn
step5:If the first packet was generated at time [0], than the
second packet will be generated at time [0+x1],The third packet will be generated at time [0+x1+x2],
and so on ….
Random-number generation
1.static method random from class Math
-Returns doubles in the range 0.0 <= x < 1.0
2.class Random from package java.util
-Can produce pseudorandom boolean, byte, float, double, int, long and Gaussian values
-Is seeded with the current time of day to generate different sequences of numbers each time the program executes
Java 程序編碼規范
所有的程序開發手冊都包含了各種規則。一些習慣自由程序人員可能對這些規則很不適應，但是在多個開發人員共同寫作的情況下，這些規則是必需的。這不僅僅是為了開發效率來考慮，而且也是為了后期維護考慮。
內容: 命名慣例 、Java文件樣式 、代碼編寫格式 、程序編寫 、編程技巧 、Swing 、調試 、性能 、可移植性
1) 命名規范
定義這個規范的目的是讓項目中所有的文檔都看起來像一個人寫的，增加可讀性，減少項目組中因為換人而帶來的損失。（這些規范并不是一定要絕對遵守，但是一定要讓程序有良好的可讀性）
l Package名：Package名應該都是由一個小寫單詞組成。
l Class名：Class名必須由大寫字母開頭而其他字母都小寫的單詞組成
l Class 變量名：變量名用一個小寫字母開頭。后面的單詞用大寫字母開頭。
l Static Final 變量名：Static Final 變量名應該都大寫，并且指出完整含義。
l 參數名：參數的名字必須和變量的命名規范一致。
l 數組名：數組應該總是用下面的方式來命名：
byte[] buffer 而不是：byte buffer[]
l 方法的參數：使用有意義的參數命名，如果可能的話，使用和要賦值的字段一樣的名字：
