fsl_fman_ucode_ls1043_r1.0_108_4_9.bin

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

fsl_fman_ucode_ls1043_r1.0_108_4_9.bin

跳至解决方案
1,838 次查看
zumengchen
Contributor III

Hi experts,

This fman file has been mentioned in QorIQ SDK 2.0 Documentation, Rev. 0, May 2016, which is 4.4.5.4 Frame Manager Microcode (FMan ucode). but I can't find it in QorIQLinuxSDKv2.0AARCH64IMAGE.iso, there are only the following two fman bin file:

ls1043ardb/fsl_fman_ucode_t2080_r1.1_106_4_18.bin

ls1043ardb/fsl_fman_ucode_t2080_r1.1_108_4_5.bin

The weird thing is the name here, why t2080?

I using this fman ucode, Mini-PCIe can't be seen. Something wrong, can you help me out, thanks a lot.

Cheers,

Zumeng

标签 (1)
标记 (1)
0 项奖励
回复
1 解答
1,395 次查看
ufedor
NXP Employee
NXP Employee

> The weird thing is the name here, why t2080?

These SOCs (T2080 and LS1043A) have the same FMan IP and share the same microcode.

> I using this fman ucode, Mini-PCIe can't be seen.

PCIe controller is completely independent of the FMan and its microcode.

在原帖中查看解决方案

0 项奖励
回复
2 回复数
1,395 次查看
zumengchen
Contributor III

Thanks a lot, good to know

0 项奖励
回复
1,396 次查看
ufedor
NXP Employee
NXP Employee

> The weird thing is the name here, why t2080?

These SOCs (T2080 and LS1043A) have the same FMan IP and share the same microcode.

> I using this fman ucode, Mini-PCIe can't be seen.

PCIe controller is completely independent of the FMan and its microcode.

0 项奖励
回复