AND9807. AP0300 Demo System User Guide APPLICATION NOTE

Transcription

1 AP0300 Demo System User Guide General AP0300 Description ON Semiconductor AP0300AT Image Signal Processor (ISP) is optimized for use with HDR (High Dynamic Range) sensors. The AP0300AT provides full auto functions support to enhance HDR images and advanced noise reduction which enables excellent low light performance. AP0300 Description Demo system User Guide This document describes how to use the AP0300 demo system, upgrade the firmware on that system on flash, and how to use it with DevWare. This document covers basic AP0300 demo board configuration, currently supported use cases, required HW (Hardware), required FW (Firmware) and SW (Software). Notes are added regarding known issues and limitations. This document does not cover customer FW development for the HIP or DSP Introduction The AP0300 demo board ( AP0300_VFGA169_DEMO3HEAD_REV0 ) connects to the demo3 board to allow I2C control of the AP0300 and transfer of image data via the demo3 USB3 driver. The AP0300 demo board also connects to a sensor demo board to allow I2C control of the sensor by the AP0300, and to transfer image data from the sensor to the AP0300. These two I2C busses and image transfer busses are separate so that the demo3 cannot directly access the sensor. The AP0300 is an ISP in which the control FW is not fixed in an internal ROM. The FW can be modified by programming an attached flash memory, or downloaded via I2C. The AP0300 demo board contains this flash onboard, and it can be programmed in circuit by the supporting FW in the AP0300, via the I2C interface and demo3 board. To accommodate this choice of FW source (flash or I2C), an input to the AP0300 selects the desired boot source. A boot ROM in the AP0300 checks this boot_sel input and runs the FW accordingly. On the AP0300 demo board, an I2C I/O expander controls the boot_sel input to the AP0300. Due to the market requirements, the architecture of the AP0300 provides just a few HW registers on the I2C interface with the demo3. These are for part identification (chip ID, rev), a command register, and a command parameters buffer. There is no direct access to I/O or imaging system HW resources via the I2C interface with the demo3. Without the FW loaded, the only functions available via the I2C interface are to download FW to run, or to download FW to be programmed into the attached flash memory. APPLICATION NOTE The jumper positions are listed here in left to right, top to bottom order in the board layout. AP0300 Demo Hardware The AP0300 demo board provides a MIPI image data interface, 4 lanes, between the AP0300 and sensor. For image data output, the board provides both a parallel interface and 4 lane MIPI interface. Note that the parallel interface maximum speed is 100 MHz, limited by the demo3 parallel receive port. Note: At this early stage, we are only supporting the AR0231 Rev7 and AR0147 Rev1. The current configuration uses MIPI in from the sensor, and MIPI out of the AP0300. Also, this document is only describing usage with flash to begin streaming. The AP0300 demo system hardware consists of: Demo3 board AP0300 Demo board (AP0300_VFGA169_DEMO3HEAD_REV0) AR0231 rev7 sensor board (AR0231_iBGA121_DEMO3HEAD_REV0) or AR0147 rev1 sensor board (AR0147T_iBGA80_DEMO3HEAD_REV0) AP0300 Board Configuration and Jumper Settings Configure the AP0300 demo board jumpers as follows. Consult the schematic of AP0300_VFBGA169_DEMO3HEAD.pdf as needed. Contact Applications Engineering for a copy if desired. The jumper positions are listed here in left to right, top to bottom order in the board layout. Semiconductor Components Industries, LLC, 2018 October, 2018 Rev. 0 1 Publication Order Number: AND9807/D

