• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 79 subscribers
  • Views 837 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.

BSL Scripter Error Codes

Raffael Zingg
Prodigy 60 points


Hy all

I've got some problems using the bsl scripter with a F5310.

I often get a Fail while trying to send a password or a mass erase
ErrorCode ist 80 or 38

------------------------------------------
BSL Scripting application 1.06
The local time is: 12:41 on 09.11.2011
------------------------------------------
Initializing, Mode: 5xx COM: COM7 DONE
RX Password: FAIL(80)
Mass Erase: FAIL(80)

or otherwise:

------------------------------------------
BSL Scripting application 1.06
The local time is: 12:43 on 09.11.2011
------------------------------------------
Initializing, Mode: 5xx COM: COM7 DONE
RX Password: FAIL(80)
Mass Erase: FAIL(38)

 Is there somewhere a complete list of all error codes?
In slau319a i found only a subset.
or does somebody know what this codes mean?

Many thanks for your help!
Raffael

  • 0
    Prodigy 60 points

    I think that I found the problem:
    I jump to BSL from usercode (using the following code: ((void (*)())0x1000)();  )
    In normal function I changed the clock to 8MHz. Before jumping to BSL I changed it back to the defaultvalues. Unfortunatelly I forgot one register what resultet in a clock different from the default startup clock.

    So it seems that this 80 has to do somenting with not detectable informations on the serial iterface.

    Not at all, it would be helpfull to get a full list of possible error codes!
    I tried to compile the bsl_scripter to single step it, but there I got some linker problems. Because of missing timeI have to let things like they are.

    Regards
    Raffael

  • 0 in reply to Raffael Zingg
    Guru 227245 points

    Raffael Zingg said:
    I forgot one register what resultet in a clock different from the default startup clock.

    In this case, not only the BSL didn't understand the command, the PC also most likely didn't understand the response (which only coincidentally is still taken as 0x80 - any other response would likely appear with more or less scrambled bits on the PC).

**Attention** This is a public forum