TheBackShed.com

Forum Index : Microcontroller and PC projects : Micromite 5.2 Firmware Update

Page 1 of 2

Author

Message

Geoffg

Guru

Joined: 06/06/2011
Location: Australia
Posts: 3282

Posted: 11:09pm 23 Jun 2016

Copy link to clipboard

Print this post

I have updated the Micromite firmware to Ver 5.2 and it can be downloaded from: http://geoffg.net/micromite.html

This is mostly a bug fix release with three main new features:
- Ability to trap errors.
- MsgBox() function for the MM+.
- The PAGE command for the MM+.

Check the Change Log for the details (it runs to one and a half pages). For anyone who has installed the previous beta version this release is almost the same with a couple of extra bug fixes.

Thanks again to everyone who has tried out the beta versions. Of all the bugs fixed only a couple were discovered by me, the rest were found by you and I am very grateful

Geoff

Geoff Graham - http://geoffg.net

robert.rozee
Guru

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

Posted: 05:08am 24 Jun 2016

Copy link to clipboard

Print this post

i'm afraid the 5.2 release version still contains the editor bug outlined here:
http://www.thebackshed.com/forum/forum_posts.asp?TID=8701&PN=4
(Posted: 03 June 2016 at 12:37am)
that places the cursor on the end of the status line at the bottom of the screen under certain conditions.

apologies,
rob :-)

kiiid

Guru

Joined: 11/05/2013
Location: United Kingdom
Posts: 671

Posted: 05:33am 24 Jun 2016

Copy link to clipboard

Print this post

Edit:
Has the GUI DEFAULT command disappeared?

Edited by kiiid 2016-06-25

http://rittle.org

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

lew247

Guru

Joined: 23/12/2015
Location: United Kingdom
Posts: 1702

Posted: 05:41am 24 Jun 2016

Copy link to clipboard

Print this post

Tried downloading it and it says [quote]Whoops... cannot find that page

Page Not Found HTTP 404 - File not found[/quote]

matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 10222

Posted: 05:51am 24 Jun 2016

Copy link to clipboard

Print this post

Quote Has the GUI DEFAULT command disappeared?

From the change log:

Quote The GUI DEFAULT command has been removed as its functionality is now
provided by the GUI SETUP command.

Geoffg

Guru

Joined: 06/06/2011
Location: Australia
Posts: 3282

Posted: 06:56am 24 Jun 2016

Copy link to clipboard

Print this post

Sorry Rob, I forgot to add in the notes that yours is the one bug that I have not been able to fix yet. It is a curly one.

Lewis, the link does work. Have you tried clearing your browser's cache?

Geoff

Geoff Graham - http://geoffg.net

lew247

Guru

Joined: 23/12/2015
Location: United Kingdom
Posts: 1702

Posted: 07:17am 24 Jun 2016

Copy link to clipboard

Print this post

it's ok Geoff,. It came back online 10 minutes after I posted that
Maybe too many people were trying to download all at once
I tried to edit my post to say it's back but it wouldn't let me edit it

Phil23
Guru

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

Posted: 04:28pm 24 Jun 2016

Copy link to clipboard

Print this post

Just noticed page 16 of the MM+ addendum manual...

[Code]
100-Pin Example
The Explore 100 board using the 100-pin Micromite Plus uses the following pin allocations:

Pin 48 is the SSD1966 LED_A control
Pin 1 is the touch Chip Select
Pin 40 is the touch IRQ input
Pin 39 is the touch click output (see the next chapter)
Pin 47 is the SD card Chip Select

The corresponding configuration commands are:
OPTION LCDPANEL SSD1963_5, LANDSCAPE, 48
OPTION TOUCH 1, 40, 39
OPTION SDCARD 47

64-Pin Example
For the Explore 64 board (64-pin Micromite Plus) the following allocations are recommended:.....[/code]

I'm sure all new users will appreciate that.

So good to have something that supported by thorough AND current documentation.

Thanks

Phil

Grogster

Admin Group

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

Posted: 05:23pm 24 Jun 2016

Copy link to clipboard

Print this post

Page 63 of the standard manual, under OPTION ERROR, at the bottom of the description box it says:

MicroMite Manual, Page 63 said ON ERROR ABORT can make it very difficult to debug a program, so it is strongly recommended that only ON ERROR SKIP be used.

Is that actually worded correctly? Is it meant to be "ON ERROR IGNORE can make it very difficult to debug a program".........

I would have thought that normal abort and show the error message is what you WANT for debugging purposes.

Once you are totally sure the program is bug-free(a bold statement!), then you could have the ON ERROR IGNORE.

Am I correct in assuming that with ON ERROR IGNORE, the variables holding the error number and text are updated with the latest error? This would mean if you have a couple of errors, the variables would hold the number and text of the LAST error, but not necessarily the error that caused problems, which may have been an ignored error or two back.

Correct?

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

Geoffg

Guru

Joined: 06/06/2011
Location: Australia
Posts: 3282

Posted: 01:04am 25 Jun 2016

Copy link to clipboard

Print this post

Thanks Grogs, you are right.

Quote Am I correct in assuming that with ON ERROR IGNORE, the variables holding the error number and text are updated with the latest error? This would mean if you have a couple of errors, the variables would hold the number and text of the LAST error, but not necessarily the error that caused problems, which may have been an ignored error or two back.

