Error Occurring with S32Flashtool2.17

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Error Occurring with S32Flashtool2.17

ソリューションへジャンプ
1,952件の閲覧回数
dylee
Contributor II

Hello,

I am using the S32G-VNP-RDB2.

I have installed S32Flashtool2.17 and am trying to update uboot using this Flash Tool.

When using the Flash Tool, the test connection passes, but I encounter an error when clicking

'Upload target and algorithm to hardware'.

Progress: 100

Flash algo is loaded.

Error: Algorithm initialization is failed.

I would like to know the cause and solution for this issue.

Thank you.

 

 

0 件の賞賛
返信
1 解決策
1,846件の閲覧回数
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Thanks for your feedback.

On regards of the eMMC algorithm failing, seems to be a HW misconfiguration. This seems to be related to the following community thread, in which a solution was already provided:

Solved: S32 Flash Tool failure to establish communication with device - NXP Community

Might be of use.

As for S32FlashTool v2.17, we have no problem on loading the eMMC algorithm once the HW is configured correctly:

DanielAguirre_0-1716387857804.png

Please, let us know.

元の投稿で解決策を見る

0 件の賞賛
返信
5 返答(返信)
1,898件の閲覧回数
dylee
Contributor II

Thanks to the image you shared, I achieved the same results with the same settings.
I noticed the difference in settings between us through the screenshot you shared. I set the Algorithm to EMMC, while you set it to MX25UM51245G. I am not very familiar with Algorithms. Can you explain the various algorithms available, including MX25UM51245G? Or could you share related documentation?

0 件の賞賛
返信
1,873件の閲覧回数
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Thanks for your feedback.

In general, the algorithm refers to a specific Flash Memory. In the case of EMMC, this is a JEDEC standard, for which all eMMC memories should implement the same algorithm.

On regards of NOR Flash devices, they do not have a strict JEDEC standard, for which a specific algorithm needs to be used depending on the specific memory P/N. Under the RDB2, the NOR Flash memory P/N is the one we selected under the algorithm (MX25UM51245G), that is why we see no problem when loading the algorithm.

For more information, we can recommend looking into the doc folder available under the S32FlashTool main folder:

DanielAguirre_0-1716301428380.png

Please, let us know.

0 件の賞賛
返信
1,864件の閲覧回数
dylee
Contributor II

Thank you for your prompt feedback. I have an additional question regarding the information you provided in your response.

As you mentioned, I have confirmed that data is being stored correctly through the Nor Flash algorithm. However, when I select the eMMC model in the UI Tool I am using, it does not seem to function smoothly. I was wondering if you have tested the eMMC model at your end and if it works properly when selected. I would appreciate your insights on any potential issues related to algorithms or drivers specific to eMMC.

Furthermore, I would be grateful if you could provide detailed guidance on the steps I need to follow to perform a Flash Download on eMMC. It would be very helpful if you could explain the specific procedure, including any necessary files, tools, and settings.

0 件の賞賛
返信
1,847件の閲覧回数
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Thanks for your feedback.

On regards of the eMMC algorithm failing, seems to be a HW misconfiguration. This seems to be related to the following community thread, in which a solution was already provided:

Solved: S32 Flash Tool failure to establish communication with device - NXP Community

Might be of use.

As for S32FlashTool v2.17, we have no problem on loading the eMMC algorithm once the HW is configured correctly:

DanielAguirre_0-1716387857804.png

Please, let us know.

0 件の賞賛
返信
1,932件の閲覧回数
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Can you help us elaborate more on the steps you followed to get that outcome? We are unable to reproduce the behavior from our side:

DanielAguirre_0-1715952866288.png

Please, let us know.

0 件の賞賛
返信