2 Table 1. AP03000 DEMO BOARD JUMPER IN LAYOUT ORDER Designator Config (Optional/Required) Functional selection Schematic Page P11 installed (Optional) power the LED to indicate board power 4 P (Required) to select on board flash for FW instead of socket at J2 5 P39 removed (Required) secondary I2C master port test points/connections 3 P (Required) selects sensor connector pin for trigger signal, depends on sensor board, 1 2 for AR0231, AR P2 removed (Required) connects second sensor trigger signal to AP P1 removed (Required) connects primary sensor trigger signal to AP P (Optional) connects GPIO1 to UART for HIP diagnostic output 5 P (Required) connects primary sensor trigger to AP P19 installed (Required) connects AP0300 SPI data to flash 5 P4 2 3 (Required) Disables JTAG/Boundary scan port. Set to 1 2 to allow JTAG debug of CPUs (requires powered JTAG pod to be connected) 3 P5 removed (Required) boot select, boot mode controlled by I/O expander, jumper override does not work on rev0 board 3 P (Optional) connects GPIO0 to UART for BSP diagnostic output 5 P I2C address for I/O expander U21 (drives boot_sel), AD0_1 low, AD0_2 high 7 P (Optional) connects GPIO2 to UART for ICP diagnostic output 5 P (Optional) connects GPIO3 to UART for DSP diagnostic output 5 P32 installed (Required) disable Beagle connector (P27) level shifters for I2C to AP P (Optional) Select 5 V power from demo3 connector (USB), 2 3 selects external 5 V supply. This only supplies core 0.9 V regulator, demo3 connector supplies still required for other voltages 4 P (Optional) I2C address for EEPROM U17, AD1 low, AD2 high, currently not used. This is on the demo3 I2C bus 6 P21 removed (Required) Enables I2C level shifters for I/O expander U21, required to configure drive for AP0300 boot_sel input 7 P (Required) Sensor reset signal sourced from AP P29 installed (Required) disable demo3/beagle I2C level shifter to sensor (sensor I2C from AP0300) 7 P (Optional) select 3.3 V for Host VDDIO, required for UART diagnostic output 4 P (Required) select clock input 5 P17 removed (Required) disconnects crystal driver from AP P3 2 3 (Optional) connect AP0300 frame_sync input to ground, 1 2 selects input from demo3 3 P (Required) I2C address for I/O expander U24, AD1_1 high, AD1_2 low. Make sure this address selection does not conflict with U21 address selection on P31 7 P38 removed (Required) enables demo3 I2C level shifter to I/O expander U24 7 P24 1 2, 3 4 (Required) connects demo3 I2C to board I2C bus 6 P (Optional) select 3.3 V for VDDIO GPIO P (Optional) select 3.3 V for GPIO 0 9 VDDIO, required if using UART diagnostic output 4 P (Optional) select on board 27 MHz oscillator for AP0300 clock, select 2 3 for clock from demo3, maximum clock is 30 MHz 5 2

3 Figure 1. AP0300 Jumper Settings. The Items Noted Are Most Likely Jumper Changes From Board Delivery 3

4 Sensor Board Configuration This section describes specific sensor board configuration jumpers required to work with the AP0300 demo board compared to directly connected to a demo3. Other typical sensor demo board jumpers, like test modes and GPIOs, are not described here. Supported sensors are covered individually and are added as supported. AR0231 Sensor Board Configuration The AP0300 FW currently only supports AR0231 rev7 sensors. Other revisions of the sensor are rejected. Three items require correct configuration to work with the AP0300 demo board: the sensor s input clock source, the sensor s slave I2C device address, and the supply to the MIPI D PHY. The following are specific to the AR0231_iBGA121_DEMO3HEAD_REV0 board. Consult the schematic at ar0231_ibga_demo3head_rev0.pdf. (Contact the AE for a copy). P42, P48, P49 installed to configure I2C slave device address to 0x20. P19, 2 3 select input clock from demo3 connector, which is driven by the AP0300 demo board. P46, 2 3 select 1.2 V for MIPI serial interface Connect the demo3 board to the AP0300 demo board J1 connector block. This is on the board side with all of the configuration jumpers. Connect the bit shift board and/or the sensor board to the AP0300 demo board P6, on the opposite side from the demo3. If the AP0300 demo board has a socket for the AP0300 chip, then an extender is needed for the sensor board to clear the socket. The bit shift board can be used for this since only the MIPI image signals will be used (the bit shifting is for the sensor parallel output). See Figure 2. AR0147 sensor Board Configuration The AP0300 FW currently only supports AR0147 rev1 sensors. Other revisions of the sensor are rejected. Three items require correct configuration to work with the AP0300 demo board: the sensor s input clock source, the sensor s slave I2C device address, and the supply to the MIPI D PHY. The following are specific to the AR0147T_iBGA80_DEMO3HEAD_REV0 board. Consult the schematic at AR0147_IBGA80_DEMO3HEAD.pdf. (Contact AE for copy) P1, P4, and P5 installed to configure I2C slave device address to 0x20. P16, 1 2 select 1.8V I/O P18, 1 2 select 1.2V for MIPI serial interface P19, 3 5 select input clock from demo3 connector, which is driven by the AP0300 demo board. P24, 1 2 and 3 4 to connect I2C signals with the AP0300 board 4

5 Figure 2. AP03000 Demo System Board Stack AP0300 Demo System Software The AP0300 demo system software consists of DevWare or later Python AP0300 FW Demo release package AP0300_Dev_Kit_LICENSE_(Read Me_File)_ pdf AP0300 Devkit READ ME license devware directory AP0300AT FWUPDATE REV1.xsdat to be loaded to DevWare for the firmware upgrade AP0300AT FWUPDATE REV1.ini INI file that pairs with the corresponding XSDAT file and contains firmware upgrade presets scripts directory 5

