When setting a total of 100 CanHardwareObject(HRH)

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

When setting a total of 100 CanHardwareObject(HRH)

跳至解决方案
926 次查看
kazuki
Contributor II

The sample software confirmed is Can_Llce_DS_Can2Can_S32G399A_M7.

The operation confirmation environment is as follows.
S32DS:Ver3.5 Build id: 240130 (Update 10)
Debug Probe:S32 Debug Probe
LLCE:S32G_LLCE_1_0_5_QLP1
PFE:PFE-DRV_S32G_M7_MCAL_RTM_1.0.0_QLP1
RTD:RTD_4.4_4.0.0
compiler:GCC v9.2
tresosStudio:Ver28.2
Board used: S32G-VNP-RDB3

I set a total of 100 CanHardwareObjects (HRH) with the following settings.
・PayloadSize: CAN_OBJECT_PL_64
・CanMBType: RECEIVE

(Can_Llce_DS_Can2Can_S32G399A_M7.mex was directly edited and added)

the following error occurred.

--------
Issue: The hardware platform does not include enough long (64B) message buffers in order to service all configured HRHs. Please decrease the number of HRHs and/or the number of long MB used by each HRHs.
Level: Error
Type: Tool problem
Tool: Peripherals
Origin: Peripherals
Resource: Sources
Information: The hardware platform does not include enough long (64B) message buffers in order to service all configured HRHs. Please decrease the number of HRHs and/or the number of long MB used by each HRHs.
--------
I was able to generate it by reducing some CanHardwareObject(HRH) according to the error contents.

I have the following questions.

LLCE_firmware_user_guide.pdf (UserGuide for LLCEfirmware Document Number: Rev1.0.5) has the following description.
1.2 LLCE features
support for up to 4096 reception message buffers, including 1700 buffers of 64 bytes size and 2396 buffers of 8
bytes size.

Based on the above information, I think adding 100 pieces is within the range, but are you aware of this?
What are the restrictions on the number of CanHardwareObject(HRH) settings?

0 项奖励
回复
1 解答
916 次查看
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Are you able to share a capture of the error being shown under your platform? Also, editing the *.mex directly not using Config Tools is not endorsed by NXP, since it could create undefined outcomes. We are able to see the error of 1700 max buffer if we try to exceed it:

DanielAguirre_0-1711377206469.png

But once we go back into the expected range, we don't see any errors:

DanielAguirre_1-1711377248431.png

Please, let us know.

在原帖中查看解决方案

0 项奖励
回复
1 回复
917 次查看
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Are you able to share a capture of the error being shown under your platform? Also, editing the *.mex directly not using Config Tools is not endorsed by NXP, since it could create undefined outcomes. We are able to see the error of 1700 max buffer if we try to exceed it:

DanielAguirre_0-1711377206469.png

But once we go back into the expected range, we don't see any errors:

DanielAguirre_1-1711377248431.png

Please, let us know.

0 项奖励
回复