Hi, I am using Dynamic C version 9.62 & Rabbit Field Utility 3.05. Also I am using rabbit module RCM3100. I am trying to load my program in rabbit 3000 processor using RFU. I have created a.bin file & tried downloading program with RFU using following steps. Compiled the project with Compile mode as 'Compile defined target configuration to.bin file' & selecting appropriate target (RCM3100 512K SRAM, 512K Flash) in target-less options in project settings.
Also included the default rabbit bios while compiling. After creating.bin file, downloaded it using RFU(version 3.05) after setting the appropriate coldload.bin, pilot.bin & flash.ini file paths. While downloading messages 'Sending Coldloader', 'Sending Pilot Bios', 'Erasing Flash' & 'Sending Program' respectively were displayed.
After download was complete, removed the programming cable & cycled power to rabbit module to reset it. After resetting rabbit module, program did not execute. Are there any more options or settings that are required? Kindly guide me to download my program using RFU. Dec 29, 2011 in by New to the Community ( 0 points). Hi, I have checked on my board.
It is working for me. Try to compile and load the sample application FLASHLED2.C from the path C: DCRABBIT9.62 Samples RCM3100 1. Open the file FLASHLED2.C from the Dynamic C 9.62 2. Click on Options-project options-Compiler -Bios memory setting as code and Bios in flash, 3. From the targetless -select RCM3100 then click on OK 4. Click on Compile-compile to bin file -Compile to flash 5. Load the FLASHLED2.bin file through the RFU 3.05 Check the DS1 and DS2 (two leds will blink), remove the PROG cable and reset the board, it should work.
Jan 6, 2012 by Veteran of the Digi Community ( 653 points).
RabbitLink Software This chapter describes the software functionality available when using a RabbitLink. 3.1 Downloading and Debugging via the RabbitLink Downloading a program to an embedded target via the RabbitLink is done using Dynamic C or the Rabbit Field Utility (RFU). The rows in the following table show which versions of Dynamic C and the RFU are compatible with which versions of the RabbitLink firmware. The firmware version is the same as its serial console; the version number is displayed in the console's startup message. Compatibility Between Dynamic C and the RabbitLink Firmware. Rabbit Field Utility Version 1.00 Versions 7.03 thru 7.06 Version 2.0 Version 2.00 Versions 7.10 thru 7.26 Version 2.20 and later Version 2.05 Versions 7.30 and later Version 2.20 and later Before a program can be downloaded to a Rabbit-based target, the RabbitLink must be visible on the network.
It must also be visible to Dynamic C or the Rabbit Field Utility (RFU). This is accomplished by setting the network parameters on the RabbitLink board and giving this information to Dynamic C or the RFU. 3.1.1 RabbitLink Network Parameters Follow the steps in if you have not already done so.
The RabbitLink requires an IP address, a gateway address, a netmask and a port number to communicate across a network. 3.1.2 More RabbitLink Network Parameters Enter the RabbitLink addresses in the Communications dialog box. Depending on your version of Dynamic C, the Communications dialog box is accessed by choosing it directly from the Options menu or by choosing Project Options from the Options menu and then selecting the Communications tab. From the RFU, the Communications dialog box is accessed from the Setup menu. The Network Address field should contain the IP address of the RabbitLink. The Control Port field should be set to the TCP port number that the RabbitLink uses to accept control commands from Dynamic C-the default value is 4244. If the RabbitLink is behind a firewall, the Control Port field should be set to the port on the firewall that is being forwarded to the RabbitLink.
If a RabbitLink or multiple RabbitLinks are attached to a local network, press the Discover button in the Communications dialog box to have Dynamic C or the RFU send a broadcast message to each RabbitLink attached to the network. The default UDP port for discovery is 4242. Each RabbitLink will respond with its IP address, name, control port, current status, and MAC address. Selecting any line in the Discover window will cause the information for that RabbitLink to be placed into the appropriate fields in the Communications dialog box.
3.1.3 Password Protection Though not required, it is highly recommended that the passphrase security feature be activated before the RabbitLink is deployed. This gives some protection to the embedded target system from unauthorized communication.
The passphrase may be up to 256 characters long. The serial console command ' set passphrase' will prompt twice for a passphrase and will store the hashed value of it on the RabbitLink. When a session starts, the RabbitLink will ask for the passphrase, allowing access to the embedded system only after receiving the correct value. If no passphrase is set, just press when asked for it. If you forget the passphrase, the only way to recover is to use the RabbitLink serial console to set a new passphrase. This will require the hardware connections shown in and the software setup described in.
3.1.4 Using Dynamic C or the RFU to Download Regardless of whether you use the RFU or Dynamic C, downloading across an Ethernet connection is essentially the same as across a serial connection. The RFU downloads bin files that were previously created using Dynamic C. Dynamic C starts with a source code file and compiles it down to the target. 3.1.5 Remote Debugging with Dynamic C Once a program is successfully downloaded to the target controller attached to the RabbitLink, Dynamic C may be used to debug the program as if the PC running Dynamic C was directly connected to the target. Refer to the Dynamic C User's Manual for detailed information on downloading and debugging.
3.1.6 Troubleshooting Tips. If Dynamic C is unable to establish communication with the RabbitLink, make sure that the RabbitLink is powered on, and make sure that the Ethernet cable is firmly connected to the RabbitLink and that the LED labeled LINK is on. If Dynamic C is still unable to establish communication with the RabbitLink, make sure that Dynamic C has the correct IP address and control port information. Look in the Communications dialog box. If Dynamic C is able to establish communication with the RabbitLink, but midway through the download process displays either ' Error receiving Flash ID from target'or ' Target Communication Error,' check to make sure that the program download cable is plugged in correctly from the RabbitLink to the controller being programmed, and that the controller is powered on. 3.2 RabbitLink Firmware The firmware necessary to operate the RabbitLink with a Rabbit-based target system is loaded at the factory.
This means that after the hardware connections have been made and the network parameters configured, the RabbitLink is ready to download a program to the local or remote Rabbit-based system. If it is necessary to reload or replace the firmware, the following.bin files are available for download from the RabbitLink directory that was created when Dynamic C installed. The.bin files are downloaded to the Rabbitlink using the RFU. The corresponding source files are in the same directory and may be used instead by compiling them to the RabbitLink using Dynamic C. CLEARPARAM.BIN-Binary image to reset the network configuration parameters of the RabbitLink board (stored on the second flash) to default values. This binary file is used to reset the serial port if its operation has become undefined.
DOWNLOAD.BIN-RabbitLink firmware binary image. The RabbitLink firmware version must be compatible with the version of Dynamic C that is used to download applications to the target that is connected to the RabbitLink (see ). The companion CD in the RabbitLink Tool Kit contains versions 1.00, 2.00 and 2.05 of the firmware. 3.2.1 Downloading Firmware to the RabbitLink Follow these steps to reload the firmware or to reset the RabbitLink serial port. Connect the RabbitLink board to your PC as shown in with the PROG connector on the programming cable connected to the PROG IN header of the RabbitLink board. Figure 3.2.1-1 RabbitLink Connections for Downloading Firmware. Use the RFU version 2.0 or later to load the DOWNLOAD.BIN firmware or the CLEARPARAM.BIN binary image onto the RabbitLink board.
Disconnect the programming cable. Unplug the power supply, then plug the power supply back in. This resets the RabbitLink from Program Mode to Run Mode. 3.2.2 Firmware Upgrades Follow the above steps to install a firmware upgrade. Just substitute the name of the firmware upgrade for the firmware binary image file ( DOWNLOAD.BIN ). Firmware upgrades will be available at or at 3.3 Serving Web Pages and Sending E-Mail The RabbitLink is intended for downloading and debugging across an Ethernet-based network with a Rabbit-based target. However, it is possible to use the RabbitLink to send e-mail and serve web pages from the Rabbit-based target.
This isn't recommended. Z-World offers DeviceMate as a better-fit solution for those who wish to use Internet services. 3.3.1 Using DeviceMate Features The DeviceMate feature set has many options, such as watchdogs and message logging, and also an interface that is easier to use than what is available on the RabbitLink.
Pod bot for cs 1.3. >![]('') > and paste the code at new line in addons/metamod/Plugins.ini Note: press [=] to open PODBot menu Tutorial of waypoint is avalible at index.html inside podbot pod_V3_docs folder or you can find [here]('') for custom maps Thanks for downloading ^_^ ==========================. >![]('') >Put the podbot folder in cstrike addons #### 2. ![]('') Before you download this, you must have at least [AMX Mod X 1.8.1 Full(include metamod)]('Click here to download') HOW TO INSTALL ================== #### 1. >![]('') > Copy this code below > win32 addons/podbot/podbot_mm.dll > or this for linux users > linux addons/podbot/podbot_mm.dll #### 3.
For more information about DeviceMate, please visit the Zworld website: The DeviceMate software may be downloaded to the RabbitLink to replace the RabbitLink firmware. 3.3.2 Using RabbitLink Features RabbitLink console commands may be used to send e-mail and serve web pages. A complete list of the available commands are in Prior to Dynamic C 7.20, a console API existed for target applications to send console commands to the RabbitLink. Please see for API function descriptions. Starting with Dynamic C 7.20, the console commands are sent to the RabbitLink through the serial port interface.
Z-World, Inc. Phone: 1.530.757.3737 Fax: 1.530.757.3792 Rabbit Semiconductor Phone: 1.530.757.8400 Fax: 1.530.757.8402.
Complete instructions are available by clicking on the Help button in the upper righthand corner of the program window. Context-sensitive help is accessed by positioning the cursor over the desired subject and then pressing. C.0.2.1 Add Files to Encrypt There are two ways to select files to encrypt.
Type the path and filename in the lower window. Click the Add Files to Encrypt button to bring up a file open dialog box and browse for the desired file. The list of files to be encrypted may be edited if desired. Notice that if anything is entered in the lower window, a new button named “Encrypt” appears.
Rabbit Field Utility 3.05
Two entries in the window change it to “Encrypt All”. Clicking this button causes the utility to encrypt the file(s) listed in the lower window. C.0.2.2 File Extension Encrypted files will be saved with the same pathname but with the extension supplied. Dynamic C will use encrypted and non-encrypted files seamlessly, so the choice of extension is for one’s own file management.
C.0.2.3 Optional Text Area The upper window is a text window of up to 4k bytes in length. Any text entered will appear in all files in the list appearing in the lower window. If two files are to be given unique headers, they should be encrypted separately. This area can be used for copyright information, instructions, disclaimers, warnings, or anything else relevant to viewers of the file.
C.0.3 File Compression Utility Dynamic C has a compression utility feature. The default utility implements an LZSS style compression algorithm.
Support libraries to decompress files achieve a throughput of 10 KB/s to 20 KB/s (number of bytes in uncompressed file/time to decompress entire file using ReadCompressedFile) depending upon file size and compression ratio. The compiler directive performs a standard #ximport, but compresses the file by invoking the compression utility before emitting the file to the target. Support libraries allow the compressed file to be decompressed on-the-fly. Compression ratios of 50% or more for text files can be achieved, thus freeing up valuable xmem space. The compression library is thread safe. For details on compression ratios, memory usage and performance, please see Technical Note 234, “File Compression (Using #zimport)” available on our website, at C.0.3.1 Using the File Compression Utility The utility is invoked by Dynamic C during compile time when #zimport is used.
The keyword #zimport will compress any file. Of course some files are already in a compressed format, for example jpeg files, so trying to compress them further is not useful and may even cause the resulting compressed file to be larger than the original file. (The original file is not modified by the compression utility nor by the support libraries.) The compression of FS2 files is a special case. Instead of using #zimport, #ximport is used along with the function CompressFile. Compressed files are decompressed on-the-fly using ReadCompressedFile. Compressed FS2 files may also be decompressed on-the-fly by using ReadCompressedFile.
In addition, an FS2 file may be decompressed into a new FS2 file by using DecompressFile. There are 3 sample programs to illustrate the use of file compression. Samples/zimport/zimport.c: demonstrates #zimport. Samples/zimport/zimportfs2.c: demonstrates file compression in combination with the file system. Samples/tcpip/http/zimport.c: demonstrates file compression support using the http server C.0.3.2 File Compression/Decompression API The file compression API consists of 7 functions, 3 of which are of prime importance: OpenInputCompressedFile - open a compressed file for reading or open an uncompressed #ximport file for compression. CloseInputCompressedFile - close input file and deallocate memory buffers.
ReadCompressedFile - perform on-the-fly decompression. The remaining 4 functions are included for compression support for FS2 files: OpenOutputCompressedFile - open FS2 file for use with CompressFile. CloseOutputCompressedFile - close file and deallocate memory buffers. CompressFile - compress an FS2 file, placing the result in a second FS2 file.
DecompressFile - decompress an FS2 file, placing the result in a second FS2 file. Complete descriptions are available for these functions in the Dynamic C Function Reference Manual and also via the Function Lookup facility (Ctrl+H or Help menu). There are several macros associated with the file compression utility:. ZIMPORTMASK - Used to determine if the imported file is compressed ( #zimport) or not ( #ximport). OUTPUTCOMPRESSIONBUFFERS (default = 0) - Number of 24K buffers for compression (compression also requires a 4K input buffer, which is allocated automatically for each output buffer that is defined). INPUTCOMPRESSIONBUFFERS (default = 1) Number of 4KB internal buffers (in RAM) used for decompression.
Each compressed file has an associated file descriptor of type ZFILE. All fields in this structure are used internally and must not be changed by an application program.
C.0.3.3 Replacing the File Compression Utility Users can use their own compression utility, replacing the one provided. If the provided compression utility is replaced, the following support libraries will also need to be replaced: zimport.lib, lzss.lib and bitio.lib. They are located in lib. The default compression utility, Zcompress.exe, is located in Dynamic C’s root directory. The utility name is defined by a key in the current project file: Compression Utility Zimport External Utility=Zcompress.exe To replace Zcompress.exe as the utility used by Dynamic C for compression, open your project file and edit the filename. The compression utility must reside in the same directory as the Dynamic C compiler executable. Dynamic C expects the program to behave as follows:.
Take as input a file name relative to the Dynamic C installation directory or a fully qualified path. Produce an output file of the same name as the input file with the extension.DCZ at the end. E.g., test.txt becomes test.txt.dcz.
Exit with zero on success, non-zero on failure. If the utility does not meet these criteria, or does not exist, a compile-time error will be generated. C.0.4 Font and Bitmap Converter Utility The Font and Bitmap Converter converts Windows fonts and monochrome bitmaps to a library file format compatible with Rabbit’s Dynamic C applications and graphical displays. Non-Roman characters may also be converted by applying the monochrome bitmap converter to their bitmaps. Double-click on the fmbcnvtr.exe file in the Utilities folder where you installed Dynamic C. Select and convert existing fonts or bitmaps.
Complete instructions are available by clicking on the Help button within the utility. When complete, the converted file is displayed in the editing window.
Editing may be done, but probably won’t be necessary. Save the file as nameme.lib: the name of your choice. Add the file to applications with the statement: #use nameme.lib // remember to add this filename to “lib.dir” file or by cut and pasting from nameme.lib directly into the application file.
C.0.5 Rabbit Field Utility Module The Rabbit Field Utility (RFU) will load a binary file created with Dynamic C to a Rabbit-based board. The RFU can be used to load a binary file without Dynamic C present on the host computer, and without recompiling the program each time it is loaded to a controller. The Dynamic C installation created a desktop icon for the RFU. The executable file, rfu.exe, can be found in the subdirectory named “Utilities” where Dynamic C was installed. Complete instructions are available by clicking on the Help button within the utility.
The Help document details setup information, the file menu options and BIOS requirements. The RFU executable that comes with the Dynamic C distribution is branded as a product, as seen in the “About” screenshot shown here.
You can brand the RFU or customize its functionality to suit your needs. Please contact technical support for the source file needed for customization: The RFU enables those without Dynamic C to update their Rabbit-based board with a few files installed on the computer and the appropriate connection to the target board. The necessary files are included with Dynamic C.
They are: the executable ( Rfu.exe), the cold loader, the pilot BIOS, and a couple of files used to determine information about the memory device being used. The default files used for the cold loader, etc., can be seen by selecting “File Locations.” from the Setup menu. We strongly recommend that the default files be used. They are needed internally by the RFU and improper operation of the utility will result if a replacement file does not contain the expected code or information.
Rfu.exe and its ancillary files are freely distributable. The RFU communicates with the target using a serial connection. This connection requires a programming cable. C.0.5.1 Command Line RFU There is also a command line version of the RFU. On the command line specify: clRFU SourceFilePathName options where SourceFilePathName is the path name of the.bin file to load to the connected target. The options are as follows: -s port:baudrate.