hard fault after touchgfx::muldivu() called
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-11-05 3:25 PM - last edited on ‎2024-11-07 7:34 AM by GaetanGodart
Hello,
I am working on STM32F426 with TouchGFX. However, after I upgrade STM32CUBEIDE and TouchGFX to latest version, I got a hard fault error. In the stack information, it shows the hard fault happens after touchgfx::muldivu() called.
And in the fault analyzer, the fault is to attempt to perform a division by zero.
May I know if there is any way to solve it? Thanks.
Edit : fixed it
- Labels:
-
TouchGFX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-11-05 4:54 PM
Would be more helpful to describe what was the problem and how you fixed it - then anyone searching in the future could find it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-11-07 7:33 AM - edited ‎2024-11-07 7:34 AM
Hello @hbZhao ,
Indeed, it would be nice if you could briefly explain the issue you had and how you solved it! :smiling_face_with_smiling_eyes:
I have reverted your message to the original (before edit) so you don't have to rewrite it).
Regards,
Software engineer at ST (TouchGFX)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-11-07 7:40 AM
@hbZhao wrote:the fault is to attempt to perform a division by zero.
:
:
May I know if there is any way to solve it?
Don't attempt to divide by zero!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-11-07 8:25 AM
>>Don't attempt to divide by zero!
100% this..
And perhaps CHECK if this is a posibility, and perhaps use a number for the solution which isn't unrepresentable?
Up vote any posts that you find helpful, it shows what's working..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-11-15 4:23 AM
Hello @hbZhao ,
Have you been able to move forward with your issue?
Did you find where you were dividing by 0?
Regards,
Software engineer at ST (TouchGFX)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-11-15 4:48 AM - edited ‎2024-11-15 4:54 AM
Looks more deeply in the library, so probably from a parameter or table passed in. Or corruption to said table or structure.
The call tree might be the most enlightening at this depth. Or some asserts to catch impending failure earlier.
Some thing where you expect a list with 2 elements but pass only one? N-1
Up vote any posts that you find helpful, it shows what's working..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-11-25 6:25 AM
Hello @hbZhao ,
Have you been able to move forward with your issue?
Have you been able to find where you were dividing by zero and fix it?
Regards
Software engineer at ST (TouchGFX)
