Jump to content

[Fixed] Hard Fault PC=0x0003199c


Marxon
 Share

Recommended Posts

Hi everyone,

there is a problem with my Midibox Sequencer V4 (LPC Core)

If i want to save a Track Event Preset, the sequencer stops working and shows the following error:

Hard Fault PC=0x0003199c

It creates a correct named preset but its empty (0 kb filesize)

But from time to time it saves it correctly.

I tried different sd-cards without success.

What couldt be the problem? I searched around the firmware files for this error code but it is not listed

and i dont really know how to debug it.

Thanks a lot for your help!

Marxon

Edited by Marxon
Link to comment
Share on other sites

Of course!

Additionally these are my SD-Card infos from the Sequencer:

[41937.654] SD Card Informations

[41937.654] ====================

[41937.654] --------------------

[41937.654] CID:

[41937.654] - ManufacturerID:

[41937.654] - OEM AppliID:

[41937.654] - ProdName: SD01G

[41937.656] - ProdRev: 36

[41937.656] - ProdSN: 0x00e8039c

[41937.656] - Reserved1: 45

[41937.656] - ManufactDate: 107

[41937.656] - msd_CRC: 0x2c

[41937.656] - Reserved2: 1

[41937.656] --------------------

[41937.658] --------------------

[41937.658] - CSDStruct: 0

[41937.658] - SysSpecVersion: 0

[41937.658] - Reserved1: 0

[41937.658] - TAAC: 93

[41937.658] - NSAC: 0

[41937.658] - MaxBusClkFrec: 50

[41937.660] - CardComdClasses: 309

[41937.660] - RdBlockLen: 9

[41937.660] - PartBlockRead: 1

[41937.660] - WrBlockMisalign: 0

[41937.660] - RdBlockMisalign: 0

[41937.660] - DSRImpl: 0

[41937.660] - Reserved2: 0

[41937.662] - DeviceSize: 3883

[41937.662] - MaxRdCurrentVDDMin: 6

[41937.662] - MaxRdCurrentVDDMax: 6

[41937.662] - MaxWrCurrentVDDMin: 6

[41937.662] - MaxWrCurrentVDDMax: 6

[41937.662] - DeviceSizeMul: 7

[41937.664] - EraseGrSize: 16

[41937.664] - EraseGrMul: 13

[41937.664] - WrProtectGrSize: 31

[41937.664] - WrProtectGrEnable: 0

[41937.664] - ManDeflECC: 0

[41937.664] - WrSpeedFact: 5

[41937.664] - MaxWrBlockLen: 9

[41937.666] - WriteBlockPaPartial: 0

[41937.666] - Reserved3: 0

[41937.666] - ContentProtectAppli: 0

[41937.666] - FileFormatGrouop: 0

[41937.666] - CopyFlag: 0

[41937.666] - PermWrProtect: 0

[41937.668] - TempWrProtect: 0

[41937.668] - FileFormat: 0

[41937.668] - ECC: 0

[41937.668] - msd_CRC: 0x41

[41937.668] - Reserved4: 1

[41937.668] --------------------

[41937.668]

[41937.668] Reading Root Directory

[41937.670] ======================

[41937.670] Retrieving SD Card informations - please wait!

[41937.670] SD Card: '': 1008 of 1017 MB free

[41937.670] [.....d.] 08/06/08 01:12:50 AM <DIR> 0 SESSIONS

[41937.672] [.....d.] 08/06/08 00:48:32 AM <DIR> 0 SYSEX

[41937.672] [.......] 08/06/08 01:12:54 AM 2080 MBSEQ_BM.V4

[41937.672] [......a] 00/00/-20 00:00:00 AM 850 MBSEQ_GC.V4

[41937.674] [......a] 08/06/08 02:55:38 AM 16792 MBSEQ_HW.V4

[41937.674] [.......] 06/03/09 06:48:46 PM 692 NEUTEX~1.TXT

[41937.674] [.....d.] 02/25/12 01:42:48 PM <DIR> 0 MIDI

[41937.676] [.....d.] 08/06/08 00:26:58 AM <DIR> 0 PRESETS

[41937.676]

[41937.676] Checking SD Card at application layer

[41937.676] =====================================

[41937.676] Current session: /SESSIONS/MRX

[41937.678] File /SESSIONS/MRX/MBSEQ_B1.V4: valid (64 patterns)

[41937.678] File /SESSIONS/MRX/MBSEQ_B2.V4: valid (64 patterns)

[41937.678] File /SESSIONS/MRX/MBSEQ_B3.V4: valid (64 patterns)

[41937.680] File /SESSIONS/MRX/MBSEQ_B4.V4: valid (64 patterns)

[41937.680] File /SESSIONS/MRX/MBSEQ_M.V4: valid (128 mixer maps)

[41937.680] File /SESSIONS/MRX/MBSEQ_S.V4: valid (64 songs)

[41937.682] File /SESSIONS/MRX/MBSEQ_G.V4: valid

[41937.682] File /SESSIONS/MRX/MBSEQ_BM.V4: valid

[41937.682] File /SESSIONS/MRX/MBSEQ_C.V4: valid

[41937.682] File /MBSEQ_C.V4: valid

[41937.684] File /MBSEQ_BM.V4: valid

[41937.684] File /MBSEQ_HW.V4: valid

[41937.684] done.

--------------------------------------------------------------

------------------------------------------------------------------

[43374.819] [sEQ_UI_Button_Handler] Button SR:1, Pin:1 not mapped, it has been pressed.

[43374.819] [sEQ_UI_Button_Handler] Button SR:1, Pin:4 not mapped, it has been pressed.

[43374.915] [sEQ_UI_Button_Handler] Button SR:1, Pin:1 not mapped, it has been depressed.

[43374.915] [sEQ_UI_Button_Handler] Button SR:1, Pin:4 not mapped, it has been depressed.

[43385.667] Track Overview:

[43385.667] ===============

[43385.667] | Track | Mode | Layer P/T/I | Steps P/T | Length | Port | Chn. | Muted |

[43385.669] +-------+-------+-------------+-----------+--------+-------+------+-------+

[43385.670] | G1T1 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 1 | no |

[43385.670] | G1T2 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 2 | no |

[43385.672] | G1T3 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 3 | no |

[43385.673] | G1T4 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 4 | no |

[43385.674] | G2T1 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 13 | no |

[43385.674] | G2T2 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 14 | no |

[43385.676] | G2T3 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 15 | no |

[43385.677] | G2T4 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 16 | no |

[43385.678] | G3T1 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 13 | no |

[43385.678] | G3T2 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 14 | no |

[43385.678] | G3T3 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 15 | no |

[43385.680] | G3T4 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 16 | no |

[43385.680] | G4T1 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 13 | no |

[43385.682] | G4T2 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 14 | no |

[43385.682] | G4T3 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 15 | no |

[43385.684] | G4T4 | Note | 4/ 8/ 1 | 256/256 | 16 | Def. | 16 | no |

[43385.684] +-------+-------+-------------+-----------+--------+-------+------+-------+

[43385.685] done.

Edited by Marxon
Link to comment
Share on other sites

  • 2 weeks later...
  • 2 months later...

I haven't changed anything to solve this issue, as I wasn't able to reproduce it.

Please let me know if it fails again on future MBSEQ firmware updates, it could be related to a memory allocation issue which causes memory accesses to invalid addresses (this will be hard to troubleshoot -> therefore "hard fault" ;-))

Best Regards, Thorsten.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...