Fix typos in tracing vectors
Dynamically choose between DAP_M3 and DAP_DebugSS
Fix copy/paste error in am335x-boot.dss
Add files for decoding pinmux data
Documentation
Add more complete EMIF register dump
Fix all line endings
Explicitly handle line endings for this repo
Update to work with CLOCKTREETOOL-SITARA
The individual Clock Tree Tools were merged into a unified
bundle called CLOCKTREETOOL-SITARA. This tool represents
the latest and is recommended for use. The first line of
the *.rd1 file has an updated header. This update is so
that files generated with this script can be cleanly
imported into this updated tool. The generated output can
be modified by hand if you need to import into the old tool
for any reason.
The individual Clock Tree Tools were merged into a unified
bundle called CLOCKTREETOOL-SITARA. This tool represents
the latest and is recommended for use. The first line of
the *.rd1 file has an updated header. This update is so
that files generated with this script can be cleanly
imported into this updated tool. The generated output can
be modified by hand if you need to import into the old tool
for any reason.
export csv of padconf for ds0
am335x-bbb-pru-startup.js initial commit
Script for simplifying connection to BBB PRU via JTAG
Derived from example script here:
http://processors.wiki.ti.com/index.php/Debug_Configuration_Initialization_Scripts
Documentation for this script and its usage available here:
http://processors.wiki.ti.com/index.php/PRU-ICSS_Debug_on_AM335x
Script for simplifying connection to BBB PRU via JTAG
Derived from example script here:
http://processors.wiki.ti.com/index.php/Debug_Configuration_Initialization_Scripts
Documentation for this script and its usage available here:
http://processors.wiki.ti.com/index.php/PRU-ICSS_Debug_on_AM335x
quick analysis of power domains and modules
This file should be useful for debugging suspend/resume issues when
trying to enter DeepSleep0 with AM335x.
See this page for more info:
http://processors.wiki.ti.com/index.php/Debugging_AM335x_Suspend-Resume_Issues
This file should be useful for debugging suspend/resume issues when
trying to enter DeepSleep0 with AM335x.
See this page for more info:
http://processors.wiki.ti.com/index.php/Debugging_AM335x_Suspend-Resume_Issues
Improved robustness due to clock inspection/adjustment
1. Print a message in case where cannot connect at all. (General JTAG
issues.)
2. Initially connect to DAP_M3 to interrogate the state of DEBUGSS_CLK
and EMIF_CLK.
3. Skip analysis of EMIF registers and print message in case where EMIF
clock is disabled (e.g. just before reaching DS0).
4. In case where EMIF is alive, but DEBUGSS_CLK is disabled, temporarily
enable the clock through the DAP_M3, read the EMIF registers of
interest, and then restore DEBUGSS_CLK to its original value.
These enhancements make it much easier to use this script and avoid the
need for kernel changes or poking registers with devmem2.
1. Print a message in case where cannot connect at all. (General JTAG
issues.)
2. Initially connect to DAP_M3 to interrogate the state of DEBUGSS_CLK
and EMIF_CLK.
3. Skip analysis of EMIF registers and print message in case where EMIF
clock is disabled (e.g. just before reaching DS0).
4. In case where EMIF is alive, but DEBUGSS_CLK is disabled, temporarily
enable the clock through the DAP_M3, read the EMIF registers of
interest, and then restore DEBUGSS_CLK to its original value.
These enhancements make it much easier to use this script and avoid the
need for kernel changes or poking registers with devmem2.
Add extra robustness with try/catch statements
Switch to DAP_M3
The normal DAP sits on the L3 interconnect and requires more clocks to
be active in order for it to work. In Linux that clock is often not
active by default. We can use the DAP_M3 instead which is still
accessible. This also helps with debugging low power issues since the
DAP_M3 remains accessible almost all the way into DS0. This allows you
to inspect the SoC state very close to DS0 to look for issues.
The normal DAP sits on the L3 interconnect and requires more clocks to
be active in order for it to work. In Linux that clock is often not
active by default. We can use the DAP_M3 instead which is still
accessible. This also helps with debugging low power issues since the
DAP_M3 remains accessible almost all the way into DS0. This allows you
to inspect the SoC state very close to DS0 to look for issues.
analysis of ddr_cke_ctrl
vref_ctrl analysis
minor formatting
Add comments regarding vtp_ctrl register
Add check for ddr_io_ctrl.ddr3_rst_def_val
Use DAP_M3 to read Control registers
The normal DEBUGSS_DAP sits on the L3 interconnect and so it is not
usable when you most of the chip has been turned off, as is the case
when going to DS0. Using the DAP_M3 has less visibility into the device
as a whole, but is still usable almost all the way to suspend.
The normal DEBUGSS_DAP sits on the L3 interconnect and so it is not
usable when you most of the chip has been turned off, as is the case
when going to DS0. Using the DAP_M3 has less visibility into the device
as a whole, but is still usable almost all the way to suspend.
Decode the values for pullup/pulldown/keeper for each DDR pin
Add warning if reg_phy_enable_dynamic_pwrdn is disabled
Add print that tells name of file created
Check PWR_MGMT_CTRL.reg_sr_tim for JEDEC compliance
See the section titled "DDR3: JEDEC Compliance for Maximum Self-Refresh
Command Limit" in the AM335x silicon errata for more details.
See the section titled "DDR3: JEDEC Compliance for Maximum Self-Refresh
Command Limit" in the AM335x silicon errata for more details.
Add Modified BSD License to header of files.
Initial commit for am335x-boot.dss
added a bunch of missing registers!
Add DAP disconnect to end of file
Force usage of DAP
* Users no longer need to connect to a core before invoking the script
* DAP is non-intrusive to A8, i.e. don't ever have to halt A8
* Users no longer need to connect to a core before invoking the script
* DAP is non-intrusive to A8, i.e. don't ever have to halt A8
initial commit