Changes between Version 1 and Version 2 of WaveformDeveloperGuide
- Timestamp:
- 02/13/10 21:04:42 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WaveformDeveloperGuide
v1 v2 1 1 = ALOE Waveform Developer Guide = 2 [[BR]] '''WARNING''': This page is under heavy construction, be careful when following instructions found here. [[BR]]3 2 4 3 Here you will find information on how to design, debug and test Software Radio applications for ALOE. … … 53 52 54 53 == Debugging Waveforms with Eclipse (or gdb) == 54 55 55 Once your ALOE is running, and just after loading the application, you can attach to the running process using your favourite debugger (gdb, ddd, eclipse, etc.). The following steps lead you to debug a waveform component: 56 56 … … 58 58 59 59 {{{ 60 runph phal-repositories - d 160 runph phal-repositories --debug 61 61 }}} 62 62 63 2. On the prompt, as usual, load your waveform 63 64 … … 65 66 runph$: phload my_app 66 67 }}} 68 67 69 3. Create or open an Eclipse project for your component. 68 70 69 4. Place a break-point on every component you want to debug, in the INIT or in the RUN phase (or in both)71 4. Place a break-point on every component you want to debug, in the INIT or in the RUN phase 70 72 71 73 5. Right-click in the binary (left-frame, "Project Explorer") and select debug … … 78 80 runph$: phinit my_app 79 81 }}} 80 8. If you placed a breakpoin thte the initialization phase, you will see how the program stops on it. You can continue the execution (step by step or free running) until the component arrives to the Status() call. At that point, you can begin to debug the RUN phase. We recommended using step-by-step execution, so you can place a breakpoint anywhere in the RUN piece of code and you will see how the program stops on every timeslot. In the runph prompt type: 82 83 8. If you placed a breakpoint in the initialization phase, you will see how the program stops on it. You can continue the execution (step by step or free running) until the component arrives to the Status() call. At that point, you can begin to debug the RUN phase. We recommended using step-by-step execution, so you can place a breakpoint anywhere in the RUN piece of code and you will see how the program stops on every timeslot. In the runph prompt type: 81 84 82 85 {{{ 83 86 runph$: phstep my_app 84 87 }}} 88 85 89 9. Leave the component in free-run (in Eclipse), it will fall to idle, until the next step, so, go back to runph prompt and type ''phstep'' again. Remember that you also have the option to remove breakpoints and run a finite number of steps, you can do so by typing, in the runph prompt: 86 90 … … 88 92 runph$: phrun my_app 100 89 93 }}} 90 To run 100 timeslots. 94 95 To run 100 timeslots. 91 96 92 97