Correct again.

Geoff

Geoff Graham - http://geoffg.net

disco4now

Guru

Joined: 18/12/2014
Location: Australia
Posts: 1000

Posted: 02:13am 25 Jun 2016

Copy link to clipboard

Print this post

Just a small thing I noticed when comparing the new Cfunctions.h to see what was new.
In the new CFunctions.h file the definition below at around line 74 is missing the closing bracket in the definition. i.e

#define putConsole(a ((void (*)(char)) Vector_putConsole) (a)

in place of

#define putConsole(a) ((void (*)(char)) Vector_putConsole) (a)

Regards
Gerry

Latest F4 Latest H7 FotS

kiiid

Guru

Joined: 11/05/2013
Location: United Kingdom
Posts: 671

Posted: 10:50pm 26 Jun 2016

Copy link to clipboard

Print this post

There is something wrong with the I2C support. A program which is working fine on 5.1 hangs to the level to require reset (!!!) on 5.2.
I was able to isolate the problem and it is coming from this line: I2C write TSLaddr, 1, 1, &Hb4

http://rittle.org

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

Geoffg

Guru

Joined: 06/06/2011
Location: Australia
Posts: 3282

Posted: 02:17am 27 Jun 2016

Copy link to clipboard

Print this post

Not good. I will have a look at it.

Geoff

Geoff Graham - http://geoffg.net

Geoffg

Guru

Joined: 06/06/2011
Location: Australia
Posts: 3282

Posted: 03:18am 29 Jun 2016

Copy link to clipboard

Print this post

kiiid said There is something wrong with the I2C support. A program which is working fine on 5.1 hangs to the level to require reset (!!!) on 5.2. I was able to isolate the problem and it is coming from this line: I2C write TSLaddr, 1, 1, &Hb4

I have not been able to get this to fail.

I presume that you are using the MM+ ?
Could it be because you are using option 1 (ie, a stop condition is not sent) ?

I have done a compare on the 5.1 source compared to 5.2 and the only differences are in the RTC commands, nothing has changed in the general I2C commands. Are you using RTC GETTIME by any chance?

Geoff

Geoff Graham - http://geoffg.net

matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 10222

Posted: 03:32am 29 Jun 2016

Copy link to clipboard

Print this post

Quote Are you using RTC GETTIME by any chance?

A RTC GETTIME command in an interrupt routine could likely create problems for any option 1 command I2C and visa versa. The solution would be to set a flag after the option 1 command and check for it in the interrupt routine

kiiid

Guru

Joined: 11/05/2013
Location: United Kingdom
Posts: 671

Posted: 06:09am 29 Jun 2016

Copy link to clipboard

Print this post

It looks like the problem was related with the "brain loss" issue (I was outputing information on the LCD), so once it was gone, I didn't get any further problems with the I2C operation as well.Edited by kiiid 2016-06-30

http://rittle.org

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

Phil23
Guru

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

Posted: 01:46pm 30 Jun 2016

Copy link to clipboard

Print this post

Just noticed the interpreter didn't return an error on this little mistake.

Dropped me to a prompt & then the watchdog forced a re-start.

Should it have been reported?

As Sub without END SUB? (Typed END IF, in my rush)...

[code]Sub SetFlags

StatFlags=0

If SolarVolts>=SolarMin Then StatFlags=&b000001
If SolarVolts>=SolarThres Then StatFlags=StatFlags+&b000010
If TmpPan-TmpCur>=TmpDifPan Then StatFlags=StatFlags+&b000100
If TmpOut-TmpDif>=TmpDif Then StatFlags=StatFlags+&b001000
If PumpStat="Running" Then StatFlags=StatFlags+&b010000
If PumpRunTime>30 then StatFlags=StatFlags+&b100000

End If

Sub ChkCon
[/code]

Cheers

Phil.

kiiid

Guru

Joined: 11/05/2013
Location: United Kingdom
Posts: 671

Posted: 01:08am 04 Jul 2016

Copy link to clipboard

Print this post

I think there is definitely a problem with the built-in editor in the 5.2 version. It is very unstable and in Tera Term would exit unexpectedly on its own back to the command line in about 90% of the cases. Then in the command line something like [B[B appears.
I can see the changes in editor.c between 5.1 (which was good) and 5.2, but still can't figure out why is this happening. For now just reporting the problem which I have verified is consistent on a few different boards.
Speaking in more general terms, I think it would be good if the built-in editor is a bit revised and expanded with functionality in the next version. Things like "go to line" or "find and replace", or even a keystroke to remove a line, lot of useful functions are currently missing and can be added. The colourcode option also needs some revised colours because currently they are not looking good on the screen and I always have to disable it.

Edited by kiiid 2016-07-05

http://rittle.org

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

Grogster

Admin Group

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

Posted: 02:12am 04 Jul 2016

Copy link to clipboard

Print this post

Is this the MM+ or the standard MM?

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

kiiid

Guru

Joined: 11/05/2013
Location: United Kingdom
Posts: 671

Posted: 02:14am 04 Jul 2016

Copy link to clipboard

Print this post

MM+, but it doesn't matter because they both use the same editor

http://rittle.org

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

Page 1 of 2

Print this page