 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Micromite and Micromite Plus Beta 31
Page 1 of 2   |
|||||
| Author | Message | ||||
Geoffg Guru  Joined: 06/06/2011 Location: AustraliaPosts: 3292 |
Another beta. Hopefully this one has nailed all the lingering bugs in the MX170 version (famous last words). You can download it from: http://geoffg.net/Downloads/Micromite/Micromite_4.7_Beta.zip (clear your browser cache first). The changes are listed in the file Changes.txt but the important ones are: - Fixed the bug related to the TOUCH(X) function. - Implemented the ability to call the subroutine MM.PROMPT at the command prompt. The manual has been updated to document this feature (page 21). Please let me know if you find any more bugs. Geoff Geoff Graham - http://geoffg.net |
||||
atmega8 Guru Joined: 19/11/2013 Location: GermanyPosts: 724 |
Geoff, issues.txt says: "The Silicon Chip Driver has issues with Windows 10. The workaround is to power the PIC32 separately (ie, not use the USB +5V)." So we have to wait until Silicon Chip or Microsoft will fix the Bug? When providing external Power, but use the USB console, will the console work? ( I will test this tomorrow..) THX for all this cool enhancements😄, great! Atmega8 |
||||
| Geoffg Guru Joined: 06/06/2011 Location: AustraliaPosts: 3292 |
I should be able to fix it in firmware. I will let you know. Geoff Graham - http://geoffg.net |
||||
| atmega8 Guru Joined: 19/11/2013 Location: GermanyPosts: 724 |
Thank you Geoff..... |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
@Geoff, Possible bug . . . On 28-pin MX170 (not tried any other MMs), with a MM.PROMPT Sub (either saved in library; or just existing within a program), then you loose the '>' prompt at the start of the line. I am using usb-to-ttl into TeraTerm. As soon as I delete (or rename) the MM.PROMPT sub (or library) then the '>' returns WW |
||||
kiiid Guru Joined: 11/05/2013 Location: United KingdomPosts: 671 |
Geoff, I would like to find out a bit more about the mentioned issue with pin 22 and ssd1963-based displays. Can you please say a few words why is it and will pin 22 be available for use in future or, or never? Thanks http://rittle.org -------------- |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
@Geoff, If you exit the Editor using ESC, the MM.PROMPT Sub is not run (and you see the '>' prompt) |
||||
TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
After a LIBRARY SAVE, the MM.PROMPT sub is not run and the prompt is the default. After LIST it is run and the prompt reverts to my custom prompt. 18:24:32 >> LIBRARY SAVE > > > list 18:25:10 >> 18:25:16 >> 18:25:17 >> 18:25:17 >> library list Sub MM.PROMPT Print Time$ " >> "; End Sub 18:25:47 >> 18:26:19 >> MMEdit looks for the ">" in a few places so custom prompts which don't end in ">" will cause a few issues. I can add a timeout, but for now, please put the ">" in the custom prompt string if you are using MMEdit. Jim VK7JH MMedit |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
After reading Jim's post (and Page21) I see that the built-in command prompt is 'removed' and hence ignore my previous post . . . However, MM.Prompt is not run when using 'ESC' to exit the Editor; as well as immediately after LIBRARY SAVE. I assume it should be?? |
||||
| Chris Roper Senior Member  Joined: 19/05/2015 Location: South AfricaPosts: 280 |
This is a weird one: I did an XModem transfer of this code: [code] Const ds4 = 4 Const ds3 = 5 Const ds2 = 6 Const ds1 = 7 Const sw1 = 16 Const rp1 = 26 sub mm.prompt setpin ds4, dout setpin ds3, dout setpin ds2, dout setpin ds1, dout setpin sw1, din setpin rp1, ain Print "LPCDB>" end sub [/code] and the Micromite (28pin) went into an unbreakable loop with the following Console Output: 
Cheers Chris http://caroper.blogspot.com/ |
||||
boss Senior Member Joined: 19/08/2011 Location: CanadaPosts: 268 |
@Geoff Does exists road map for 100 pin chip FW? Regards Bo |
||||
| TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
I think the important part is the error message I got at the beginning of the output: sub mm.prompt
setpin 4, dout setpin 5, dout setpin 6, dout setpin 7, dout setpin 16, din setpin 26, ain Print "LPCDB>" end sub Saved 313 bytes [11] SetPin 4, dout Error: Pin 4 is reserved on startup [11] SetPin 4, dout Error: Pin 4 is reserved on startup [11] SetPin 4, dout I am using pin 4 for the LCD so the error message is valid, just no way of fixing it. Eventually the message changed to too many SUBs the same as Chris. I was unable to reset the MM+ and had to bring out the programmer.... I think that if there is an error in MM.PROMPT, we should be put back to the normal prompt without trying to run the sub again. Jim VK7JH MMedit |
||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
I know I am not Geoff, but I do know that the 100-pin version has not been developed yet, so there won't be any road map or other. It is mentioned in the documentation, as once the 64-pin one is up and running and as bug-free as possible, it is my understanding that the 100-pin chip will follow soon after that - it is a future release. But for right now, it is sort of in limbo, so to speak. Smoke makes things work. When the smoke gets out, it stops! |
||||
| Geoffg Guru Joined: 06/06/2011 Location: AustraliaPosts: 3292 |
Yes, now that I am concentrating on the MX470 (Micromite Plus) I plan to do the 100-pin version as well as some important bugs (eg, USB and Win 10). This beta has a couple of issues with MM.PROMPT - First, it is not consistently recognised after EDIT, XMODEM, etc. The second is that an error inside the sub causes mayhem. I will fix both of these in the next release. This is only temporary. Another priority for the next beta. Geoff Geoff Graham - http://geoffg.net |
||||
CFLY Regular Member  Joined: 20/05/2015 Location: FrancePosts: 41 |
Thank you Geoff! TOUCH (X) is OK and TEST GUI TOUCH also on screen 5 '  |
||||
| CFLY Regular Member Joined: 20/05/2015 Location: FrancePosts: 41 |
A pb !? I load my program (in B31, Micromite+) by the serial interface with MMEdit, I enter the "option autorun on", Off/on the supply and the program start ... OK. I disconnect the serial interface, Off/on the supply and nothing !!! I connect the serial interface, Off/on the supply and the program start ... I disconnect only the the link "Data to Micromite", Off/on the supply, "Micromite Plus MMBasic Ver 4.7 Beta 31 ..." on MMEdit ... OK, but the program is not started I connect the link "Data to Micromite" and I disconnect "Data from Micromite", no prompt on MMEdit ... OK and the program start With serial interface connected, I stop MMEdit, Off/on the supply and the program start ... 
Pb known? |
||||
| CFLY Regular Member Joined: 20/05/2015 Location: FrancePosts: 41 |
With the serial<=>USB disconnected from the pc, not ok With the serial<=>USB connected with only 5V it's ok ... |
||||
| CFLY Regular Member Joined: 20/05/2015 Location: FrancePosts: 41 |
With the serial interface (serial console) not connected, after power on, I can, only, star the program by the reset switch ... |
||||
| CFLY Regular Member Joined: 20/05/2015 Location: FrancePosts: 41 |
On my card, the MCLR has only a 10k on 3.3v ... |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
Sounds like you are getting parasitic power from the serial connection, and once you remove that connection, that source of parasitic power is then gone, so the chip does not start, or has a dirty start because there is no 'Clean' power. Parasitic power can supply enough power to run the chip, if that is where the supply is coming from, so you need to look carefully at the way you are powering the chip. What exactly are you using to power the circuit? Are you using a pre-built module or your own chip circuit on a breadboard? Breadboards have been the source of many problems before today...... EDIT: Seems OK on my module - I just setup a "Hello" loop, and then reset the MM+, and away it went as it was supposed to: 
Smoke makes things work. When the smoke gets out, it stops! |
||||
| Page 1 of 2 |
|||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
