This patch add an conditional size boundary check to
make sure that the collected minidumps is within the
reserved memory region. If not, it throws failure
message and do reset.
Change-Id: I97c721f792350e83463f5dcff412785b8263bb4c
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
Skip reset in crash dump path which give access to user
to perform secure authentication.
in crash path,
bootipq cmd only authenticate kernel/rootfs.
booting to kernel is restircted.
Enable CONFIG_SKIP_RESET to skip reset in crashdump path.
Change-Id: I28fdd4dc6475d4d26b20a87aa039cef165db1375
Signed-off-by: Gurumoorthy Santhakumar <quic_gsanthak@quicinc.com>
This patch enable the uboot to collec the minidump
by parsing the TLVs exposed by the kernel and store it
into the nvmem (Non volatile memory) either NAND / eMMC
To enable this feature,
setenv dump_minimal 1
setenv dump_to_nvmem "<partition_name>"
Change-Id: I2f2ed2ad2e8506957288052edaf5d6290ae787b7
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
This patch enables support to do minidump on DDR.
Enable this support by setting respective reserved mem address
in the env "dump_to_mem"
setenv dump_minimal 1
setenv dump_to_mem "<addr> <size>"
addr & size param should matches with respect to the kernel
reserved memory region.
setenv dump_to_mem "0x44000000 0x500000"
Change-Id: I3f98269d42eed1e6301ed76eb9d1bcdd82046d41
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
With this change, Add option to support
prefixing crash dump files with timestamp prefix
Change-Id: I30343e6d7dc58376264dd34a4a3cd25bb34e65c6
Signed-off-by: Saahil Tomar <quic_saahtoma@quicinc.com>
This patch removes the support for dumpinfo_s structure to have
uniform EBICS0 bin for both sec and non-sec boots as the Read As Zero
(RAZ) flag has been enabled to protect code and data regions of TZ
The patchset applies to all the targets except IPQ5018 as the RAZ
flag enablement was not supported in IPQ5018
Change-Id: I63514284448de08926cd2c9b741f02859067044d
Signed-off-by: devi priya <quic_devipriy@quicinc.com>
Some USB devices taking more time to store the binary file if the
device has multiple partitions. Immediate usb stop can discard the
previously transfered binary. This patch adds delay to overcome the
issue
Change-Id: Iccbf272ebdfc3542ac1474129e07e852e8d7bbaa
Signed-off-by: Praveenkumar I <quic_ipkumar@quicinc.com>
Previously the MAX_NAND_PAGE_SIZE was defined as 2K
during when we will face issues when dumping to
flash in nand-4k. This patch updates the max size
to 4K to support the same in nand-4k.
Change-Id: Idcec9998f56df1db21fc03097d0454efd81bbbd3
Signed-off-by: Selvam Sathappan Periakaruppan <quic_speriaka@quicinc.com>
During dump collection, when dump_to_flash enabled, nand erases are skipped
due to unaligned written. This changes handles that and write after erasing
Signed-off-by: Karthick Shanmugham <kartshan@codeaurora.org>
Change-Id: Idfc6b3a0596a5ddb5c7e0b0da5c7bcb2751769b8
This change will skip the bad blocks offsets, if any while writing
into the nand flash duirng crash when dump_to_flash enabled. This
change also verifies whether the dump data is not overwritten into
the next partition.
Signed-off-by: Karthick Shanmugham <kartshan@codeaurora.org>
Change-Id: I0eec4c772a5f5efb3c17bfd1fd3d3d9a5ff85d1d
When dump_to_flash is set, and if the cur_type value is
set to QCA_WDT_LOG_DUMP_TYPE_INVALID, while loop is
executed forever. So, handled the error cases properly.
Change-Id: Ic3fdc01897b4fe9a45023074e9397af3c84f3aaa
Signed-off-by: Balaji Prakash J <bjagadee@codeaurora.org>
This changes remove nand command and Env support
Signed-off-by: Vandhiadevan Karunamoorthy <vkarunam@codeaurora.org>
Change-Id: I6c59f8259306ef79499420afe4da17a2674e98be
To test minidump feature, we require a method to
collect full dump and minidump binaries on a
single run for side by side comparison.
This change enables dumping of minidump and
full dump binaries consecutively when uboot
env variable 'dump_minimal_and_full' is set.
Change-Id: I846084546d3c67398d7ef7b81e87c97bcc63c609
Signed-off-by: Gitanjali Krishna <gitanjal@codeaurora.org>
This change adds support in u-boot to handle
dumping of DEBUGFS TLV information and MMU Metadata
file.
Change-Id: Iebf67b932ba90b5081e6903c5fe44ed3105df798
Signed-off-by: Gitanjali Krishna <gitanjal@codeaurora.org>
Change Metadata file name for minidump
from MODULE_INFO.txt to MOD_INFO.txt to
avoid mismatch with T32 scripts
Change-Id: I4e56455ceaa7ba832b3882fc62a23a0b29244e83
Signed-off-by: Gitanjali Krishna <gitanjal@codeaurora.org>
This change adds a time delay of 1 second before resetting the
SoC after USB crashdump collection, as some devices requires
spare time to flush the contents to disk.
Change-Id: I407ca5a2eb55762edd5fdb011b8464285019b18c
Signed-off-by: Pavithra Palanisamy <pavip@codeaurora.org>
Using CONFIG_TZ_END_ADDR for manipulating the size of EBICS_S2
dump size, restricts us to have CONFIG_TZ_END_ADDR as the
EBICS_S2 start address. Instead of using CONFIG_TZ_END_ADDR,
used the table info for calculating the size.
This way, for ipq6018, 256M boundary(0x50000000) can be used as
EBICS_S2 dump start address.
Change-Id: I2fc69774301aad599425af1e9b106fe8bc35dbf8
Signed-off-by: Balaji Prakash J <bjagadee@codeaurora.org>
This change will add support for collecting crashdump as
compressed gzip file, if specified through uboot environment
variable 'dump_compressed'
Change-Id: I0c3fb16bc07aaa0103e75a551477fce13f9e26da
Signed-off-by: Pavithra Palanisamy <pavip@codeaurora.org>
As per FAT spec, the number of sectors can be more than
clusters, as clusters starts from databegin.
So check cluster overflow against total clusters.
The FAT at present in u-boot lacks a lot, such as
support for long file names, subdir etc.
The mini dump was using more than 8 character name,
changed that one too.
Change-Id: Icfae6d955dd93432b3d33d7c0b9a724382d87185
Signed-off-by: Manoharan Vijaya Raghavan <mraghava@codeaurora.org>
This change modifies size of crashdump buffer to
12K from 16K for ipq60xx and ipq807x
This change also makes dumping of crashdump TLVs more
generic and does not assume any fixed positions for
static or dynamic dump segments
Change-Id: I9723ebf55e4a6db3360b3370a2c6e15d22741e08
Signed-off-by: Gitanjali Krishna <gitanjal@codeaurora.org>
This change adds support to search for valid FAT32 partition
throughout the device during crashdump collection on USB,
despite encountering any invalid-partition on the loop.
Change-Id: Ic6bda03a2448c38f0e93d32214340c2ee896f385
Signed-off-by: Pavithra Palanisamy <pavip@codeaurora.org>
This change adds support to ignore invalidated
TLVs in crashdump buffer
Change-Id: Ic8513fb4155755f421f94683fe739ba73d55aa21
Signed-off-by: Gitanjali Krishna <gitanjal@codeaurora.org>
This change enables support to collect crashdump files
in connected usb storage device on requirement.
Change-Id: If191bcae5329dd2c9e84035069e4d9b0e73b546b
Signed-off-by: Pavithra Palanisamy <pavip@codeaurora.org>
Change TLV message buffer offsets to match with kernel
that has been adjusted to use last 16K of memory
allocated for crashdump buffer. This was done to
accomodate greater number of dump segemnts.
Change-Id: Idb8c1bab6a0900152a9d413382b2b3c87a19170e
Signed-off-by: Venkat Raju Sana <vrsana@codeaurora.org>
This change adds an additional dump binary
containing Meta Data information for minimal
crashdump collection feature
Change-Id: I8427f3d41cf454ea7adf6b1565be58f3cc950e61
Signed-off-by: Gitanjali Krishna <gitanjal@codeaurora.org>
Force the crashdump collection based on environment variable. If the
environment varibale force_crashdump is set then we will proceed directly
with the crashdump collection, else we will wait for user input
for 10s before going for crashdump collection.
Change-Id: Ida500bd060dcdd46736e9ea950a0009353abcbf1
Signed-off-by: Nikhil Prakash V <nprakash@codeaurora.org>
