CorteXlab's Wiki

User Tools

Site Tools

Trace:
tuto_fpga_pico

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
Next revisionBoth sides next revision
tuto_fpga_pico [2016/12/14 14:46] – [Using a custom bitstream with a PicoSDR] onicolastuto_fpga_pico [2017/08/22 14:23] – migrate from scenario.desc to scenario.yaml mimbert
Line 11: Line 11:
 Let's take a look at ''ofdm.grc'': On ''airlock'', run ''$ gnuradio-companion <path-to-ofdm.grc>''. Let's take a look at ''ofdm.grc'': On ''airlock'', run ''$ gnuradio-companion <path-to-ofdm.grc>''.
  
-First, what it is intended to do : We send a video file to RTDEX Sink, and form RTDEX Source we get the constellation points of the OFDM demodulation and the video file is sent to an UDP Sink (in order to open it with VLC for example). We have also a lot of parameters blocks we don't care about in this tutorials (all the custom register blocks are specific to the bitstream).+First, what it is intended to do: we send a video file to RTDEX Sink, and from RTDEX Source we get the constellation points of the OFDM demodulation and the video file is sent to a UDP Sink (in order to open it with VLC for example). We have also a lot of parameter blocks we don't care about in this tutorials (all the custom register blocks are specific to the bitstream).
  
  
-This example can be used straight away when you are working on your setup, but not in CortXlab because of the video file over UDP thing. Instead of this, we are going to do something a lot easier, which is sending a constant integer to the PicoSDR, and see if we get it back.+This example can be used straight away when you are working on your setup, but not in CorteXlab because of the video file over UDP thing. Instead of this, we are going to do something a lot easier, which is sending a constant integer to the PicoSDR, and see if we get it back.
  
  
Line 83: Line 83:
 ## Create the scenario ## Create the scenario
  
-In order to run the experiment in CorteXlab we need a description called scenario. Create a file named ''scenario.desc'' and copy the following in it :+In order to run the experiment in CorteXlab we need a description called scenario. Create a file named ''scenario.yaml'' and copy the following in it :
 <code> <code>
 # Example scenario description file # Example scenario description file
Line 92: Line 92:
 # Scenario textual description # Scenario textual description
 #   simple string (a one liner) #   simple string (a one liner)
-desc base scenario for CorteXlab+description: base scenario for CorteXlab
  
 # Experiment maximum duration # Experiment maximum duration
 #   Time after which the experiment is forced to stop #   Time after which the experiment is forced to stop
-#   integer (minutes) +#   integer (seconds) 
-durat 5+duration: 300
  
 # Node list # Node list
Line 103: Line 103:
 #   format: #   format:
 # #
-#   (machine): +#   nodes: 
-#   entry (entry point script relative to the task root) +#     (machine): 
-#   exit (exit point script relative to the task root. Use "none" for none)+#       command: (entry point script relative to the task root)
  
-node31: +nodes: 
-   entry ofdm.py +  node31: 
-   bitstreamA OFDM_6_6_0_sx315.bit+    command: ofdm.py 
 +    bitstreamA: OFDM_6_6_0_sx315.bit
 </code> </code>
  
-If you trasnlate this file it says "The experiment will run for 5 minutes. The script ofdm.py will be executed on node 31 using the bitstream OFDM_6_6_0_sx315.bit".+If you translate this file it says "The experiment will run for 5 minutes. The script ofdm.py will be executed on node 31 using the bitstream OFDM_6_6_0_sx315.bit".
  
  
Line 123: Line 124:
 │   ├── ofdm.py │   ├── ofdm.py
 │   ├── epy_block_0.py │   ├── epy_block_0.py
-│   ├── scenario.desc+│   ├── scenario.yaml
 │   ├── ofdm.grc │   ├── ofdm.grc
 │   └── OFDM_6_6_0_sx315.bit │   └── OFDM_6_6_0_sx315.bit
Line 218: Line 219:
 you@srvairlock:~/results/task_15/node31$ ls you@srvairlock:~/results/task_15/node31$ ls
 epy_block_0.py    impact_instr.txt      ofdm.py        stdout.txt epy_block_0.py    impact_instr.txt      ofdm.py        stdout.txt
-epy_block_0.pyc   OFDM_6_6_0_sx315.bit  scenario.desc+epy_block_0.pyc   OFDM_6_6_0_sx315.bit  scenario.yaml
 _impactbatch.log  ofdm.grc              stderr.txt _impactbatch.log  ofdm.grc              stderr.txt
 </code> </code>
  
-We see that all of the files we used to create the task are inside. The other two are:+We see that all of the files we used to create the task are inside. The others are:
  
   * ''stdout.txt'': all output messages from your GNU Radio python script are written here. These include GNU Radio messages as well as all "print"s you include in your code. Seeing the contents of this file is useful to assert its correct operation.   * ''stdout.txt'': all output messages from your GNU Radio python script are written here. These include GNU Radio messages as well as all "print"s you include in your code. Seeing the contents of this file is useful to assert its correct operation.
   * ''stderr.txt'': all error messages are printed here. If you see strange things on the ''stdout.txt'' or nothing at all, it might be interesting to take a look at the ''stderr.txt'' to debug your code.   * ''stderr.txt'': all error messages are printed here. If you see strange things on the ''stdout.txt'' or nothing at all, it might be interesting to take a look at the ''stderr.txt'' to debug your code.
-  * ''impact_instr.txt'': The impact instructions used to flash the bitstream +  * ''impact_instr.txt'': The impact instructions used to flash the bitstream (this file is automatically generated) 
-  * ''_impactbatch.log'': Impact log+  * ''_impactbatch.log'': Impact execution log
  
 Let's take a look inside ''stdout.txt'': Let's take a look inside ''stdout.txt'':
tuto_fpga_pico.txt · Last modified: 2017/11/15 16:22 by onicolas
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki