Skip to content
This repository

OMAPCONF: Texas Instruments OMAP Processors Diagnostic Tool

branch: master

[DRA7][PRCM] Use SYS_CLK1 rates based on CM_CLKSEL_SYS

The SYS_CLK1 rate is currently hard-coded to 20 MHz matching
the value on the DRA7 EVM, but not every one will be using
the same crystal frequency. Use the CM_CLKSEL_SYS register
value to compute the SYS_CLK1 rate. The rates are limited
to 19.2, 20 and 27 MHz as per the latest DM manual.

NOTE: SYS_CLK2 rate is also hard-coded similarly, but there
doesn't seem to be a register for reading it. So, for accuracy,
this value needs to be updated in code.

Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Nishant Menon <nm@ti.com>
latest commit c83d2f5925
Suman Anna sumananna authored April 09, 2014 Nishanth Menon committed April 09, 2014
Octocat-spinner-32 arch [DRA7][PRCM] Use SYS_CLK1 rates based on CM_CLKSEL_SYS April 09, 2014
Octocat-spinner-32 audioic [DRA7][AUDIO] Add support for tlv320aic3x audioic August 16, 2013
Octocat-spinner-32 bash_completion.d initial public release v1.50 September 21, 2012
Octocat-spinner-32 common omapconf: get rid of macro based version information March 31, 2014
Octocat-spinner-32 i2c-tools [I2C] update to I2C Tools library v3.1.0 November 19, 2012
Octocat-spinner-32 linux fix empty interrupt statistic when CPU1 is offline October 09, 2012
Octocat-spinner-32 pmic [DRA7][VOLTAGE] omapconf set voltage <rail> <voltage> August 16, 2013
Octocat-spinner-32 regression_test_suite [REGRESSIONTESTSUITE] add EMIF test, remove kernel clock test, do not… December 06, 2012
Octocat-spinner-32 .gitignore omapconf: get rid of macro based version information March 31, 2014
Octocat-spinner-32 CHANGELOG omapconf v1.69 March 31, 2014
Octocat-spinner-32 CONTRIBUTE initial public release v1.50 September 21, 2012
Octocat-spinner-32 CREDITS initial public release v1.50 September 21, 2012
Octocat-spinner-32 LICENSE initial public release v1.50 September 21, 2012
Octocat-spinner-32 MAINTAINERS initial public release v1.50 September 21, 2012
Octocat-spinner-32 Makefile Makefile: add dirty tag if git repo was modified. April 09, 2014
Octocat-spinner-32 README.md update README with static/dynamic build instructions January 22, 2013
Octocat-spinner-32 omapconf.c [DRA7][PRCM] add omapconf dump prcm [<pwrdm>] August 16, 2013
Octocat-spinner-32 revision.h omapconf: get rid of macro based version information March 31, 2014
README.md

OMAPCONF

A Powerful Diagnostic Tool for Texas Instruments OMAP Processors

ABOUT:

OMAPCONF is a Linux user-space standalone application designed to provide a quick'n easy way to diagnose (monitor/debug/audit...) TI OMAP configuration/status dynamically at runtime, in any situation:

  • Any Linux distribution (Ubuntu, ...)
  • Any Android release (Froyo, GingerBread, HoneyComb, Ice-Cream Sandwich, Jelly Bean, ...)
  • TI official platforms (blaze, panda, ...),
  • Custom OMAP platforms, etc.
  • With no single kernel recompilation needed

OMAPCONF leverages "/dev/mem" special device to directly access complete TI OMAP memory space (registers, ...).

SUPPORT:

OMAPCONF CURRENTLY SUPPORTS TI OMAP44XX AND OMAP54XX DEVICES. LEGACY TI OMAP PLATFORMS (OMAP[1-2-3]) ARE NOT SUPPORTED.

THIS SOFTWARE IS PROVIDED AS IS, WITH NO SUPPORT OR MAINTENANCE COMMITMENT FROM TEXAS INSTRUMENTS INCORPORATED.

Build instructions (Ubuntu):

OMAPCONF is available as a Ubuntu package. To proceed with package installation type the following:

# sudo apt-get install tiomapconf

Once package is installed, you can check which omapconf version you are using:

# dpkg -l tiomapconf

Package is available via TI OMAP4 Ubuntu PPA. See the OMAPpedia page for further instructions.

Build instructions (other Linux Distributions):

To only build the output binary file: # make CROSS_COMPILE=arm-none-linux-gnueabi- omapconf

NB: - CROSS_COMPILE variable must be set to point to the correct compiler. - By default, omapconf is statically built, to ease sharing. In case it is not needed or size matters, it is possible to build it dynamically, by setting variable STATIC_BUILD to "". # export STATIC_BUILD= or # make CROSS_COMPILE=arm-none-linux-gnueabi- STATIC_BUILD= omapconf

To build and install ompaconf:

# make CROSS_COMPILE=arm-none-linux-gnueabi- DESTDIR=YOUR_DIR install

YOUR_DIR is a destination directory where omapconf output binary file will be copied (e.g. ubuntu/android filesystem)

That's it!

Build instructions and installation via ADB (Android):

Make sure your Android device is connected to host via ADB:

# adb kill-server
# adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
 emulator-5554  device
# adb root

To build and install ompaconf for Android via ADB:

# make CROSS_COMPILE=arm-none-linux-gnueabi- install_android

OMAPCONF binary will be copied to /data directory (known writable directory) on your Android device. You may get it copied to a different directory by updating Makefile at your convenience.

Help:

Type "./omapconf --help" to get complete list of available commands and options. Note that in case of incorrect command/option, help will also be displayed.

A dedicated wiki page is available here.

Something went wrong with that request. Please try again.