6 A set of scripts that are used in the firmware upgrade process and to convert elf/cif/coff files into I2C blob and Flash images for f/w upgrade build_code_image.py build_dsp_image.py build_flash_image.py build_fw_upgrade_images_ex.py build_i2c_blob_app.py fw_update.py firmware directory Contains pre packaged AP0300 f/w images for various processors. These firmware binaries are meant to be used for demo and evaluation purposes, and to explore the firmware upgrade process bl2.cif BSP second stage bootloader in CIF format, needed to rebuild Flash image bl2.blob.chip.bin BSP 2 nd stage bootloader blob to be used for loading the firmware to RAM bl2.build.props stage bootloader buld properties for traceability boot_config_table.chip.bin boot confirmation table to be used in building Flash image cert_store.bin certificate store config to be used in building Flash image hip_ccapp.cif HIP Camera Control Application in CIF format. This application implement Camera Control Interface over I2C and enables demo interface to DevWare hip_ccapp.build.props HIP Camera Control App build properties icp.cif ICP processor firmware in CIF format icp.build.props ICP firmware build properties for traceability FW Upgrade Procedure and Running AP0300 from Flash Firmware can be updated as new releases become available. AP0300 demo boards would typically be delivered with no programming in the attached flash memory. FW needs to be updated with new releases. There are two ways to load the new firmware into the AP0300. The recommended method is to program the flash memory with a new release of the firmware. After this, a board reset, configured to boot from flash, will start running the FW immediately. The alternative to load the FW is to download it via I2C and the demo3. This is faster than programming the flash memory, but must be repeated if the board is reset or powered off. AP0300 with Devware requires Python. If you have an older version, less than 3.5.x, uninstalls this version and install a newer version. If Python is uninstalled, Devware should prompt the user to install a new version. For either download method, start DevWare and point it to AP0300AT FWUPDATE REV1.xsdat. At this point, DevWare will automatically load the matching INI. Open the Python console in DevWare s View menu to see progress messages while FW load operations execute. After either of the following procedures, you can open AP0300AT REV1.xsdat using DevWare s File Open Sensor Data File. DevWare will automatically load the matching INI. Once the AP0300AT REV1.ini is loaded, in the Registers dialog, select the FW Version Info variable page for display. Check the version information for each processor, especially the *_BUILD_NO values, against the values given in the Release_Notes.html Scope section. First, Start Devware. In this example, External version This will normally comeup, but push No 6

7 Then, Select option to pick sensor data file Select this one only when programming the flash Then, unselect all options and finish 7

