Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
resources:tools-software:linuxdsp:docs:linux-kernel-and-drivers:remoteproc:remoteproc [07 Jul 2020 11:52] Sunny Fengresources:tools-software:linuxdsp:docs:linux-kernel-and-drivers:remoteproc:remoteproc [03 Jan 2021 21:43] (current) – fix links Robin Getz
Line 8: Line 8:
   * ADSP-SC573 Ezkit or,   * ADSP-SC573 Ezkit or,
   * ADSP-SC589 MINI   * ADSP-SC589 MINI
-Nothing connections needed except the uart, ethernet and power connections.+No connections are required except the uart, ethernet and power connections.
  
 ===== Software Configuration ===== ===== Software Configuration =====
Line 30: Line 30:
  
  
 +\\
 ===== How to Use the Remoteproc Framework ===== ===== How to Use the Remoteproc Framework =====
 ==== Remote Processor Start ==== ==== Remote Processor Start ====
Line 41: Line 42:
 root@adsp-sc589-ezkit:~# echo blinky_Core1_sc589.ldr > /sys/class/remoteproc/remoteproc0/firmware root@adsp-sc589-ezkit:~# echo blinky_Core1_sc589.ldr > /sys/class/remoteproc/remoteproc0/firmware
 </code> </code>
-<WRAP info 100%>The blinky_Core1_sc589.ldr is SHARC firmware generated through ADI [[https://www.analog.com/en/design-center/evaluation-hardware-and-software/software/adswt-cces.html|CrossCore® Embedded Studio]]. Refer this page for [[resources:tools-software/linuxdsp/docs/linux-kernel-and-drivers/remoteproc/remoteproc_ldr_generate|How to generate remoteproc LDR file in CCES]].+<WRAP info 100%>The blinky_Core1_sc589.ldr is one SHARC LED blinking application generated through ADI [[adi>en/design-center/evaluation-hardware-and-software/software/adswt-cces.html|CrossCore® Embedded Studio]]. Refer this page for ''[[resources:tools-software/linuxdsp/docs/linux-kernel-and-drivers/remoteproc/remoteproc_ldr_generate|How to generate remoteproc LDR file in CCES]]''.
 </WRAP> </WRAP>
  
Line 48: Line 49:
 root@adsp-sc589-ezkit:~# echo start > /sys/class/remoteproc/remoteproc0/state root@adsp-sc589-ezkit:~# echo start > /sys/class/remoteproc/remoteproc0/state
 </code> </code>
-The LED would start blinky on sc589-ezkit board.+The LED will start blinking on sc589-ezkit board.
  
 ==== Remote Processor Stop ==== ==== Remote Processor Stop ====
-Run the below command, SOFT irq would be raised through SEC interface to SHARC core, then SHARC releases all related resources including interrupts, hardwares and SHARC set itself to IDLE.+Run the below command, one SOFT irq would be raised through SEC interface to SHARC core, SHARC core will release all related resources(interrupts, hardwares, etc) and set itself to IDLE state once receiving the interrupt.
 <code> <code>
 root@adsp-sc589-ezkit:~# echo stop > /sys/class/remoteproc/remoteproc0/state root@adsp-sc589-ezkit:~# echo stop > /sys/class/remoteproc/remoteproc0/state
Line 57: Line 58:
  
 ==== Remote Processor Auto Boot ==== ==== Remote Processor Auto Boot ====
-ADI set a specified name called adi_adsp_core1_fw.ldr or adi_adsp_core2_fw.ldr to auto boot when kernel booting up.+ADI sets a specified name called adi_adsp_core1_fw.ldr or adi_adsp_core2_fw.ldr to auto boot when kernel starts.
 If you want to auto boot the remote processor, rename your own ldr file to **adi_adsp_core1_fw.ldr** or **adi_adsp_core1_fw.ldr** and put it in **/lib/firmware** directory.  If you want to auto boot the remote processor, rename your own ldr file to **adi_adsp_core1_fw.ldr** or **adi_adsp_core1_fw.ldr** and put it in **/lib/firmware** directory. 
  
 ---- ----
 **Back to** [[resources:tools-software/linuxdsp/docs/linux-kernel-and-drivers/start|Kernel Features and Device Drivers for ADSP-SC5xx Yocto Linux]] **Back to** [[resources:tools-software/linuxdsp/docs/linux-kernel-and-drivers/start|Kernel Features and Device Drivers for ADSP-SC5xx Yocto Linux]]
resources/tools-software/linuxdsp/docs/linux-kernel-and-drivers/remoteproc/remoteproc.1594115577.txt.gz · Last modified: 07 Jul 2020 11:52 by Sunny Feng