Linux Debug - Revision history

SebastienSz: /* Observing systems clocks */

2019-05-03T08:31:09Z

Observing systems clocks

← Older revision		Revision as of 10:31, 3 May 2019
Line 140:		Line 140:
	</pre>		</pre>

	==Observing ~~systems~~ clocks==		==Observing system clocks==

	You can "export" and observe some clocks:		You can "export" and observe some clocks:

2019-05-03T08:30:54Z

@@ 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

2018-08-01T15:06:00Z

Showing clock tree

← Older revision		Revision as of 17:06, 1 August 2018
Line 104:		Line 104:
	[*] DebugFS representation of clock tree		[*] DebugFS representation of clock tree

			\| Creates a directory hierarchy in debugfs for visualizing the clk
			\| tree structure. Each directory contains read-only members
			\| that export information specific to that clk node: clk_rate,
			\| clk_flags, clk_prepare_count, clk_enable_count & clk_notifier_count.
			</pre>

	~~Creates a directory hierarchy in debugfs for visualizing the~~ clk \|		all clocks are availables under ''/sys/kernel/debug/clk'':
	~~tree structure. Each directory contains read~~-only members \|		<pre class="apf">
	~~that export information specific to that~~ clk node: clk_rate, \|		# mount -t debugfs none /sys/kernel/debug/
	clk_flags, clk_prepare_count, clk_enable_count & \|		# cat /sys/kernel/debug/clk/clk_summary
	~~clk_notifier_count.~~
	</pre>		</pre>

	~~all clocks are availables under /sys/kernel/debug/clk~~

	==Tracers==		==Tracers==

2017-07-19T05:47:31Z

Changing processor registers from Linux user space with imxregs

← Older revision		Revision as of 07:47, 19 July 2017
Line 36:		Line 36:

	===Unlock registers access===		===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):		* 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):

2013-09-04T15:54:39Z

Function profiler

2013-02-05T18:03:00Z

Showing already allocated GPIOs

@@ Line 96: / Line 96: @@
 ....
 </pre>
 ==Tracers==

2012-04-04T13:19:29Z

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

@@ 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>

2012-02-28T10:05:27Z

Using DebugFS

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

2012-02-28T09:58:50Z

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

← Older revision		Revision as of 11:58, 28 February 2012
Line 61:		Line 61:
	</pre>		</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==		==Using DebugFS==

2012-02-08T10:17:36Z

Changing processor registers from Linux user space with imxregs

← Older revision		Revision as of 12:17, 8 February 2012
Line 19:		Line 19:

	In recent releases (>= 3.0) you should find this tool in ''/usr/bin/'' on your board.		In recent releases (>= 3.0) you should find this tool in ''/usr/bin/'' on your board.

			===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}}

	* 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):		* 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>		</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:		* Then in Linux console/terminal, launch ''imxregs'' like that:
	<pre class="apf">		<pre class="apf">
Line 48:		Line 50:
	</pre>		</pre>

	===Examples:===		===Examples===
	* Show OCR1 registers of each GPIO Port:		* Show OCR1 registers of each GPIO Port:
	<pre class="apf">		<pre class="apf">