|
QuickFIRE support questions
If you have problems when using the QuickFIRE check the following:
- Is power applied correctly?.
- Are the Power Supply links fitted correctly i.e. if Power Supply is 3V LK2 & LK3 North, if Power Supply is 5V LK2 & LK3 South
- Is your PC connected to the correct serial port on the QuickFIRE. The QuickFIRE defaults to PL6 or TERM for communication with a P.C.
- Have you selected to correct COM port on your PC (if applicable)?. Is the Module/Serial port connected to the selected COM port?. Check that you are running a suitable terminal program using the correct serial port parameters (38400,8,1,n by default).
- Turn the power off and move the battery backup link (LK5 on QF-200) West, refit the link East again. This will clear the contents of the battery backed RAM. On very rare occasions this can become corrupted and prevent the controller starting up properly.
- If the Module is able to transmit data but not receive, check that you have not installed a SERIAL mouse on the same COM port as you are using for the Module. If you have installed a serial mouse either use a different COM port or comment out the relevant lines and reset the PC. Serial mouse drivers often disable the transmitter in the PC serial port.
- Try using Hyper Terminal or Windows Terminal. These packages do not require the CTS/RTS hand shaking. If the Module works in these and not the supplied terminal, check your serial cables to ensure that the hand shaking lines are connected.
- If you still can not communicate with the Module, try a another P.C.
- Make sure that the Bootstrap mode is not enabled. If switch SW2 bank C is on the controller will enter bootstrap mode from power on. In this mode the usual power up routines are disabled. Please refer to your documentation for full details.
- If the LEDs on the controller are not illuminating check that the LEDs are enabled using switch SW2 bank A. If this switch is in the OFF position the LEDs are disabled to reduce the current consumption of the controller card.
If the QuickFIRE still does not respond correctly, write a full description of the fault, any error messages, etc. and fax it to Technical support or email support@cms.uk.com.
Bootstrap Loader.
The QuickFIRE controller has a built in bootstrap loader and we provide a basic operating system and a bootstrap loader program on the shipping CD. This can allow the board to recover from a catastrophic failure resulting in corruption of the Flash memory. To enter the Bootstrap mode set the Mode switch SW2 bank C to ON and enable the LEDs by setting bank A to ON. Connect the terminal serial port PL4 to the PC. On the PC run a terminal program which allows raw text downloads (such as Hyper Terminal or Teraterm). Set the communication parameters to 19200, 8, n, 1 with no hand shaking. Either reset or turn on the controller. Hit a key on the PC and the terminal should echo the character '@'. This indicates that the processor is in bootstrap mode - any additional characters will be echoed correctly. Next download the basic operating system 'DEFAULT.B' as a raw text file. How you do this depends on your terminal. This will take a few minutes to complete. When this transfer is complete download the file 'BOOTSTRAP.TXT'. This is a program which will copy the code downloaded into the Flash memory. The first thing that the program will do is check that the operating system file has downloaded correctly. If everything is OK the LED D4 will light up and stay on. If there is an error the LED will flash and the process should be repeated. Assuming that everything is OK after about 2 minutes the LED should start to flash. This indicates that the data has been programmed correctly. Turn the power off and return the Mode switch SW2 bank C to the OFF position to enable the processor to start up normally next time power is applied. This process puts a basic image into the flash which allows the 'upminos' utility program to be used to load in your full image file. The reason that only a small image file is used is for speed. The bootstrap file format requires large numbers of additional characters and the transfer only occurs at 19200 baud. It is much quicker to do this process in two stages. It also allows the customer to use their own EPROM image without having to go through the process of creating a bootstrap image from their own application.
If you feel that the product is faulty please download and complete a Returns Application form before returning the product for repair.
Although Cambridge Microprocessor Systems Ltd is committed to supplying its customers with a standard well tested product, errors and bugs can always be found in even the most widely used software packages. If you find any errors or bugs please let us know by sending an email to support@cms.uk.com. All reported errors will receive a response from one of our engineers.
|
Support
