User Tools

Site Tools


lab4

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
lab4 [2014/02/24 03:24] allisonlab4 [2014/02/26 15:39] (current) allison
Line 45: Line 45:
   - Using antistatic precautions, unpack the BBB. Plug in the USB connection (under the 4 LEDs by the power connector) to the BBB and the PC. This will provide power as well.   - Using antistatic precautions, unpack the BBB. Plug in the USB connection (under the 4 LEDs by the power connector) to the BBB and the PC. This will provide power as well.
   - The BBB should be visible as a flash drive. Double click on Start.html   - The BBB should be visible as a flash drive. Double click on Start.html
-  - MORE here: terminal, scp, Bonescript to shut off LEDs +  - MORE to be added here: terminal, scp, Bonescript to shut off LEDs 
-  - Copy (scp) the example files to the BBB (the zip file can either be expanded on the PC or BBB). These files should be placed in the myapp directory under the example_apps directory (pru_sw/app_loader/example_apps) //We need to see where this will go //+  - Copy (scp) the example files to the BBB (the zip file can either be expanded on the PC or BBB). These files should be placed in the myapp directory under the example_apps directory (~/Desktop/am335x_pru_package-master/pru_sw/app_loader/example_apps) //Note to tech: should set up a proper user and so on for these boards//
   - //cd// to the example_apps directory   - //cd// to the example_apps directory
   - Edit the DIRS file to add the source and paths to the files in myapp. This will allow make to find and move the files appropriately   - Edit the DIRS file to add the source and paths to the files in myapp. This will allow make to find and move the files appropriately
Line 52: Line 52:
   - //cd bin//   - //cd bin//
   - //./pru_ex// to run the program   - //./pru_ex// to run the program
-  - Repeat steps 5 - 10 for your version of the program to build and debug your program //would be good to get a debugger //+  - Repeat steps 5 - 10 for your version of the program to build and debug your program //Note to tech: would be good to get a debugger //
   - When your program is working demonstrate it to the TA     - When your program is working demonstrate it to the TA  
-  - Determine the maximum frequency (minimum bit period) that you can reliable send the data and confirm with an oscilloscope.+  - Determine the maximum frequency (minimum bit period) that you can reliably send the data and confirm with an oscilloscope.
   - How could you improve the performance? How could the ARM/PRU programs be altered to send the data whenever a new signal was required (do not implement)?   - How could you improve the performance? How could the ARM/PRU programs be altered to send the data whenever a new signal was required (do not implement)?
  
Line 66: Line 66:
  
  
-==== Reference Manuals ==== +==== Reference Manuals and Links ==== 
-  *   {{:bbb_srm.pdf|Beaglebone Black Reference Manual}}+  * {{:bbb_srm.pdf|Beaglebone Black Reference Manual}} 
 +  * [[http://processors.wiki.ti.com/index.php/PRU_Assembly_Instructions | Assembly Instructions]] 
 +  * [[http://elinux.org/PRUSSv2_Interrupt_Controller | Interrupt controller ]] 
 +  * [[http://processors.wiki.ti.com/index.php/PRU_Assembly_Reference_Guide | Assmebly Guide ]]
  
  
 ==== Resources ==== ==== Resources ====
   *{{:pru_lab.zip}}   *{{:pru_lab.zip}}
lab4.1393212261.txt.gz · Last modified: 2014/02/24 03:24 by allison

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki