*
*Home|Chinese|Japanese*About ARM|Forums|Events|News|Employment|Contact Us|Investors*
dotted rule
*ARM - the architecture for the digital worldARM - the architecture for the digital world
search
*
*
***
*MARKETS:PRODUCTS & SOLUTIONS:CONNECTED COMMUNITY:TECHNICAL SUPPORT:DOCUMENTATION*
*
technical support
*Home > Technical Support > FAQs > Development Tool FAQs > Development Boards Fault Report Form
*
****
*.Technical Support
*
*
*>>Home Page*
*
*.Obtaining Support*
*
*.FAQs*
*
**Development Tool FAQs*
**IP FAQs*
**Embedded Software FAQs*
**Artisan Physical IP FAQs (Login Required)*
*
*.Downloads*
*
*.Documentation*
*
*.Training*
*
*.Where To Buy*
*
*.Keil MCU Tools*
*
*.What's New*
*
*.ARM Newsgroups*
*
*.Active Assist On-site Services*
*
*
*
technical support FAQsask ARM*
*

Technical Support Search
*     (Advanced Search)
  FAQs   Documentation   Downloads   Forums

*

 
downarrowDevelopment Boards Fault Report Form


Important Note 1: This form is for customers who have purchased tools directly from ARM. If your tools were purchased from a distributor, please contact your supplier.

Important Note 2: Please submit one fault report form per development system in English.

Important Note 3: During the fault investigation process it may become necessary to remove components to identify the reported fault. As a result, ARM cannot guarantee that the RMA will be returned in the same condition as when the fault was reported, should the fault not be able to be identified and remedied or the product be deemed Beyond Economic Repair.

* Indicates a required field.

Support case number (if known) : 

Details of end user reporting fault

* Name :
* Company :
Telephone :
* Email :
* Confirm Email :
* Address :
Building/Division:
* Country :
* Postal/Zip Code :
Return Address (if different) :

Details of faulty development system components

Please list all components of your development system including the serial number, board (PCB) part number/version and FPGA/PLD versions for each board.

All ARM baseboards have a boot monitor that should display the version information. Please refer to your board's user guide for details of using the boot monitor. The boot monitor will output information from a serial port and can be viewed by a terminal application. The Versatile PB926EJ-S and the Emulation Baseboard (EB) also show the bootmonitor version on the character LCD display after power-up. If you cannot find out the version information from either of these methods, there are also labels on the devices themselves.

Boot monitor version :Examples :
FPGA/PLD version :rev b build 37
Board version :HBI-0048D
Serial number :5032900 or 0132730101-0049


* Component :* Serial number:Board version:FPGA/PLD version:
Other:  
Other:  

Tool version details

To be able to investigate your inquiry as quickly as possible it is necessary to know the full system you are using with the ARM development Boards. Please select the software versions that you are using from the pull down boxes below.

Before you select the appropriate tool versions below have you tried our latest patches? (see links below)

IntegratorMulti-ICEProgcardsRealView ICE (RVI)Versatile

Multi-ICE :

RVI host software :

RVI firmware :


progcards_multiice :

progcards_usb :

progcards_rvi :

Note: progcards_multiice.exe was previously named progcards.exe.

Other comments about tool versions:


Description of fault

* Please describe the symptoms of the fault in as much detail as possible, for example:

'Cannot run boot monitor on my Integrator system. I have set DIP switches S1[1] and S1[4] on the AP board to ON. The 'MISC' LED on core module does not light. 'FPGA_OK' LED on logic module does not light...'



Which DIP switches and jumpers do you have set on your boards?



Please list which LEDs are lit on each board in your system: (e.g., FPGA_OK / GLOBAL_DONE / LOCAL_DONE / DONE / MISC / FPGA_IMAGE)



Are you using any of our application notes? If so, please can you list which ones below:



Please describe what happens when you try to reprogram the FPGA configuration flash using our progcards utility (if possible, to aid our diagnosis, please also paste the text from the progcards output).



* Was the board 'Dead On Arrival' (DOA)? Yes No

If the board was not DOA then what activity were you performing with the development system before it failed? For example:

'We have been developing a custom USB controller in the Logic Tile, and the boards were working OK until we loaded a new USB controller design into the Logic Tile FPGA yesterday...'



Additional information:



* Can you accept a replacement or do you require your original part?

 Replacement
 Original Part

* The more information you provide, the easier it will be for us to diagnose what may be wrong with your faulty board. Please tick the box on the left to confirm that you believe the above information to be accurate and complete. 





back to top

*
**
*4 dots*Other ARM Websites
*
shadow *LEGAL STATEMENTshadow