文件列表:

MJPEG_encode\Include\SDK-cycle_count.h (1366, 2006-07-05)
MJPEG_encode\Include\SDK-ezkitutilities.h (3828, 2007-04-04)
MJPEG_encode\Include\adi_itu656.h (13398, 2006-07-06)
MJPEG_encode\Include\adi_usbcmd.h (4569, 2006-11-08)
MJPEG_encode\Include\adi_usbio_blackfin.h (3040, 2006-11-09)
MJPEG_encode\Include\JPEG-MJPEG\IMG_common.h (3513, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\JPEG_Struct.h (1720, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\JPEG_UserTypedefs.h (5891, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\JPEG_api_common.h (5259, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\JPEG_api_decoder.h (2013, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\JPEG_api_encoder.h (2029, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\JPEG_bitsbuffer.h (3549, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\JPEG_memalloc.h (1805, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\MJPEG_AVI_Common.h (5857, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\MJPEG_AVI_FileReader.h (2247, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\MJPEG_AVI_FileReader_exp_header.h (2035, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\MJPEG_AVI_FileWriter.h (2101, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\MJPEG_AVI_FileWriter_exp_header.h (2187, 2006-07-17)
MJPEG_encode\Include\JPEG-MJPEG\jpeg_mjpeg_cache.h (2177, 2006-11-10)
MJPEG_encode\Include\JPEG-MJPEG\jpeg_mjpeg_err.h (1662, 2006-07-21)
MJPEG_encode\Include\JPEG-MJPEG\si_errata.h (2501, 2006-07-17)
MJPEG_encode\BFinUtils\adi_itu656.c (29529, 2006-07-06)
MJPEG_encode\BFinUtils\adi_ssl_Init.c (20097, 2007-04-02)
MJPEG_encode\BFinUtils\adi_usbio.c (20867, 2006-11-09)
MJPEG_encode\BFinUtils\SDK-ezkitutilities.c (26157, 2007-09-13)
MJPEG_encode\BFinUtils\JPEG-MJPEG\JPEG-MJPEG_UserAccess_BF533.dpj (9166, 2006-11-03)
MJPEG_encode\BFinUtils\JPEG-MJPEG\JPEG-MJPEG_UserAccess_BF561.dpj (9129, 2006-11-03)
MJPEG_encode\BFinUtils\JPEG-MJPEG\JPEG_BitsBuffer.c (30603, 2006-07-17)
MJPEG_encode\BFinUtils\JPEG-MJPEG\JPEG_FormMCU_BLACKFIN.asm (9470, 2006-07-17)
MJPEG_encode\BFinUtils\JPEG-MJPEG\JPEG_McuBuffer.c (70229, 2006-07-30)
MJPEG_encode\BFinUtils\JPEG-MJPEG\JPEG_MemAlloc.c (5690, 2006-07-17)
MJPEG_encode\BFinUtils\JPEG-MJPEG\MJPEG_AVI_FileInfo.c (5911, 2006-07-17)
MJPEG_encode\BFinUtils\JPEG-MJPEG\MJPEG_AVI_FileReader.c (29624, 2006-07-17)
MJPEG_encode\BFinUtils\JPEG-MJPEG\MJPEG_AVI_FileWriter.c (29650, 2006-07-17)
MJPEG_encode\BFinUtils\JPEG-MJPEG\jpeg_mjpeg_cache.c (1973, 2006-07-25)
MJPEG_encode\BFinUtils\JPEG-MJPEG\jpeg_mjpeg_err.c (4161, 2006-07-21)
MJPEG_encode\BFinUtils\ADSP-BF561\SDK-CoreB_Idle.doj (752, 2006-04-17)
MJPEG_encode\BFinUtils\ADSP-BF561\SDK-coreb_idle.c (561, 2006-05-23)
MJPEG_encode\BFinUtils\ADSP-BF561\SDK-cycle_count.asm (2061, 2006-07-05)
... ...

The files in this directory are: SDK-cycle_count.asm SDK-dummy.c SDK-CoreB_Idle.doj SDK-CoreB_Idle.doj Below is a description of the files in this directory. SDK-cycle_count.asm: ------------------- This file is used by the set of image processing and analysis algorithms that are found in the '...\BlackfinSDK\Algorithms\ImageProcessingAnalysis\ADSP-BF561' folder. SDK-dummy.c: ------------ One aapproach to dual core development is to create sub-projects for each memory type: Core A L1, Core B L1, L2 memory and L3 memory, with a main project that links together the result of each sub-project. At the time of this release, it is a requirement of VisualDSP that the ADSP-BF561 main project have at least one source file, so a dummy source file is provided here, which the applications may include in their main projects. SDK-CoreB_Idle.c, SDK-CoreB_Idle.doj: ------------------------------------- Many ADSP-BF561 applications run on a single core, with no program running on core B. If the application is boot-loaded without the use of the VisualDSP debugger, core B remains idle. The single core applications are typically linked using an LDF whose name is consistent with the project name, but ends with "sc" for "single core". The object file, 'SDK-CoreB_Idle.doj', contains an idle loop that is linked by the "sc" LDF, for the purpose of loading an idle loop, for core B to execute, if needed. The source file 'SDK-CoreB_Idle.c', shows that idle loop. Why is the idle loop needed? To review the ADSP-BF561 runtime behavior, after hardware reset, core A begins running, but core B is held in the idle state. The two ways that Core B can run, is for Core A to clear COREB_SRAM_INIT (bit 5) in the SICA_SYSCR register, or for the VisualDSP emulator to perform it's connection sequence, which releases Core B from the idle state. (For that reason, when using the emulator, a program must ALWAYS be loaded to core B program space, even if it's just an idle loop.) For the System Services Power Management Module to perform its initialization, which involves programming the PLL or affecting the SDRAM settings, both cores must be in an idled state. Dual core programs and single core programs, whether boot loaded, or loaded with the VisualDSP emulator) require a mechanism for Core A to bring Core B into IDLE, while the PLL or EBIU changes are applied. This file is used by single core programs for which core B has been released from the idle state, either by VisualDSP, or by a previously running program.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：