25 hours ago[PDK-13972]: Added sciserver and rmpmhal version header files master REL.PSDK.09.02.00.23
[PDK-13972]: Added sciserver and rmpmhal version header files
-Sciserver amd rmpmhal version header files are autogenerated on
pdk build using generator shell scripts.
-This is disabled in windows builds[PDK-12986] and results in build errors
while building sciserver_tirtos
-Now windows will use the default header files included in the
package and it will be regenerated/overwritten for linux builds
Signed-off-by: S Likhith <likhith@ti.com>
-Sciserver amd rmpmhal version header files are autogenerated on
pdk build using generator shell scripts.
-This is disabled in windows builds[PDK-12986] and results in build errors
while building sciserver_tirtos
-Now windows will use the default header files included in the
package and it will be regenerated/overwritten for linux builds
Signed-off-by: S Likhith <likhith@ti.com>
[PDK-13988][SCICLIENT]: Removes PM Domain Reset from sciclient_firmware_boot_testapp
PM domain reset fails currently. This causes the sciclient_firmware_boot_testapp to hang.
PM domain reset need not be tested as a part of this testapp. Hence removing it.
Signed-off-by: S Likhith <likhith@ti.com>
PM domain reset fails currently. This causes the sciclient_firmware_boot_testapp to hang.
PM domain reset need not be tested as a part of this testapp. Hence removing it.
Signed-off-by: S Likhith <likhith@ti.com>
Package SA2UL driver as part of PDK
Signed-off-by: Jahnavi Guvvala <j-guvvala@ti.com>
Signed-off-by: Jahnavi Guvvala <j-guvvala@ti.com>
[OSAL]: Added Extended source file for Load Submodule
- Removed Osal load test from osal_extended_testapp.c file
- Added them to submodule specific test file.
- Driver change for LoadP static APIs
- Added Negative test for LoadP_calcCounterDiff API
Signed-off-by: Asha <x1101668@ti.com>
- Removed Osal load test from osal_extended_testapp.c file
- Added them to submodule specific test file.
- Driver change for LoadP static APIs
- Added Negative test for LoadP_calcCounterDiff API
Signed-off-by: Asha <x1101668@ti.com>
[OSAL]: Added separate extended testapp for EventP Submodule
- Remove OSAL EventP tests from osal_extended_testapp.c.
- Added them to submodule specific file.
- Added Zero Allocation count test in the negative test
Signed-off-by: Asha <x1101668@ti.com>
- Remove OSAL EventP tests from osal_extended_testapp.c.
- Added them to submodule specific file.
- Added Zero Allocation count test in the negative test
Signed-off-by: Asha <x1101668@ti.com>
[OSAL]: Fix OSAL extended testapp.
- General tests and negative tests were swapped.
- Name the tests correctly
- Negative test was not getting called.
- Add a call to the negative test.
Signed-off-by: Mriganka Chakravarty <m-chakravarty@ti.com>
- General tests and negative tests were swapped.
- Name the tests correctly
- Negative test was not getting called.
- Add a call to the negative test.
Signed-off-by: Mriganka Chakravarty <m-chakravarty@ti.com>
[IPC]: Put C7X cores to IDLE state to facilitate core shutdown.
Signed-off-by: Mriganka Chakravarty <m-chakravarty@ti.com>
Signed-off-by: Mriganka Chakravarty <m-chakravarty@ti.com>
[OSAL]: Added new testcases for the Sub-modules
- Multiple Mutex create test
- Null checks on Heap API's
- Utils nonos test
- CycleProfiler test
- Enabled Hwi Null check test
Signed-off-by: Asha <x1101668@ti.com>
- Multiple Mutex create test
- Null checks on Heap API's
- Utils nonos test
- CycleProfiler test
- Enabled Hwi Null check test
Signed-off-by: Asha <x1101668@ti.com>
[OSAL]: Added tescases for Submodule
1. Added Negative testcase for Hwi Submodule
- OsalApp_hwiDeleteNegativeTest
2. Added test for zero Allocation Count check for QueueP_delete
3. Added test for zero Allocation count check for Heap_delete
Signed-off-by: Asha <x1101668@ti.com>
1. Added Negative testcase for Hwi Submodule
- OsalApp_hwiDeleteNegativeTest
2. Added test for zero Allocation Count check for QueueP_delete
3. Added test for zero Allocation count check for Heap_delete
Signed-off-by: Asha <x1101668@ti.com>
[OSAL]: Added new testcases for Debug sub module
- DebugNegativeTest
Signed-off-by: Sangeetha Duraisamy <x1096604@ti.com>
- DebugNegativeTest
Signed-off-by: Sangeetha Duraisamy <x1096604@ti.com>
I2C_extended_testapp: added test cases
-I2C_test Wakeup Enable/disable
Signed-off-by: Pradeepa Chandrashekar x1074845@ti.com
-I2C_test Wakeup Enable/disable
Signed-off-by: Pradeepa Chandrashekar x1074845@ti.com
Enable IPC extended app only for J784S4
- IPC extended app is not validated for all SOCs and all cores
- Inadvertently it was enabled for all SOCs and all cores
- Limited the app to j784s4 and mcu1_0 where this app is validated and working
Signed-off-by: Rishabh Garg <rishabh@ti.com>
- IPC extended app is not validated for all SOCs and all cores
- Inadvertently it was enabled for all SOCs and all cores
- Limited the app to j784s4 and mcu1_0 where this app is validated and working
Signed-off-by: Rishabh Garg <rishabh@ti.com>
Fix OSPI U-boot from SBL
- Linux tag 09.02.00.005 has some dma related issues which causes hang in
u-boot while booting from OSPI
- Updated U-boot binaries with 09.02.00.006 linux tag
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- Linux tag 09.02.00.005 has some dma related issues which causes hang in
u-boot while booting from OSPI
- Updated U-boot binaries with 09.02.00.006 linux tag
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
[SBL] Add SBL UART target for HS-FS devices for Secure HSM Boot
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
[PDK-13952][IPC]: Reset VRing queues after an RTOS firmware is shutting down.
- After RTOS firmware is shut down and reloaded, it does a VirtIO init.
- This resets all the queue indices at the remote core end.
- Self core should also reset its indices to stay in sync with the remote core.
- This is done after the remote RTOS core advertises that it is shutting down.
Signed-off-by: Mriganka Chakravarty <m-chakravarty@ti.com>
- After RTOS firmware is shut down and reloaded, it does a VirtIO init.
- This resets all the queue indices at the remote core end.
- Self core should also reset its indices to stay in sync with the remote core.
- This is done after the remote RTOS core advertises that it is shutting down.
Signed-off-by: Mriganka Chakravarty <m-chakravarty@ti.com>
[IPC] Added graceful shutdown feature
- Current IPC driver uses mailbox to send kick(interrupt) to remote processor
and actual message is written to vring memory
- Updated IPC driver to add callback in case remote processor sends actual
message via mailbox. This will be used for sending shutdown message
- Modified mailbox ISR to identify the mailbox message: do normal processing
if it is not a shutdown message. For shutdown message ensure all previous
messages are processed and then call the callback API, rpMboxMsgFxn
- Added the list of RP mailbox messages currently available in Linux
- In application callback ensured that all IPC tasks are unblocked so that core
can go to WFI
- Updated IPC example to invoke below sequence on receiving shutdown message:
* Close open drivers: Sciclient in this case
* Disable all interrupts
* Send shutdown ack to remote core (MPU in this case)
* Put the core to WFI
- Current IPC driver uses mailbox to send kick(interrupt) to remote processor
and actual message is written to vring memory
- Updated IPC driver to add callback in case remote processor sends actual
message via mailbox. This will be used for sending shutdown message
- Modified mailbox ISR to identify the mailbox message: do normal processing
if it is not a shutdown message. For shutdown message ensure all previous
messages are processed and then call the callback API, rpMboxMsgFxn
- Added the list of RP mailbox messages currently available in Linux
- In application callback ensured that all IPC tasks are unblocked so that core
can go to WFI
- Updated IPC example to invoke below sequence on receiving shutdown message:
* Close open drivers: Sciclient in this case
* Disable all interrupts
* Send shutdown ack to remote core (MPU in this case)
* Put the core to WFI
Fix Udma_assert typo
- Causing build errors for multiple SOCs including J722S.
- Introduced by bool/Bool updates.
Signed-off-by: Michael Nichols <m-nichols@ti.com>
- Causing build errors for multiple SOCs including J722S.
- Introduced by bool/Bool updates.
Signed-off-by: Michael Nichols <m-nichols@ti.com>
[PDK-13980] Fix Boot App OSPI
- Boot App OSPI uses sbl libraries
- Upon enabling DMA in the SBL, the SBL starts linking to the spi_dma
library instead of spi library. However, the boot app continues to
link to the standard spi library, resulting in a data mismatch when
reading from OSPI flash memory.
- Modified the code to link the spi_dma library instead of spi library
- Updated the fp_readData() function pointer to use Board_flashRead()
instead of memcpy because DMA is now enabled
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- Boot App OSPI uses sbl libraries
- Upon enabling DMA in the SBL, the SBL starts linking to the spi_dma
library instead of spi library. However, the boot app continues to
link to the standard spi library, resulting in a data mismatch when
reading from OSPI flash memory.
- Modified the code to link the spi_dma library instead of spi library
- Updated the fp_readData() function pointer to use Board_flashRead()
instead of memcpy because DMA is now enabled
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
PDK-13770: Board: Added return value check for Board MMR ctrl function
- Board_pinmuxKickCtrl function used to lock/unlock the PADCONFIG MMR
registers during pinmux configuration returns the lock/unlock status
which is not checked by pinmux config functions. In case of failure to
unlock the MMR registers, pinmux configuration will fail but proper
error status wont be sent to the calling function as the
Board_pinmuxKickCtrl function return is not checked.
- Updated pinmux config code to check the return value of
Board_pinmuxKickCtrl function and return proper status to the caller
functions.
- Board_pinmuxKickCtrl function used to lock/unlock the PADCONFIG MMR
registers during pinmux configuration returns the lock/unlock status
which is not checked by pinmux config functions. In case of failure to
unlock the MMR registers, pinmux configuration will fail but proper
error status wont be sent to the calling function as the
Board_pinmuxKickCtrl function return is not checked.
- Updated pinmux config code to check the return value of
Board_pinmuxKickCtrl function and return proper status to the caller
functions.
PDK-12063: Board: Removed unused board init macros
- Each bit of Board config parameter selects the functionality of Board init
API allowing maximum 32 different configurations. Board init macros
are used to select the config parameter. All the 32 bins
of the config parameter are currently in use and it is not possible to
add new functionality to Board init API to due to limitation of 32
board init flags/macros.
- There are multiple board config functionalities applicable to legacy
Jacinto platforms which are not currently supported in PDK. Removing
the board init macros related to legacy platforms to allow more board
init flags on J7 platforms.
- Each bit of Board config parameter selects the functionality of Board init
API allowing maximum 32 different configurations. Board init macros
are used to select the config parameter. All the 32 bins
of the config parameter are currently in use and it is not possible to
add new functionality to Board init API to due to limitation of 32
board init flags/macros.
- There are multiple board config functionalities applicable to legacy
Jacinto platforms which are not currently supported in PDK. Removing
the board init macros related to legacy platforms to allow more board
init flags on J7 platforms.
[PDK-13979][J721E] Fix lockstep boot test
- For J721E, Hardware does not support combining TCMs of the both the
cores while booting in lockstep mode
- Hardware support to combine TCMs of both the cores is added from J7200
onwards
- SBL_getAtcmSize and SBL_getBtcmSize return TCM memory sizes for split mode.
- Made the changes in code to use this API to get the memory for J721e while calling it twice
and summing it for other SOCs
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- For J721E, Hardware does not support combining TCMs of the both the
cores while booting in lockstep mode
- Hardware support to combine TCMs of both the cores is added from J7200
onwards
- SBL_getAtcmSize and SBL_getBtcmSize return TCM memory sizes for split mode.
- Made the changes in code to use this API to get the memory for J721e while calling it twice
and summing it for other SOCs
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
Fix Boot App failure on HS devices
- When the ‘shareable’ attribute in the MPU configuration is set to false
for DDR (Double Data Rate) memory, it effectively makes the DDR memory cacheable.
- Since DDR memory is cacheable, it is essential to perform cache write-back
operations before proceeding with the authentication step
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- When the ‘shareable’ attribute in the MPU configuration is set to false
for DDR (Double Data Rate) memory, it effectively makes the DDR memory cacheable.
- Since DDR memory is cacheable, it is essential to perform cache write-back
operations before proceeding with the authentication step
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
Enable Secure HSM Boot on HS-FS devices
- Since now SBL_loadAndAuthHsmBinary() is part of normal boot flow,
hsm.bin shouldn't present in boot media while booting GP device
- If hsm.bin is present in boot media while booting on GP device, tifs
tries to authenticate hsm.bin which leads to boot hang
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- Since now SBL_loadAndAuthHsmBinary() is part of normal boot flow,
hsm.bin shouldn't present in boot media while booting GP device
- If hsm.bin is present in boot media while booting on GP device, tifs
tries to authenticate hsm.bin which leads to boot hang
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
Fix Boot Performance Test
- Since PHY tuning time is included in boot performance test, Total Boot
time increased by "PHY Tuning Time"
- Increased the expected CAN response time by average "PHY Tuning Time"
i.e 8ms
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- Since PHY tuning time is included in boot performance test, Total Boot
time increased by "PHY Tuning Time"
- Increased the expected CAN response time by average "PHY Tuning Time"
i.e 8ms
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
Revert "Driver Changes for IPC late APIs"
This reverts commit 1200ed43891e4f707125b24bc4c286cd186ed433.
This reverts commit 1200ed43891e4f707125b24bc4c286cd186ed433.
Revert "ipc:enabling late APIs for J784s4 as those are used by EthFw."
This reverts commit ef39661427acb6bcea88960f2df92211ebf83974.
This reverts commit ef39661427acb6bcea88960f2df92211ebf83974.
PDK-13754: Board: Fix for MMR unlock on C66x core.
- Accessing the MMR registers on C66x core requires RAT configuration
with proper RAT offset. RAT configuration is being enabled but RAT
offset is not added to MMR register base address which is causing
the MMR unlock failure.
Corrected the base address to add RAT offset while executing on C66x
DSP core.
- Accessing the MMR registers on C66x core requires RAT configuration
with proper RAT offset. RAT configuration is being enabled but RAT
offset is not added to MMR register base address which is causing
the MMR unlock failure.
Corrected the base address to add RAT offset while executing on C66x
DSP core.
Fix: UDMA UT crash on C7x_2 while trying to L2SRAM
Issue:
Each C7x core has it's own internal L2SRAM, but in global linker file
the location L2SRAM points to C7SS0's L2SRAM and this address maynot be
accessable by other C7x cores. UDMA UT is crashing on C7x_2 while trying
to access L2SRAM.
Resolution:
Since no one use L2SRAM other than udma_ut in pdk, remove L2SRAM in
global linker file and create linker ammend files per core in UDMA UT.
Fixes: PDK-12463
Signed-off-by: Lohith Kumar <l-kumar@ti.com>
Issue:
Each C7x core has it's own internal L2SRAM, but in global linker file
the location L2SRAM points to C7SS0's L2SRAM and this address maynot be
accessable by other C7x cores. UDMA UT is crashing on C7x_2 while trying
to access L2SRAM.
Resolution:
Since no one use L2SRAM other than udma_ut in pdk, remove L2SRAM in
global linker file and create linker ammend files per core in UDMA UT.
Fixes: PDK-12463
Signed-off-by: Lohith Kumar <l-kumar@ti.com>
12 days ago[PDK-13792]: Updated conditional syntax in boardcfg_makefile to support windows build REL.PSDK.09.02.00.14
[PDK-13792]: Updated conditional syntax in boardcfg_makefile to support windows build
-Bash style string comparator syntax fails on a windows build
-Updated to use make condtional syntax to eliminate the error
Signed-off-by: S Likhith <likhith@ti.com>
-Bash style string comparator syntax fails on a windows build
-Updated to use make condtional syntax to eliminate the error
Signed-off-by: S Likhith <likhith@ti.com>
TSN: common: Update tsn library makefiles
Updated tsn library makefiles due to updates in
TSN Stack Libraries and resolved issues in jenkins
build.
Signed-off-by: duc <duc.tran@excelfore.com>
Updated tsn library makefiles due to updates in
TSN Stack Libraries and resolved issues in jenkins
build.
Signed-off-by: duc <duc.tran@excelfore.com>
TSN: NETCONF: Added TSN NETCONF and PUGIXML Makefiles
- Added makefile_pugixml and makefile_tsn_netconf to build
pugixml and tsn_netconf libraries
- Updated tsn_component.mk to add pugixml and tsn_netconf
components
Signed-off-by: Allan Co <allanrodrigo.co@excelfore.com>
- Added makefile_pugixml and makefile_tsn_netconf to build
pugixml and tsn_netconf libraries
- Updated tsn_component.mk to add pugixml and tsn_netconf
components
Signed-off-by: Allan Co <allanrodrigo.co@excelfore.com>
TSN: Common: Support cpp file compilation in PDK
- Updated common.mk and rules_ti_cgt_arm.mk to handle compilation
of *.cpp file.
Signed-off-by: Allan Co <allanrodrigo.co@excelfore.com>
- Updated common.mk and rules_ti_cgt_arm.mk to handle compilation
of *.cpp file.
Signed-off-by: Allan Co <allanrodrigo.co@excelfore.com>
[SYSFW-6825] Update hsm.bin file
- With the existing hsm.bin file, able to boot from hs-se devices and
not from hs-fs devices
- Received an updated hsm.bin file from the System Firmware (SysFW) team,
which now enables booting from both HS-SE and HS-FS devices.
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- With the existing hsm.bin file, able to boot from hs-se devices and
not from hs-fs devices
- Received an updated hsm.bin file from the System Firmware (SysFW) team,
which now enables booting from both HS-SE and HS-FS devices.
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
[PDK-13744] Add performance test for SBL OSPI nand
- Added PHY tuning time to the SBL performance numbers
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- Added PHY tuning time to the SBL performance numbers
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
[PDK-13745][PDK-13535][SBL] Enable PHY tuning, DMA for OSPI NOR and
OSPI NAND
- Enabled DMA for OSPI SBL targets
- Instead of defining configurations explicitly in SBL, default
configurations were used for OSPI
- Added comments for profiling points
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
OSPI NAND
- Enabled DMA for OSPI SBL targets
- Instead of defining configurations explicitly in SBL, default
configurations were used for OSPI
- Added comments for profiling points
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
UART: Add a wrapper function for getting data from UART console using interrupts.
Add UART_getc2() function for leveraging the UART_read() API which
checks if interrupts are enabled and falls back to UART_readPolling() if not enabled,
supporting both modes of UART read.
Signed-off-by: Meghana Malladi <m-malladi@ti.com>
Add UART_getc2() function for leveraging the UART_read() API which
checks if interrupts are enabled and falls back to UART_readPolling() if not enabled,
supporting both modes of UART read.
Signed-off-by: Meghana Malladi <m-malladi@ti.com>
[I2C]:I2C_Extended TestApp:added test cases
-i2c_Negative test: configured Rx and Tx FIFO threshold value and clear the FIFO.
Signed-off-by: Pradeepa Chandrashekar x1074845@ti.com
-i2c_Negative test: configured Rx and Tx FIFO threshold value and clear the FIFO.
Signed-off-by: Pradeepa Chandrashekar x1074845@ti.com
[OSAL]: Added new testcases for Semaphore sub module
- OsalApp_semaphoreNullTest
- OsalApp_semaphorePendTest
- OsalApp_semaphoreMaxTest
Signed-off-by: Asha <x1101668@ti.com>
- OsalApp_semaphoreNullTest
- OsalApp_semaphorePendTest
- OsalApp_semaphoreMaxTest
Signed-off-by: Asha <x1101668@ti.com>
UDMA_UT: Add testcases for Udma Channel APIs
- Corrected runflags for Rm Uhc test cases
- Restored instType for test cases in udma_test_proxy_neg.c
- Fixed variables for Uhc resource channels assigned in udma_test_common.c
- Implemented test cases in UDMA_UT test app for UDMA Channel API's
1.UdmaChConfigPdmaTestNeg-PDK-13699
2.UdmaChConfigPdmaTest-PDK-13834
3.UdmaChConfigRxTestNeg-PDK-13700
4.UdmaChEnableTestNeg-PDK-13698
5.UdmaTestChGetTdCqRingHandle-PDK-13738
6.UdmaTestChGetFqRingNum-PDK-13739
Signed-off-by: Sushmi x1123751@ti.com
- Corrected runflags for Rm Uhc test cases
- Restored instType for test cases in udma_test_proxy_neg.c
- Fixed variables for Uhc resource channels assigned in udma_test_common.c
- Implemented test cases in UDMA_UT test app for UDMA Channel API's
1.UdmaChConfigPdmaTestNeg-PDK-13699
2.UdmaChConfigPdmaTest-PDK-13834
3.UdmaChConfigRxTestNeg-PDK-13700
4.UdmaChEnableTestNeg-PDK-13698
5.UdmaTestChGetTdCqRingHandle-PDK-13738
6.UdmaTestChGetFqRingNum-PDK-13739
Signed-off-by: Sushmi x1123751@ti.com
Updated PDK makerules
Signed-off-by: Rishabh Garg <rishabh@ti.com>
Signed-off-by: Rishabh Garg <rishabh@ti.com>
[PDK-13916][DSS]: Fixing failure on DSS m2m test
Reverting the Comparision done in the App_create API for the createStatus
Signed-off-by: Asha <x1101668@ti.com>
Reverting the Comparision done in the App_create API for the createStatus
Signed-off-by: Asha <x1101668@ti.com>
Migrating to TIFS version v09.02.04
Signed-off-by: Chandru Dhavamani <chandru@ti.com>
Signed-off-by: Chandru Dhavamani <chandru@ti.com>
[PDK-13575] Fix typos in MMCSD driver
- For HS_TIMING, drive strength should be programmed instead of enhanced
strobe.
- Changed enhancedStrobe to drvStrength for HS_TIMING
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- For HS_TIMING, drive strength should be programmed instead of enhanced
strobe.
- Changed enhancedStrobe to drvStrength for HS_TIMING
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
[PDK-11514] Add test case to ensure cores are switched off if no
application image
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
application image
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
Update linux binaries with 09.02.00.005 tag after manually updating
device tree
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
device tree
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
ipc:enabling late APIs for J784s4 as those are used by EthFw.
Signed-off-by: Sonu Alam <s-alam@ti.com>
Signed-off-by: Sonu Alam <s-alam@ti.com>
[sysfw]: Update j721e tifs binary
Update tifs hs and hs-fs binary for j721e
for sysfw release 09.02.02.
Signed-off-by: Chandru Dhavamani <chandru@ti.com>
Update tifs hs and hs-fs binary for j721e
for sysfw release 09.02.02.
Signed-off-by: Chandru Dhavamani <chandru@ti.com>
Driver Changes for IPC late APIs
- Enabled IPC Late APIs with SOC specific macros.
- These APIs are used by lpm driver only for J7200 and J721E.
Signed-off-by: Likhitha <x1097556@ti.com>
- Enabled IPC Late APIs with SOC specific macros.
- These APIs are used by lpm driver only for J7200 and J721E.
Signed-off-by: Likhitha <x1097556@ti.com>
[OSPI] bool/Bool implementation
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Swap the constant operands to the right of the comparison operators to avoid miss assignment of values
Signed-off-by: Asha <x1101668@ti.com>
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Swap the constant operands to the right of the comparison operators to avoid miss assignment of values
Signed-off-by: Asha <x1101668@ti.com>
[UDMA] bool/Bool implementation
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
[UDMA_UTILS]: bool/Bool implementation
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
Osal: Increase max supported mutex number per soc to 32U.
While running ETHFW with TSN, it demands around 20-22 mutexes;
exhausting the existing supported max mutex number, hence increasing
it to 32U in J721E, J7200, J784S4 and J721S2
Signed-off-by: Meghana Malladi <m-malladi@ti.com>
While running ETHFW with TSN, it demands around 20-22 mutexes;
exhausting the existing supported max mutex number, hence increasing
it to 32U in J721E, J7200, J784S4 and J721S2
Signed-off-by: Meghana Malladi <m-malladi@ti.com>
Update Linux Binaries with 09.02.00.005
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
[I2C] bool and unsigned macro implementation
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Swap the constant operands to the right of the comparison operators to aviod miss assignment of values
Signed-off-by: Asha <x1101668@ti.com>
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Swap the constant operands to the right of the comparison operators to aviod miss assignment of values
Signed-off-by: Asha <x1101668@ti.com>
[OSAL] bool and unsigned macros implementation
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
[UART] bool and unsigned macros implementation
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
[DSS] bool and unsigned macros implementation
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Swap the constant operands to the right of the comparison operators to aviod miss assignment of values
Signed-off-by: Asha <x1101668@ti.com>
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Swap the constant operands to the right of the comparison operators to aviod miss assignment of values
Signed-off-by: Asha <x1101668@ti.com>
[KERNEL] bool and unsigned macros implementation
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now defined BTRUE/BFALSE macros for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now defined BTRUE/BFALSE macros for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
UDMA_UT : Add testcases for UDMA Channel
Implemented test cases in UDMA_UT test app for UDMA Channel API's
1.UdmaChGetStatsTestNeg-PDK-13689
2.UdmaChDisableTestNeg-PDK-13690
3.UdmaChDisableTest-PDK-13826
4.UdmaChResumeTestNeg-PDK-13692
5.UdmaTestChOpenNeg-PDK-13584
Signed-off-by: Sushmi x1123751@ti.com
Implemented test cases in UDMA_UT test app for UDMA Channel API's
1.UdmaChGetStatsTestNeg-PDK-13689
2.UdmaChDisableTestNeg-PDK-13690
3.UdmaChDisableTest-PDK-13826
4.UdmaChResumeTestNeg-PDK-13692
5.UdmaTestChOpenNeg-PDK-13584
Signed-off-by: Sushmi x1123751@ti.com
3 weeks agoAdd sciclient extended unit testapp for dynamic code coverage REL.PSDK.09.02.00.07 REL.PSDK.09.02.00.08
Add sciclient extended unit testapp for dynamic code coverage
- Removed existing tests for the following files from sciclient unit testapp and included in sciclient extended unit testapp
- sciclient_pm.c
- sciclient_genericMsgs.c
- sciclient_keywriter.c
- sciclient_dkek.c
- Testcase names with App_* are replaced with SciclientApp_*
Signed-off-by: ChandrakantB <x1109162@ti.com>
- Removed existing tests for the following files from sciclient unit testapp and included in sciclient extended unit testapp
- sciclient_pm.c
- sciclient_genericMsgs.c
- sciclient_keywriter.c
- sciclient_dkek.c
- Testcase names with App_* are replaced with SciclientApp_*
Signed-off-by: ChandrakantB <x1109162@ti.com>
Fixes "Boot performance test reports high numbers"
- Sciclient_pmSetModuleClkParent API is returning failure if sciclient
is initializes with DEVGRP_00.
- Skip the step of change parent clock of the input muxed clock to A72
core in Boot Perf SBL target. Since this is needed only for Linux boot
- This commit can be reverted after fixing PDK-13497
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- Sciclient_pmSetModuleClkParent API is returning failure if sciclient
is initializes with DEVGRP_00.
- Skip the step of change parent clock of the input muxed clock to A72
core in Boot Perf SBL target. Since this is needed only for Linux boot
- This commit can be reverted after fixing PDK-13497
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
Migrating to TIFS version v09.02.03
Signed-off-by: Chandru Dhavamani <chandru@ti.com>
Signed-off-by: Chandru Dhavamani <chandru@ti.com>
[FATFS] bool and unsigned macros implementation
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
[MMCSD] bool and unsigned macros implementation
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
[BOOT] bool and unsigned macros implementation
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
previously we have used TRUE/FALSE macros both as boolean and unsigned int
Now BTRUE/BFALSE macros gets used for boolean implementation and UTRUE/UFALSE macros for the unsigned int implementation
Signed-off-by: Asha <x1101668@ti.com>
[BOARD]Including the CSL header file where required
bool/Bool implemetation in the following path
ti/board/utils/
ti/board/diag/
ti/board/src/devices/
ti/board/src/flash
ti/board/src/j784s4_evm/
ti/board/src/j721s2_evm/
ti/board/src/j7200_evm/
ti/board/src/j721e_evm/
Swap the constant operands to the left of the comparison operators to aviod miss assignment of values
Fixing datatypes of the operands to be same while comparing and when required in the functions to avoid MISRAC issues.
Signed-off-by: Asha <x1101668@ti.com>
bool/Bool implemetation in the following path
ti/board/utils/
ti/board/diag/
ti/board/src/devices/
ti/board/src/flash
ti/board/src/j784s4_evm/
ti/board/src/j721s2_evm/
ti/board/src/j7200_evm/
ti/board/src/j721e_evm/
Swap the constant operands to the left of the comparison operators to aviod miss assignment of values
Fixing datatypes of the operands to be same while comparing and when required in the functions to avoid MISRAC issues.
Signed-off-by: Asha <x1101668@ti.com>
Hard Code ATCM, BTCM sizes in SBL
- Since ATCM, BTCM sizes are incorrect in CSLR macros, as a workaround
hardcoded the correct sizes in SBL
- This commit should be reverted after fixing PDK-13842
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- Since ATCM, BTCM sizes are incorrect in CSLR macros, as a workaround
hardcoded the correct sizes in SBL
- This commit should be reverted after fixing PDK-13842
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
[PDK-13747] Fix BootApp boot issue in lockstep
- Since Boot core (mcu1_0) does not provide the TCM sizes of other R5 cores,
used CSL macros to find them
- When the core boots in lockstep mode, the TCM size is the total of the
TCM sizes of each core
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- Since Boot core (mcu1_0) does not provide the TCM sizes of other R5 cores,
used CSL macros to find them
- When the core boots in lockstep mode, the TCM size is the total of the
TCM sizes of each core
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
[MAKERULES] Turning off C7x CGT compiler advice
- Applicable from 4.x CGT onwards
Signed-off-by: Shyam Jagannathan <shyam.jagannathan@ti.com>
- Applicable from 4.x CGT onwards
Signed-off-by: Shyam Jagannathan <shyam.jagannathan@ti.com>
[OSAL] Fix MISRAC C issue with checker code MISRA.ETYPE.ASSIGN.2012
Signed-off-by: Asha <x1101668@ti.com>
Signed-off-by: Asha <x1101668@ti.com>
Add sciserver unit testapp for dynamic code coverage
- Testcases are added for following files in sciserver unit testapp
- sciserver_secproxyRoutingDescription.c
- sciserver_secproxyTransfer.c
- sciserver.c
Signed-off-by: ChandrakantB <x1109162@ti.com>
- Testcases are added for following files in sciserver unit testapp
- sciserver_secproxyRoutingDescription.c
- sciserver_secproxyTransfer.c
- sciserver.c
Signed-off-by: ChandrakantB <x1109162@ti.com>
Removed unused IPC mailbox ISR APIs
Signed-off-by: Rishabh Garg <rishabh@ti.com>
Signed-off-by: Rishabh Garg <rishabh@ti.com>
Removed dead code from IPC driver
- IPC driver is based on interrupt and Sciclient
- Removed dead code to run it in polling mode without Sci
- Removed mailbox lld files needed for AM64
Signed-off-by: Rishabh Garg <rishabh@ti.com>
- IPC driver is based on interrupt and Sciclient
- Removed dead code to run it in polling mode without Sci
- Removed mailbox lld files needed for AM64
Signed-off-by: Rishabh Garg <rishabh@ti.com>
Corrected C7x compiler version
Signed-off-by: Jahnavi Guvvala <j-guvvala@ti.com>
Signed-off-by: Jahnavi Guvvala <j-guvvala@ti.com>
[PDK-13563] Fix Linux boot issue from SBL and BootApp with latest device
tree
- The input muxed clock DEV_MAIN_PLL8_SEL_EXTWAVE_VD_CLK, which feeds the
A72 core, is set by default to use the parent clock
DEV_MAIN_PLL8_SEL_EXTWAVE_VD_CLK_PARENT_PLLFRACF_SSMOD_16FFT_MAIN_8_FOUTVCOP_CLK
- The A72 core frequency cannot be changed at run time when the parent clock is
DEV_MAIN_PLL8_SEL_EXTWAVE_VD_CLK_PARENT_PLLFRACF_SSMOD_16FFT_MAIN_8_FOUTVCOP_CLK,
which has no dividers. This causes Linux boot to hang
- The input muxed clock DEV_MAIN_PLL8_SEL_EXTWAVE_VD_CLK, which is connected to
the A72 core, needs the parent clock
DEV_MAIN_PLL8_SEL_EXTWAVE_VD_CLK_PARENT_HSDIV0_16FFT_MAIN_8_HSDIVOUT0_CLK to change
the A72 core frequency at run time
- This change is needed for both SBL target and SBL HLOS target, since linux
boots from SBL HLOS target and SBL target (in case of BootApp)
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
tree
- The input muxed clock DEV_MAIN_PLL8_SEL_EXTWAVE_VD_CLK, which feeds the
A72 core, is set by default to use the parent clock
DEV_MAIN_PLL8_SEL_EXTWAVE_VD_CLK_PARENT_PLLFRACF_SSMOD_16FFT_MAIN_8_FOUTVCOP_CLK
- The A72 core frequency cannot be changed at run time when the parent clock is
DEV_MAIN_PLL8_SEL_EXTWAVE_VD_CLK_PARENT_PLLFRACF_SSMOD_16FFT_MAIN_8_FOUTVCOP_CLK,
which has no dividers. This causes Linux boot to hang
- The input muxed clock DEV_MAIN_PLL8_SEL_EXTWAVE_VD_CLK, which is connected to
the A72 core, needs the parent clock
DEV_MAIN_PLL8_SEL_EXTWAVE_VD_CLK_PARENT_HSDIV0_16FFT_MAIN_8_HSDIVOUT0_CLK to change
the A72 core frequency at run time
- This change is needed for both SBL target and SBL HLOS target, since linux
boots from SBL HLOS target and SBL target (in case of BootApp)
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
4 weeks agoupdate ti_cgt_c7000 compiler from 3.1.0LTS to 4.1.0B1 REL.PSDK.09.02.00.04 REL.PSDK.09.02.00.05
update ti_cgt_c7000 compiler from 3.1.0LTS to 4.1.0B1
Signed-off-by: Jahnavi Guvvala <j-guvvala@ti.com>
Signed-off-by: Jahnavi Guvvala <j-guvvala@ti.com>
5 weeks ago[OSAL] Added new TaskP_getTaskStackHighWatermark function REL.PSDK.09.02.00.02 REL.PSDK.09.02.00.03
[OSAL] Added new TaskP_getTaskStackHighWatermark function
- Added new function so that application software can easily
query the high watermarks of each of the task stacks
- This leverages freertos function, not available on safertos,
so returning 0 for safertos version.
- Enabling for all freertos configurations
- Added new function so that application software can easily
query the high watermarks of each of the task stacks
- This leverages freertos function, not available on safertos,
so returning 0 for safertos version.
- Enabling for all freertos configurations
[I2C]: i2c_extended_testapp: added test cases:
- i2c_callBack mode test
- i2c_Negative test cases
Signed-off-by: Pradeepa Chandrashekar x1074845@ti.com
- i2c_callBack mode test
- i2c_Negative test cases
Signed-off-by: Pradeepa Chandrashekar x1074845@ti.com
[OSAL] : Driver changes in Semaphore Sub module
for APIs
- Removed double null check for SemaphoreP_Params_init and SemaphoreP_delete APIs
- Removed Assert condition and added Null check condition for the Semaphore_post and SemaphoreP_getCount APIs
Signed-off-by: Asha <x1101668@ti.com>
for APIs
- Removed double null check for SemaphoreP_Params_init and SemaphoreP_delete APIs
- Removed Assert condition and added Null check condition for the Semaphore_post and SemaphoreP_getCount APIs
Signed-off-by: Asha <x1101668@ti.com>
[PDK-13591][OSAL]: Change event ID for ExtBlock test for C66x
- c66xdsp_2 event ID used in ExtBlock test clashes with event id used prior to the ExtBlock test.
- This test was disabled for Jacinto devices, and hence the issue did not surface.
- The test was enabled recently.
- Change the event ID for the test on C66x to avoid clash.
Signed-off-by: Mriganka Chakravarty <m-chakravarty@ti.com>
- c66xdsp_2 event ID used in ExtBlock test clashes with event id used prior to the ExtBlock test.
- This test was disabled for Jacinto devices, and hence the issue did not surface.
- The test was enabled recently.
- Change the event ID for the test on C66x to avoid clash.
Signed-off-by: Mriganka Chakravarty <m-chakravarty@ti.com>
UDMA_UT: Add testcases for UDMA RM
Implemented test cases in UDMA_UT test app for UDMA RM API's
1.UdmaRmFreeBlkCopyUhcChTest-PDK-13776
2.UdmaRmFreeTxHcChTest-PDK-13777
3.UdmaRmFreeTxUhcChTest-PDK-13778
4.UdmaRmFreeRxUhcChTest-PDK-13779
5.UdmaRmInitPrmsinitTestNeg-PDK-13780
Signed-off-by: Sushmi x1123751@ti.com
Implemented test cases in UDMA_UT test app for UDMA RM API's
1.UdmaRmFreeBlkCopyUhcChTest-PDK-13776
2.UdmaRmFreeTxHcChTest-PDK-13777
3.UdmaRmFreeTxUhcChTest-PDK-13778
4.UdmaRmFreeRxUhcChTest-PDK-13779
5.UdmaRmInitPrmsinitTestNeg-PDK-13780
Signed-off-by: Sushmi x1123751@ti.com
UDMA_UT : Add UDMA DRU testcases
- Implemented test cases in UDMA_UT test app for UDMA DRU API's
1.UdmaTestDruGetNumNeg - PDK-13686
2.UdmaTestDruQueueConfigNeg - PDK-13687
3.UdmaTestDruGetTriggerRegAddrNeg - PDK-13688
4.UdmaTestDruGetTriggerRegAddr - PDK-13755
Signed-off-by: swetha <x1081792@ti.com>
- Implemented test cases in UDMA_UT test app for UDMA DRU API's
1.UdmaTestDruGetNumNeg - PDK-13686
2.UdmaTestDruQueueConfigNeg - PDK-13687
3.UdmaTestDruGetTriggerRegAddrNeg - PDK-13688
4.UdmaTestDruGetTriggerRegAddr - PDK-13755
Signed-off-by: swetha <x1081792@ti.com>
Cleanup of sciclient examples
- The functions and variable names with App_sciclient* are replaced with SciApp_* in all the sciclient examples
- Reordering of inclusion of header files
- Removal of tirtos and AM6x related code
- Comments are updated in sci_app_common.c, sci_app_common.h files
- Function descriptions are corrected
- sciclient_firmware_boot_TestApp is changed to sciclient_firmware_boot_testapp
Signed-off-by: ChandrakantB <x1109162@ti.com>
- The functions and variable names with App_sciclient* are replaced with SciApp_* in all the sciclient examples
- Reordering of inclusion of header files
- Removal of tirtos and AM6x related code
- Comments are updated in sci_app_common.c, sci_app_common.h files
- Function descriptions are corrected
- sciclient_firmware_boot_TestApp is changed to sciclient_firmware_boot_testapp
Signed-off-by: ChandrakantB <x1109162@ti.com>
[PDK-13763][Sciclient]: Fix return value in osal_hwip_restore()
osal_hwip_restore() function uses a return keyword for a void function.
Hence removed the return keyword from this function.
Signed-off-by: Thejasvi Konduru <t-konduru@ti.com>
osal_hwip_restore() function uses a return keyword for a void function.
Hence removed the return keyword from this function.
Signed-off-by: Thejasvi Konduru <t-konduru@ti.com>
UDMA_UT : Add testcases for UDMA Channel
Implemented test cases in UDMA_UT test app for UDMA Channel API's
1.UdmaTestChPauseNeg-PDK-13583
2.UdmaTestChOpenNeg-PDK-13584
3.UdmaTestChCloseNeg-PDK-13585
4.UdmaTestChConfigTxNeg-PDK-13586
5.UdmaTestChGetDefaultFlowHandleNeg-PDK-13587
6.UdmaTestChGetTdCqRingHandleNeg-PDK-13588
7.UdmaTestChGetFqRingNumNeg-PDK-13589
8.UdmaTestChGetCqRingNumNeg-PDK-13691
9.UdmaTestChGetTriggerEventNeg-PDK-13693
10.UdmaTestChSetSwTriggerNeg-PDK-13694
11.UdmaTestChSetChainingNeg-PDK-135695
12.UdmaTestChBreakChainingNeg-PDK-13696
13.UdmaTestChGetNumNeg-PDK-13697
14.UdmaTestChConfigUtcTestNeg-PDK-13701
15.UdmaTestChSetSwTriggerChTypeNeg-PDK-13703
16.UdmaTestChPause-PDK-13736
17.UdmaTestChGetDefaultFlowHandle-PDK-13737
18.UdmaTestChDisableDruNeg-PDK-13702
19.UdmaTestChPauseDruNeg-PDK-13771
20.UdmaTestChConfigUtcDruTestNeg-PDK-13772
21.UdmaTestChSetSwTriggerDruNeg-PDK-13773
Signed-off-by: Sushmi x1123751@ti.com
Implemented test cases in UDMA_UT test app for UDMA Channel API's
1.UdmaTestChPauseNeg-PDK-13583
2.UdmaTestChOpenNeg-PDK-13584
3.UdmaTestChCloseNeg-PDK-13585
4.UdmaTestChConfigTxNeg-PDK-13586
5.UdmaTestChGetDefaultFlowHandleNeg-PDK-13587
6.UdmaTestChGetTdCqRingHandleNeg-PDK-13588
7.UdmaTestChGetFqRingNumNeg-PDK-13589
8.UdmaTestChGetCqRingNumNeg-PDK-13691
9.UdmaTestChGetTriggerEventNeg-PDK-13693
10.UdmaTestChSetSwTriggerNeg-PDK-13694
11.UdmaTestChSetChainingNeg-PDK-135695
12.UdmaTestChBreakChainingNeg-PDK-13696
13.UdmaTestChGetNumNeg-PDK-13697
14.UdmaTestChConfigUtcTestNeg-PDK-13701
15.UdmaTestChSetSwTriggerChTypeNeg-PDK-13703
16.UdmaTestChPause-PDK-13736
17.UdmaTestChGetDefaultFlowHandle-PDK-13737
18.UdmaTestChDisableDruNeg-PDK-13702
19.UdmaTestChPauseDruNeg-PDK-13771
20.UdmaTestChConfigUtcDruTestNeg-PDK-13772
21.UdmaTestChSetSwTriggerDruNeg-PDK-13773
Signed-off-by: Sushmi x1123751@ti.com
[IPC] Fixing build error
- added #ifdef __cplusplus
Signed-off-by: Likhitha <x1097556@ti.com>
- added #ifdef __cplusplus
Signed-off-by: Likhitha <x1097556@ti.com>
[IPC] Fixing build error due to new line not present
CSL Refactoring for IPC
- Moved mailbox ip from CSL to IPC driver
Signed-off-by: Likhitha <x1097556@ti.com>
- Moved mailbox ip from CSL to IPC driver
Signed-off-by: Likhitha <x1097556@ti.com>
Adding support for new sciclient messages to request firewall access
IPC: Added Negative test cases
-These test cases cover IPC API failures for invalid configuration or parameters. Tests return error code and message upon failure.
1. Tested Virtio enable and disable Callback functions with NULL
parameters.
2. Moved Virtio_enableCallback and Virtio_disableCallback function
declarations to ipc_virtioPrivate.h to avoid -werrors.
Signed-off-by: Likhitha <x1097556@ti.com>
-These test cases cover IPC API failures for invalid configuration or parameters. Tests return error code and message upon failure.
1. Tested Virtio enable and disable Callback functions with NULL
parameters.
2. Moved Virtio_enableCallback and Virtio_disableCallback function
declarations to ipc_virtioPrivate.h to avoid -werrors.
Signed-off-by: Likhitha <x1097556@ti.com>
[OSAL]: Added new testcase for Memory Sub-Module
Signed-off-by: Sangeetha Duraisamy <x1096604@ti.com>
Signed-off-by: Sangeetha Duraisamy <x1096604@ti.com>
[PDK-13765][rm_pm_hal]: Enable Query firmware capability
Query Firmware Capability function is defined inside rm_pm_hal
module. Enable this feature in rm_pm_hal_build makefile.
Signed-off-by: Chandru Dhavamani <chandru@ti.com>
Query Firmware Capability function is defined inside rm_pm_hal
module. Enable this feature in rm_pm_hal_build makefile.
Signed-off-by: Chandru Dhavamani <chandru@ti.com>
[PDK-13711][OSAL]: Set gLoadP_initDone to true once LoadP is initialized.
- gLoadP_initDone was inadvertently set to false in this commit: 5ec15ff7ae5
- Set gLoadP_initDone to true once LoadP is initialized.
Signed-off-by: Mriganka Chakravarty <m-chakravarty@ti.com>
- gLoadP_initDone was inadvertently set to false in this commit: 5ec15ff7ae5
- Set gLoadP_initDone to true once LoadP is initialized.
Signed-off-by: Mriganka Chakravarty <m-chakravarty@ti.com>
[OSAL]: Removing Assert by adding Null checks in the below mentioned sub-modules
- MutexP nonos
- Semaphore nonos and safertos
- EventP Safertos
Signed-off-by: Asha <x1101668@ti.com>
- MutexP nonos
- Semaphore nonos and safertos
- EventP Safertos
Signed-off-by: Asha <x1101668@ti.com>
[PDK-11875] J784S4 DDR Config Optimiztion Update
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
[PDK-12198] Fix MMCSD/eMMC Performance numbers
- Used GTC timer instead of PMU counter to profile. Since PMU counter
halts during idle task.
- During a performance test, data is being copied to an SD/eMMC device
in interrupt mode using DMA. While the copy is in progress, the processor’s R5 core
is idle and the PMU counter is not running. As a result, the PMU counter may return inaccurate timings
- Enabled HS400 test on eMMC regression test
- Removed unused functions/macros/variables, used camel casing for variable/function declaration
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
- Used GTC timer instead of PMU counter to profile. Since PMU counter
halts during idle task.
- During a performance test, data is being copied to an SD/eMMC device
in interrupt mode using DMA. While the copy is in progress, the processor’s R5 core
is idle and the PMU counter is not running. As a result, the PMU counter may return inaccurate timings
- Enabled HS400 test on eMMC regression test
- Removed unused functions/macros/variables, used camel casing for variable/function declaration
Signed-off-by: Sai Ramakurthi <s-ramakurthi@ti.com>
[OSAL] Added new testcases for the Sub-Modules
Restructuring extended testcases into module specific files for the mentioned Sub Modules :
1. HwiP Sub module
2. CacheP Sub module
3. MailboxP Sub module
4. TaskP Sub module
5. MutexP Sub module
3. QueueP Sub module
4. HeapP Sub module
Disabling C66 core for extended testApp
Signed-off-by: Asha <x1101668@ti.com>
Restructuring extended testcases into module specific files for the mentioned Sub Modules :
1. HwiP Sub module
2. CacheP Sub module
3. MailboxP Sub module
4. TaskP Sub module
5. MutexP Sub module
3. QueueP Sub module
4. HeapP Sub module
Disabling C66 core for extended testApp
Signed-off-by: Asha <x1101668@ti.com>
[PDK-13500][Sciclient]: Resolve incorrect disable of write protection in Sciclient_serviceSecureProxy API
gSciclient_writeInProgress is a binary semaphore which is used to control the access
of critical section in Sciclient_serviceSecureProxy(). Currently even after this
semaphore variable is disabled, the global variables such as pSciclient_secProxyCfg
in Sciclient_readThread32(), gSciclientHandle are accessed by the threads.
As the threads share the global variables, this makes the code thread unsafe.
Hence shifted the disabling of gSciclient_writeInProgress variable to a correct
position in the Sciclient_serviceSecureProxy().
Signed-off-by: Thejasvi Konduru <t-konduru@ti.com>
gSciclient_writeInProgress is a binary semaphore which is used to control the access
of critical section in Sciclient_serviceSecureProxy(). Currently even after this
semaphore variable is disabled, the global variables such as pSciclient_secProxyCfg
in Sciclient_readThread32(), gSciclientHandle are accessed by the threads.
As the threads share the global variables, this makes the code thread unsafe.
Hence shifted the disabling of gSciclient_writeInProgress variable to a correct
position in the Sciclient_serviceSecureProxy().
Signed-off-by: Thejasvi Konduru <t-konduru@ti.com>
[Sciclient]: Fix MISRAC issues
- 2 MISRAC issues fixed for checker code MISRA.ETYPE.CATEGORY.DIFFERENT.2012
Signed-off-by: ChandrakantB <x1109162@ti.com>
- 2 MISRAC issues fixed for checker code MISRA.ETYPE.CATEGORY.DIFFERENT.2012
Signed-off-by: ChandrakantB <x1109162@ti.com>
Fixed platform.mk to remove dead code left in makerules
- XDC cleanup had this code blob left which was changing lib extension for host emulation
- There was dead code left in previous commit
- Removed the dead code to ensure build
Signed-off-by: Rishabh Garg <rishabh@ti.com>
- XDC cleanup had this code blob left which was changing lib extension for host emulation
- There was dead code left in previous commit
- Removed the dead code to ensure build
Signed-off-by: Rishabh Garg <rishabh@ti.com>