How to resolve building problem Errors:Field 'Bits' could not be resolved

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

How to resolve building problem Errors:Field 'Bits' could not be resolved

跳至解决方案
1,229 次查看
13761826501
Contributor III

Hi,

    I've encountered a building problem that not block the building process to link and generate *.elf file. 

    I really wanna know the root cause to it, really appreciately if someone can help me.

The problem caused by following step:

1. First I wrote a structure object like below:

13761826501_0-1663244143890.png

2. second , create a variable by using this structure and click build, 

3. build process work around and *.elf file generated, but "Problems" shows errors like below:

13761826501_1-1663244277585.png

13761826501_2-1663244297758.png

4. That's really confused me a lot, so I try to deleted all errors and try buiding project again. This time NO such errors occurred in "Problems".

13761826501_3-1663244429307.png

 

13761826501_4-1663244438940.png

5. But those errors  reappeared in "Problems" after I open the C source file which use the structure described in the first step

No proofs point out that the structure was wrong, but why those errors about "Field XXX could not be resolved" triggered while these errors would not block the build process? thank you !

0 项奖励
回复
1 解答
1,196 次查看
13761826501
Contributor III

The target MCU is S32K146, Thank you also for presenting the reason for such a problem exist . Later I will check the update

在原帖中查看解决方案

0 项奖励
回复
2 回复数
1,197 次查看
13761826501
Contributor III

The target MCU is S32K146, Thank you also for presenting the reason for such a problem exist . Later I will check the update

0 项奖励
回复
1,215 次查看
jiri_kral
NXP Employee
NXP Employee

Hi, 

what's your S32DS Version and target MCU? 

 

Earlier versions of S32DS has known issue - for some projects the build generates false positive errors. The errors was shown only in S32DS (S32DS is based on Eclipse) - but target was build successfully. In later S32DS version was this issue fixed. 

 

Jiri

0 项奖励
回复