8 AND9807 When this completes, the AP0300 will be configured to boot from flash memory and then reset. This will load and run the newly programmed FW. This takes about 2 minutes 10 seconds. The process is completed when the last line in the Python console Rebooting with new flash programs This is the window which should now be seen. Note that the chip_id is visible in the registers window and Comm: working is in green showing i2c communication is working. Open the Python console from the `View > Python console drop down options. Flash programming progress can be monitored in this way. Run the Python: Program FW to Flash preset by double clicking. Then, the Flash programming will commence and continue normally as shown below. 8

9 At this point, all that is needed is to load the AP0300AT REV1.xsdat XSDAT file to begin streaming. From File > Open Sensor file, select the default XSDAT. The XSDAT file name is AP0300AT FWUPDATE REV1 NDA.xsdat. AND9807 Or, to start Devware from the beginning after a system reset, follow the procedure outlined below in Operation with Devware Streaming from Flash with DevWare Run DevWare and point it to AP0300AT REV1.xsdat in the Startup Choices dialog. DevWare will automatically load the matching INI. Do not use DevWare s Probe for devices function. If not continuing from a FW update function described above, then the AP0300 must be configured to boot from flash and reset. Run the [Python: Reset boot from Flash] section. Step by step here: Pick the option to select sensor as before This time, select this xsdat for normal streaming operation Start Devware again after doing a full hardware restart Unselect option and finish 9

10 Pull up the Presets menu and select and run these in this order: 1. Python: Reset boot from Flash 2. Demo Initialization Streaming image should be seen at this point as below. 10

11 Option to Download FW to RAM This procedure will download the firmware into the AP0300 RAM using I2C. Run the INI section [Python: Download FW to RAM]. The AP0300 is configured to boot from I2C and reset. Then the FW is downloaded over I2C. When this completes, the AP0300 will be running the newly loaded FW. This takes about 20 seconds. The AP0300 remains configured to boot from I2C. Procedure to run AP0300 by loading FW to RAM This procedure will download the firmware into the AP0300 RAM using I2C. 1. Start Devware as before 2. Select the FWUPDATE XSDAT 3. Select Python Demo Download FW to RAM and wait for completion by watching the Python window 4. Go to File > open sensor data file and select AP0300AT REV1 NDA.xsdat 5. Run Demo Initialization and streaming should begin NOTE: To change the AP0300 configuration, after editing the registers/variables in the register dialog or with INI sections, execute the [CHANGE CONFIG] section.the variable pages with names that start with IQ have three types: INIT, CONFIG, and INFO. INIT values take effect during a change config. CONFIG values take effect during a change config or during a refresh (by executing the [Refresh] section). The INFO values are read only and reflect the current states and values of a variety of IQ functions. Known Issues AP0300 demo board boot_sel jumper (P5) does not work on rev0 boards. The I/O expander on the board must be configured to drive this signal into the AP0300. The INI files have sections to configure the I/O expander for either boot from flash or boot from INI, and then to reset and boot from flash or INI. The demo3 parallel port maximum speed is 100 MHz. This limits the maximum frame rate that can be handled by the demo3 parallel input to about fps with a 1928x1208 image. The demo3 MIPI receiver maximum speed is 400 MHz, with 4 data lanes, resulting in a peak of 3.2 Gbit/s (double data rate, so 800 Mbit/s each lane). PLL0 configuration is not supported. This PLL generates the clocks to the CPUs and is fixed at 240 MHz. Support for configuration will be added at a later time. Firmware Developers and Specials Users For FW developer use (and other special users) there is also a firmware subdirectory in the release package with FW executables for each processor. These can then be downloaded to the AP0300 or programmed into the flash. A developer can either replace F/W executables with their copy or use f/w upgrade INI presets to point the custom HIP and DSP firmware executables. Using DevWare with the SDK NOTE: if you are building the DSP SDK on Linux, but running DevWare on Windows, you will need to install the Windows CEVA toolchain, and ensure the toolchain binaries are in your system path before proceeding. See <dsp_sdk_install_path>\doc\readme.txt for additional details. 1. Install an optional Python package by opening a cmd window and running pip install numpy 2. Build the HIP SDK s bp_quick_start project; the resulting.axf file will be located in bp_quick_start/output/debug 3. Build the DSP SDK s bp_examples project; the resulting.a file will be located in bp_examples/output/debug 4. Execute the Python: Custom set HIP firmware image source preset, navigate to the directory containing the HIP.axf file built in step 1, select the axf file, and then click Open 5. Execute the Python: Custom set DSP firmware image source preset, navigate to the directory containing the DSP.a file built in step 2, select the.a file, and then click Open 6. Execute the Python: Custom Download FW with DSP to RAM preset; this will reset the part and then download and execute the selected HIP and DSP firmware images 7. The same images can be burned to flash by executing the Python: Custom Program FW to Flash preset If the HIP and/or DSP SDK projects are subsequently modified and rebuilt, the new build results will automatically be used the next time a Python: Custom Download FW with DSP to RAM or Python: Custom Program FW to Flash preset is executed. 11

12 ON Semiconductor and are trademarks of Semiconductor Components Industries, LLC dba ON Semiconductor or its subsidiaries in the United States and/or other countries. ON Semiconductor owns the rights to a number of patents, trademarks, copyrights, trade secrets, and other intellectual property. A listing of ON Semiconductor s product/patent coverage may be accessed at /site/pdf/patent Marking.pdf. ON Semiconductor reserves the right to make changes without further notice to any products herein. ON Semiconductor makes no warranty, representation or guarantee regarding the suitability of its products for any particular purpose, nor does ON Semiconductor assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation special, consequential or incidental damages. Buyer is responsible for its products and applications using ON Semiconductor products, including compliance with all laws, regulations and safety requirements or standards, regardless of any support or applications information provided by ON Semiconductor. Typical parameters which may be provided in ON Semiconductor data sheets and/or specifications can and do vary in different applications and actual performance may vary over time. All operating parameters, including Typicals must be validated for each customer application by customer s technical experts. ON Semiconductor does not convey any license under its patent rights nor the rights of others. ON Semiconductor products are not designed, intended, or authorized for use as a critical component in life support systems or any FDA Class 3 medical devices or medical devices with a same or similar classification in a foreign jurisdiction or any devices intended for implantation in the human body. Should Buyer purchase or use ON Semiconductor products for any such unintended or unauthorized application, Buyer shall indemnify and hold ON Semiconductor and its officers, employees, subsidiaries, affiliates, and distributors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that ON Semiconductor was negligent regarding the design or manufacture of the part. ON Semiconductor is an Equal Opportunity/Affirmative Action Employer. This literature is subject to all applicable copyright laws and is not for resale in any manner. PUBLICATION ORDERING INFORMATION LITERATURE FULFILLMENT: Literature Distribution Center for ON Semiconductor E. 32nd Pkwy, Aurora, Colorado USA Phone: or Toll Free USA/Canada Fax: or Toll Free USA/Canada orderlit@onsemi.com N. American Technical Support: Toll Free USA/Canada Europe, Middle East and Africa Technical Support: Phone: ON Semiconductor Website: Order Literature: For additional information, please contact your local Sales Representative AND9807/D