Flashdriver 生成不一致

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Flashdriver 生成不一致

442 Views
Typedef_true_false
Contributor I

我使用相同的Flash Driver程序去生成Ramcode,分别在S32K118 和 S32K116平台上,依据SDK 他们的FLASHDriver程序可以是相同的,只需要调用时使用不同的SSDConfig配置,但是编译后生成的Flashdriver不同,142所生成的ramcode不能正常的使用,118所生成的ramcode可以正常的在 142 和 118上使用,编译参数与优化等级是一致的,但是142生成的ramcode 与 118生成的差距很大,这是什么原因导致的呢

0 Kudos
Reply
3 Replies

426 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@Typdedef_true_false

你可以看工程编译后的map文件,对比map文件可以看到每个api的大小和所在的位置。

不见得S32K11X和S32K14X的API是一样的,你可以自己比对。

0 Kudos
Reply

406 Views
Typedef_true_false
Contributor I

是的 我能理解理论上代码生成应该不一致,但是无法解释为什么使用118的flash driver能够在142上使用,制作142和118 flashdriver的方法都是相同的,为什么142 的无法正常运行。 flashdriver是参考的https://community.nxp.com/t5/S32K-Knowledge-Base/S32K-How-to-make-Flash-Driver-image/ta-p/1630873

Tags (1)
0 Kudos
Reply

403 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@Typedef_true_false

我没看到你的问题,你的意思你以相同的方式制作了S32K142的Flash Driver,但是运行失败是吗?

如果是这样的话,你可以看到这个链接中的demo就是基于S32K142制作的。

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2148021%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3EFlashdriver%20generation%20inconsistency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2148021%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3EI%20use%20the%20same%20Flash%20Driver%20program%20to%20generate%20Ramcode%2C%20respectively%2C%20in%20the%20S32K118%20and%20S32K116%20platform%2C%20according%20to%20the%20SDK%20their%20FLASHDriver%20program%20can%20be%20the%20same%2C%20only%20need%20to%20call%20with%20different%20SSDConfig%20configuration%2C%20but%20after%20compilation%20to%20generate%20Flashdriver%20is%20different%2C%20142%20generated%20ramcode%20can%20not%20be%20used%20normally%2C%20118%20generated%20ramcode%20can%20be%20used%20normally%20in%20142%20and%20118%2C%20the%20compilation%20parameters%20and%20optimization%20level%20is%20the%20same%2C%20but%20142%20generated%20ramcode%20and%20118%20generated%20ramcode%20is%20different%2C%20the%20compilation%20parameters%20and%20optimization%20level%20is%20the%20same.%20However%2C%20the%20compiled%20Flashdriver%20is%20different%2C%20the%20ramcode%20generated%20by%20142%20can%20not%20be%20used%20normally%2C%20the%20ramcode%20generated%20by%20118%20can%20be%20used%20normally%20on%20142%20and%20118%2C%20the%20compilation%20parameters%20and%20optimization%20level%20are%20the%20same%2C%20but%20the%20difference%20between%20the%20ramcode%20generated%20by%20142%20and%20118%20is%20very%20large%2C%20what%20is%20the%20reason%20for%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2149792%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Flashdriver%20%E7%94%9F%E6%88%90%E4%B8%8D%E4%B8%80%E8%87%B4%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2149792%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3EHi%40Typedef_true_fa%3C%2FSPAN%3E%3CWBR%20%2F%3E%3CSPAN%3El%3C%2FSPAN%3E%20se%3C%2FP%3E%0A%3CP%3EI%20didn't%20see%20your%20question%2C%20you%20mean%20you%20made%20the%20Flash%20Driver%20for%20S32K142%20in%20the%20same%20way%20but%20it%20failed%20to%20run%20right%3F%3C%2FP%3E%0A%3CP%3EIf%20so%2C%20you%20can%20see%20that%20the%20demo%20in%20this%20link%20is%20based%20on%20the%20S32K142.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2149773%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Flashdriver%20%E7%94%9F%E6%88%90%E4%B8%8D%E4%B8%80%E8%87%B4%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2149773%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3EYes%2C%20I%20can%20understand%20that%20in%20theory%20the%20code%20generation%20should%20be%20inconsistent%2C%20but%20I%20can't%20explain%20why%20the%20flash%20driver%20that%20uses%20the%20118%20works%20on%20the%20142%2C%20and%20why%20the%20142%20doesn't%20work%20correctly%20when%20the%20method%20of%20making%20both%20the%20142%20and%20118%20flashdrivers%20is%20the%20same.%20The%20flashdriver%20is%20referenced%20at%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2FS32K-Knowledge-Base%2FS32K-How-to-make-Flash-Driver-image%2Fta-p%2F1630873%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fcommunity.nxp.com%2Ft5%2FS32K-Knowledge-Base%2FS32K-How-to-make-Flash-Driver-image%2Fta-p%2F1630873%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2148170%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Flashdriver%20%E7%94%9F%E6%88%90%E4%B8%8D%E4%B8%80%E8%87%B4%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2148170%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3EHi%40Typdedef_true_f%3C%2FSPAN%3E%3CWBR%20%2F%3E%3CSPAN%3Ealse%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EYou%20can%20look%20at%20the%20map%20file%20after%20the%20project%20is%20compiled%20and%20compare%20the%20map%20file%20to%20see%20the%20size%20and%20location%20of%20each%20api.%3C%2FP%3E%0A%3CP%3EIt%20is%20not%20necessary%20that%20the%20APIs%20of%20S32K11X%20and%20S32K14X%20are%20the%20same%2C%20you%20can%20compare%20them%20yourself.%3C%2FP%3E%3C%2FLINGO-BODY%3E