TheBackShed.com

Forum Index : Microcontroller and PC projects : Backpack Reboot Loop

Author

Message

Phil23
Guru

Joined: 27/03/2016
Location: Australia
Posts: 1667

Posted: 11:36am 23 Jan 2017

Copy link to clipboard

Print this post

One of my LCD backpacks got stuck in a reboot loop yesterday.

Just brought it inside & connected it to the FTDI & see this:-

[Code]Micromite MKII MMBasic Ver 5.2
Copyright 2011-2016 Geoff Graham

Option error - Cleared OPTION TOUCH
Processor restarted

Option error - Cleared OPTION TOUCH
Processor restarted

[/code]

Will obviously need a reset or reflash,
definitely not having any luck breaking with Ctrl-C in MMedit.

Any thoughts on what might have caused it?

Cheers.

JohnS
Guru

Joined: 18/11/2011
Location: United Kingdom
Posts: 4036

Posted: 11:52am 23 Jan 2017

Copy link to clipboard

Print this post

You could read out the flash then someone (if you can find a volunteer, if not you) can look at it to see what is set / has happened.

Any ICSP tool can probably do it unless you used the program-protect feature.

John

TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 6269

Posted: 12:43pm 23 Jan 2017

Copy link to clipboard

Print this post

Either there is a hardware error on one of the pins associated with the LCD or you have a bad option setting.

Have you tried the exclamation method:

Quote Sending a stream of exclamation marks (!) to the console Rx pin at 34800 baud during its startup.
In the first 100mS after powering up the Micromite will set the console to 34800 baud and check to see if
an exclamation mark is received. If so, it will then wait for two seconds to see if it is going to get more
than 30 of them in that time. If this is the case the Micromite will reset itself to its initial defaults and
send the message "MMBasic reset completed" to the console.
This reset can be accomplished by simply setting the terminal emulator to 38400 baud and holding down
the exclamation key while powering up the Micromite (on most keyboards this requires holding down
shift and the number one key). This will even work if the console has been set to a non standard baud
rate.

Jim

VK7JH
MMedit

Phil23
Guru

Joined: 27/03/2016
Location: Australia
Posts: 1667

Posted: 12:53pm 23 Jan 2017

Copy link to clipboard

Print this post

TassyJim said Either there is a hardware error on one of the pins associated with the LCD or you have a bad option setting.

Have you tried the exclamation method:

Yes, that's how I solved it.

It responded to a string of !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! sent from MMedit in ASCII mode.

Not sure of the cause; but I did notice the LCD now has a scratch.

Some of MsK's feline friends are known to play with projects at times.
"Touching" LCD's, & but more often taking ownership of jump leads....

Phil.

Grogster

Admin Group

Joined: 31/12/2012
Location: New Zealand
Posts: 9589

Posted: 08:26am 24 Jan 2017

Copy link to clipboard

Print this post

"I tawt I taw a puddy tat!"

An interesting error loop.
Please let us know if that happens again.
Perhaps Geoff will chime in with what that error means in laymen's terms.

Smoke makes things work. When the smoke gets out, it stops!

Print this page

To reply to this topic, you need to log in.