• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 754 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320C6203B: Possible to reverse engineer BIOS info?

Louis Savard
Prodigy 120 points

Part Number: TMS320C6203B

Hi,

I need to reproduce an older binary on the C6203. From the generated binary from back then (2005)... is there a way to reverse-engineer and identify which BIOS was used to generate a .out file?

Thanks, 

Louis

  • 0
    Prodigy 120 points
    Actually, it would be from the .x file (resulting from \ti\c6000\cgtools\bin\hex6x.exe -i c6203hex.cmd)
  • 0 in reply to Louis Savard
    TI__Intellectual 2300 points
    Hello Louis,
    did you try to just open the generated binary you have with some HEX editor and search for strings that can give a clue what BIOS version was used back in 2005 ?

    Michail
  • 0 in reply to Michail Georgiev
    Prodigy 120 points

    Yes, I did but without much success. Is the BIOS info even readable when in the format?

  • 0 in reply to Louis Savard
    TI__Intellectual 2300 points
    I was thinking of some text section left in the file by chance which can lead to BIOS version.
    In this case it should be difficult to obtain version back.
    Can you upload this binary here to take a look if not confidential any more?

    Michail
  • 0 in reply to Louis Savard
    TI__Intellectual 2300 points
    Hi again,
    I was able to see some text section which includes only system messages and two timestamps
    DATE STAMP [Oct 30 2001] [10:08:34]
    DATE STAMP [Nov 1 2001] [08:20:07]
    but nothing useful.
    Maybe BIOS version can be determined by some special part of its code included in your .x file but I am not familiar enough with this.
    Michail
  • 0 in reply to Michail Georgiev
    TI__Intellectual 2300 points

    Hello,

    Here are the rest of debug messages found in the binary. Unfortunately I can not find other clues what BIOS version was used during compilation of your legacy code.

    BR

    Michail

    Application started.",0 INTERNALHEAP",0
    "Assertion Violation: thraudioproc.c, line 234 (thrAudioproc[i].algCONNECTION != 0)",0
    "Assertion Violation: thraudioproc.c, line 263 (thrAudioproc[i].algVOXDETECT != 0)",0
    "Assertion Violation: thraudioproc.c, line 295 (thrAudioproc[i].algAGC != 0)",0
    "Assertion Violation: thraudioproc.c, line 325 (thrAudioproc[i].algMUTE != 0)",0
    "Assertion Violation: thraudioproc.c, line 350 (thrAudioproc[i].algFILTER != 0)",0
    "Assertion Violation: thraudioproc.c, line 376 (thrAudioproc[i].algCLID != 0)",0
    "Assertion Violation: thraudioproc.c, line 413 (thrAudioproc[i].algTONEGEN != 0)",0
    "Assertion Violation: thraudioproc.c, line 455 (thrAudioproc[i].algTONEDETECT != 0)",0
    "Assertion Violation: thraudioproc.c, line 479 (thrAudioproc[i].algENERGY != 0)",0
    "Assertion Violation: thraudioproc.c, line 503 (thrAudioproc[i].algH100MONITOR != 0)",0
    "Assertion Violation: thrdispatch.c, line 97 (((thrDispatch.pipIn0)->readerNumFrames) > 0)",0
    "Assertion Violation: thrdispatch.c, line 98 (((thrDispatch.pipIn1)->readerNumFrames) > 0)",0
    "Assertion Violation: thrdispatch.c, line 99 (((thrDispatch.pipOut0)->writerNumFrames) > 0)",0
    "Assertion Violation: thrdispatch.c, line 100 (((thrDispatch.pipOut1)->writerNumFrames) > 0)",0
    "SYS abort called with message ",27h,"%s",27h,0
    "SYS_error called: error id = 0x%x",0
    "C62XX_DMA_MCBSP_isr: WARNING: nextsize = 0!",0
    "C62XX_DMA_MCBSP1_isr: WARNING: nextsize = 0!",0
    "PLIO_new: controller open failed",0

  • 0 in reply to Michail Georgiev
    Prodigy 120 points

    Thank you Michail. Since I cannot identify the BIOS to reproduce the binary, we will consult with our client.

    Regards,

    Louis