Sharp KEVLH7A400 v0.3b
Welcome to the SHARP KEV7A400 Evaluation board beta starter kit.
This document contains last minute updates to the kit and/or
documentation that were not available at the kit development time.
----------------------------------------------------------------------
- Getting started
----------------------------------------------------------------------
Before starting, it might be a good idea to copy the files from the
CDROM onto your local computer. This makes it easier to run and change
the supplied code. If possible, the structure of the files should not
be changed. The examples and code included on the CDROM are based on
this structure.
If the Flash on the board needs to be reprogrammed, several files on
the CDROM need to be copied to the users' tool area. These files are
used with the ARM ADS v1.2 (evaluation) tools included with the EVB.
The following files need to be moved to the bin directory of where
the ARM ADS tools are installed:
* UTILS/ARM multi ICE/flash.li
* KEV7A400/Config/ARM AXD Flash scripts/KEV7A400.oby
The following files need to be moved to the Arm Multi-ICE directory
* KEV7A400/Config/ARM multi ICE/ARM920T.cfg
----------------------------------------------------------------------
- CDROM organization and layout
----------------------------------------------------------------------
----------------------------------------------------------------------
- EVB external SRAM memory width
----------------------------------------------------------------------
A problem exists with the LH7A400 where operations to external SRAM
may cause data corruption when performing combinations of 16 and
32-bit data accesses. Because of this problem, the external SRAM
interfaces are configured for 16 bit accesses on the EVB. (FLASH,
external SRAM, ethernet, and the CPLD are all 16 bit interfaces).
External SRAM can be configured and used at 32 bits, but care must
be taken to avoid some operations that can cause the data corruption
problem. The EVB User's Guide explains how to change the data width
of the external SRAM interface on the EVB. The problem is explained
in the LH7A400 errata sheet and is fixed in later chip revisions.
(The EVB is shipped configured in the 16 bit data width configuration
for external SRAM.)
The boot code, applications, and code examples do not use external
SRAM.
----------------------------------------------------------------------
- Important information about reprogramming FLASH
----------------------------------------------------------------------
When booting from corrupted FLASH or SRAM, the SOC may execute an
illegal instruction and may be placed into a state where the JTAG
controller cannot obtain control of the SOC.
The following EVB FLASH reprogramming sequence has been verified to
work when the FLASH has been corrupted or does not contain bootable
code. This sequence assumes the ARM Multi-ICE JTAG controller is used
to repgoram FLASH.
1. Set the boot mode selection switch (SW7) to position 3. Power on
the EVB. Open jumper JP36. Remove any jumpers on JP41 and JP42.
Set JP34 open and JP35 closed.
2. Start the Multi-ICE server software and load the ARM920T.CFG
configuration file.
3. Start the AXD debugger. Depending on what happens with AXD,
follow the procedures outlined below.
a4. If the message "Target processor would not enter debug state when
DBGRQ was asserted" appears, press the WAKEUP button (SW6) on the
EVB and then press 'Yes' on the dialog box. The AXD debugger
should now connect to the JTAG controller/EVB.
b4. If the message "RDI severe error" appears, press the WAKEUP
button (SW6) on the EVB and then press 'Restart' on the dialog
box. The AXD debugger should now connect to the JTAG
controller/EVB.
c4. In some cases, the debugger will connect to the JTAG
controller/EVB without any problems.
5. From the System Views menu in AXD, select the Command Line
Interface menu item.
6. In the window that appears, type 'obey c:KEV7A400.oby'. This
command assumes the file is located in the bin directory of
the ARM tools. If the file is located elsewhere, the entire path
needs to be supplied.
7. From the System Views menu, select the 'Debugger Internals'
menu item. In the window that appears, change the $top_of_memory
value to 0x00200000.
8. From the File menu, select Flash Download. Press the '...'
button next to the image to load text box.
9. In the file dialog box that appears, locate the binary file that
is to be loaded into FLASH. (If the original bootcode is being
replaced, this would be Simple startup demo.bin in the
Board applications/Simple Startup Demo/ directory).
Press Open to select the file. Press OK to start the FLASH
download process.
10. The ARM console window will pop up. At the base address prompt,
enter 0x10000000 and press return.
11. At the starting sector prompt, press return (to accept the
default value of 0x0).
12. Once the download has completed, a message box will pop up
indicating a successful process.
13. Power off the EVB and return the boot mode selection switch
(SW7) to position 1. Return Jumper JP36 to closed. Return the
original states of jumpers JP41, JP42, JP34, and JP35.
The EVB is shipped with the FLASH protected to prevent accidental
corruption due to software problems. Jumpers JP34 and JP35 control
the FLASH write protection.
----------------------------------------------------------------------
- CDROM notes
----------------------------------------------------------------------
Organization of the Software directory is slightly different than
stated in the beta EVB User's Guide.
----------------------------------------------------------------------
- Documentation errata
----------------------------------------------------------------------
我要上传