Linux Debug - Revision history

SebastienSz: /* Observing systems clocks */

2019-05-03T08:31:09Z

‎Observing systems clocks

SebastienSz at 08:30, 3 May 2019

2019-05-03T08:30:54Z

JulienB: /* Showing clock tree */

2018-08-01T15:06:00Z

‎Showing clock tree

JulienB: /* Changing processor registers from Linux user space with imxregs */

2017-07-19T05:47:31Z

‎Changing processor registers from Linux user space with imxregs

WikiSysop: /* Function profiler */

2013-09-04T15:54:39Z

‎Function profiler

GwenhaelG: /* Showing already allocated GPIOs */

2013-02-05T18:03:00Z

‎Showing already allocated GPIOs

Jorasse: /* Testing your custom Linux kernel before flashing it */ use u-bbot script to download kernel image

2012-04-04T13:19:29Z

‎Testing your custom Linux kernel before flashing it: use u-bbot script to download kernel image

JulienB: /* Using DebugFS */

2012-02-28T10:05:27Z

‎Using DebugFS

JulienB: /* Changing FPGA IP's registers from Linux user space with fpgaregs */

2012-02-28T09:58:50Z

‎Changing FPGA IP's registers from Linux user space with fpgaregs

WikiSysop: /* Changing processor registers from Linux user space with imxregs */

2012-02-08T10:17:36Z

‎Changing processor registers from Linux user space with imxregs

@@ Line 140: / Line 140: @@
 </pre>
-==Observing systems clocks==
+==Observing system clocks==
 You can "export" and observe some clocks:

@@ Line 139: / Line 139: @@
   have been hit and their counters.
 </pre>
 ==Links==
 * http://www-users.cs.umn.edu/~boutcher/kprobes/
 * http://tree.celinuxforum.org/CelfPubWiki/PatchArchive

@@ Line 104: / Line 104: @@
          [*]   DebugFS representation of clock tree
+| Creates a directory hierarchy in debugfs for visualizing the clk
-Creates a directory hierarchy in debugfs for visualizing the clk                                                                                                                                                            |
+| tree structure.  Each directory contains read-only members
-tree structure.  Each directory contains read-only members                                                                                                                                                                |
+| that export information specific to that clk node: clk_rate,
-that export information specific to that clk node: clk_rate,                                                                                                                                                              |
+| clk_flags, clk_prepare_count, clk_enable_count & clk_notifier_count.
-clk_flags, clk_prepare_count, clk_enable_count &                                                                                                                                                                          |
 clk_notifier_count.
 </pre>
-all clocks are availables under /sys/kernel/debug/clk
+all clocks are availables under ''/sys/kernel/debug/clk'':
 ==Tracers==

@@ Line 36: / Line 36: @@
 ===Unlock registers access===
-{{Note | On '''APF51''' & '''APF28''' you don't have to explicitly unlock registers in U-Boot to access them under Linux, like explained just above}}
+{{Note | On [[APF51]]/[[APF28]]/[[OPOS6UL]] you don't have to explicitly unlock registers in U-Boot to access them under Linux, like explained just above}}
 * To use it, you must clear i.MX PAR_1 & PAR_2 registers (registers access rights) '''before''' launching Linux kernel, so in U-Boot type (example here is for APF9328):

@@ Line 119: / Line 119: @@
 ===Function profiler===
 <pre class="host">
-$ make linux26-menuconfig
+$ make linux-menuconfig
 </pre>

@@ Line 10: / Line 10: @@
 Indeed Linux kernel images can be loaded and started from SDRAM with U-Boot:
 <pre class="apf">
-  BIOS> tftp ${loadaddr} ${board_name}-linux.bin
+  BIOS> run download_kernel
- BIOS> bootm ${loadaddr}
+MAC: 00:1e:ac:00:00:02
 </pre>

@@ Line 80: / Line 80: @@
   gpio-8   (LCD                 ) in  lo
 ....
 </pre>

@@ Line 61: / Line 61: @@
 </pre>
-==Changing FPGA IP's registers from Linux user space with fpgaregs==
+==Changing FPGA IP's registers from Linux user space==
-see [[FPGA_register]]
+See [[FPGA_register|fpgaregs]] tool.
 ==Using DebugFS==

@@ Line 19: / Line 19: @@
 In recent releases (>= 3.0) you should find this tool in ''/usr/bin/'' on your board.
 * To use it, you must clear i.MX PAR_1 & PAR_2 registers (registers access rights) '''before''' launching Linux kernel, so in U-Boot type (example here is for APF9328):
@@ Line 37: / Line 40: @@
 </pre>
-{{Note | On '''APF51''' you don't have to unlock registers to access it under linux}}
+===Usage===
-−
 * Then in Linux console/terminal, launch ''imxregs'' like that:
 <pre class="apf">
@@ Line 48: / Line 50: @@
 </pre>
-===Examples:===
+===Examples===
 * Show OCR1 registers of each GPIO Port:
 <pre class="apf">