Hello NXP Support Team,
We are currently working with the PFE driver (version 1.5.0) and PFE firmware (version 1.7.0) on S32G2 , we have a query on the function pfe_hw_feature_get_val from PFE driver 1.5.0 shown below:
/**
* @brief Reads value of the feature enable variable
* [in] feature Feature to read the value
* [out] val Value read from the DMEM
* @return EOK or an error code.
*/
errno_t pfe_hw_feature_get_val(const pfe_hw_feature_t *feature, uint8_t *val)
{
errno_t ret;
#if defined(PFE_CFG_NULL_ARG_CHECK)
if ((NULL == feature) || (NULL == val))
{
NXP_LOG_ERROR("NULL argument received\n");
ret = EINVAL;
}
else
#endif
{
NXP_LOG_ERROR("Getting feature value for: %s\n", feature->name);
*val = feature->val; // <----------- Value is set here
ret = EOK;
}
return ret;
}
We have observed that on S32G3, this function sets val to 1. Given that both the driver and feature name are the same on S32G2 and S32G3 (as referenced here: linux_1.5.0/sw/pfe_platform/hw/s32g/pfe_tmu_csr.c line 158 `if (FALSE == pfe_feature_mgr_is_available(PFE_HW_FEATURE_RUN_ON_G3))` ), we would like to confirm the correct value on S32G2.
Could you please clarify if this feature `drv_run_on_g3` should also be set to 1 on S32G2, or if there is a different expected value for that platform? Any guidance or documentation you can provide would be greatly appreciated.
Thank you for your time and assistance. we look forward to hearing from you.
Best regards,
hi,s153022
According to the definition in the source file, this is only applicable to the S32G3, it is recommended to check the driver and firmware user manual.
BR
Joey