 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 : Draft PicoMite 6.00.01 User Manual
  Page 8 of 9   |
|||||
| Author | Message | ||||
| twofingers Guru  Joined: 02/06/2014 Location: GermanyPosts: 1306 |
Next try (2024-12-10_194930_PicoMite_User_Manual rev. 1): Manual-1 - Kopie.zip Regards Michael causality ≠ correlation ≠ coincidence |
||||
homa Guru Joined: 05/11/2021 Location: GermanyPosts: 379 |
...in the first post! Everything else worked then. @twofingers: That's our non-native speaker problem! I probably would have defined it more clearly in German. But everyone here should get something out of it, and so it goes on in English. I am still in favour of reinstating Appendix J and would even argue for another one (K - 3D engine) see the reference on page 69: ‘See the document The CMM2 3D engine.pdf ’ Matthias Edited 2024-12-16 00:14 by homa |
||||
| twofingers Guru Joined: 02/06/2014 Location: GermanyPosts: 1306 |
|
||||
Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 6904 |
@homa I would argue against any expansion that makes the manual too thick to fit my ring binder. :) It's easier to get another A5 binder (and they aren't *that* easy to find anyway) than it is to find one that can take a lot of pages. If the manual splits nicely then it's a lot easier. Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
| homa Guru Joined: 05/11/2021 Location: GermanyPosts: 379 |
@Mick But you can print a PDF from page X to page Y and put it in more than one ring binder. You can also put all the attachments in a second ring binder. But a PDF is much nicer to read on a PC or an e-book reader. Searching works better in the PDF and you only have one file. File size is no longer an argument these days. In fact, I would argue that the linking within the PDF should be greatly improved. Table of contents to chapter pages as a link, or also cross references, see ... etc. Matthias |
||||
| Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 6904 |
I hate reading PDFs and love an old-fashioned ring-bound dog-eared manual. :) The PDF approach is also next to useless unless you have two screens. I need to look things up constantly as my short-term memory is terrible (medical reasons). Printing the manual in two chunks is fine, but I would definitely prefer it if the chunk that I'm unlikely to ever use didn't need to be in the manual at all. ;) The best manuals I've ever used have been those that you can leave open flat on a table while you make a brew. The worst are those that close themselves unless you prop them open with something weighty. Tablets and e-book readers that inconveniently shut themselves off to save battery power between accesses are somewhere in between. Signed, The Devil's Advocate . Edited 2024-12-16 05:38 by Mixtel90 Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
| homa Guru Joined: 05/11/2021 Location: GermanyPosts: 379 |
Where is the problem ;-)  |
||||
| ville56 Senior Member  Joined: 08/06/2022 Location: AustriaPosts: 118 |
How about splitting the whole thing into 2 manuals: 1) MMBasic language reference manual 2) MMBasic programming manual i really liked this concept back in the days of DEC. They had really good manuals, the languale reference having all the statements/functions and their arguments explained on a detailed level and the programming manuals to explain how to use the language elements to form efficient programs with examples and code snippets. 73 de OE1HGA, Gerald |
||||
| Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 6904 |
@Mathias Ok, ok.... :) That's about 8x the desk area that I have available. lol @Gerald I don't think it warrants that. The existing one is fine by me, but there are some items that are only of use to those with a lot of programming experience. These are generally related to advanced graphic applications and modifications to MMBasic in some way. I'd be even happier to see three manuals. lol A - the normal MMBasic manual, more or less as we see it now. B - a beginner's manual, teaching the rudiments of MMBasic. This would be much like Geoff's excellent "Programming in BASIC - A Tutorial". Perhaps a bit more stuff specific to MMBasic could be added. C - customizing MMBasic & advanced programming. This would cover stuff like advanced graphics, CSubs, fonts and the PIO. Believe it or not, some of us have never used any of this stuff to date. :) (Although I did once play with a font). The above are almost splits at the appendices of the existing manual anyway. B would probably be rarely updated. A maybe a little less than C, which is where a lot of the clever stuff tends to happen. However, this is just mind games. I'm perfectly happy with Geoff's proposal to split off the advanced graphics merely to reduce the bulk of the main manual. Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
Geoffg Guru Joined: 06/06/2011 Location: AustraliaPosts: 3232 |
In the final firmware we will have four manuals: - The CMM2 3D engine - Advanced Graphics Functions - Graphics in the PicoMite (a primer) - PicoMite_User_Manual (the main manual) It is just not practical to combine all of these into one, especially as some, like the 3D engine, are specialised. A good alternative would be to have two manuals, a User Manual and a Tutorial Manual (like the Getting Started with the Micromite tutorial) but lack of time and Peter's rapid introduction of new features has caused me to put that on hold. BTW, the Feb 2025 issue of Silicon Chip magazine will have a six page article introducing Peter's V6.00.01 firmware to the world. Geoff Geoff Graham - http://geoffg.net |
||||
| JanVolk Senior Member Joined: 28/01/2023 Location: NetherlandsPosts: 166 |
Gentlemen, I agree with not making the manual so large and splitting it up if necessary. Then with a good link so that you can go straight to the sub-document and view it straight away. Another point is that creating links from the content makes the PDF file very large and is also difficult to achieve with OpenOffice. Good content is also important with page numbers so that people can immediately enter that number from the PDF bar. This works very well for me. Another disadvantage of a document that is too large is that it can no longer be sent with a standard email (> 3MB I thought) and therefore the resolution of images must be reduced slightly when converting to PDF. Here's an example of what my content looks like: MMBasic PicoMite handleiding Ver 5.07.07.pdf Greetings, Jan. |
||||
Supertech Newbie  Joined: 13/11/2016 Location: AustraliaPosts: 25 |
Typo error? Already noticed? Awsome work Geoff. During (proof) reading manual, perhaps trivial, but Page 126, PIO 6 lines of text down, Says, "See the Appendix F for a more detailed description of programming POIs" Um, shouldn't it be, "See the Appendix F for a more detailed description of programming PIOs" See error? Given so many others, It caught my eye as it were, stood out..... Everything else seems correct within PIO command area that continues on. Regards to All. Supertech. |
||||
| Supertech Newbie Joined: 13/11/2016 Location: AustraliaPosts: 25 |
Sorry if these already seen, Page 145-146 Etc WEB (as group of WEB command intoduction heading) Excellent, good, however WII is next, intermingled within WEB group of commands? Shouldn't WII (sony numchuck stuff) have or be in its own group of commands, at a guess below WEB group? |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2838 |
Hi Geoff, Referencing the user-manual as linked in your first post on this thread. You may already be aware, but just in case, OPTION HDMI PINS is missing (I need it to configure it to get the Olimex ‘motherboard’ to work - no signal otherwise!) Not sure if the aim is to make this option ultimately redundant, so just highlighting it for now…. For everything Micromite visit micromite.org Direct Email: whitewizzard@micromite.o |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2838 |
(deleted duplicated post!) Edited 2024-12-17 19:23 by WhiteWizzard For everything Micromite visit micromite.org Direct Email: whitewizzard@micromite.o |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 9286 |
OPTION HDMI PINS clockpositivepin, d0positivepin, d1positivepin, d2positivepin Valid values are 0-7 and of course the pins mustn't overlap for each channel: If the pin is an even number the negative pin is defined as pin+1 If the pin is an odd number the negative pin is defined as pin-1 Defaults to 2,0,6,4 to match various commercial boards |
||||
stanleyella Guru Joined: 25/06/2022 Location: United KingdomPosts: 2183 |
I used gp 12--0+...d0+ gp 13--0-...d0- gp 14--txc+..ck+ gp 15--tc..ck- gp 16--tx2+..d2+ gp 17--tx2-..d2- gp 18--1+..d1+ gp 19--1-..d1- my vero but olimex board I got is different |
||||
| Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 6904 |
That's why it's there, Stan, so that we can have some flexibility in the connections. My own designs now use something else again. Once again, thinking of the pins as GP numbers isn't the best way at all, it makes it complicated. They are HSTX0 to HSTX7 because you can't control or access them using GP numbers. In your case: D0+ - HSTX0 (location of GP12) D0- - HSTX1 CK+ - HSTX2 CK- - HSTX3 D2+ - HSTX4 D2- - HSTX5 D1+ - HSTX6 D1- - HSTX7 (location of GP19) so the HSTX option OPTION HDMI PINS clockpositivepin, d0positivepin, d1positivepin, d2positivepin becomes OPTION HDMI PINS HSTX2, HSTX0, HSTX6, HSTX4 i.e. the default: OPTION HDMI PINS 2, 0, 6, 4 It's easy when you forget the GP pin numbers. You can soon rearrange the pin pairs and sort out the PINS option. Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
| stanleyella Guru Joined: 25/06/2022 Location: United KingdomPosts: 2183 |
ta Mick, I'll document your hdmi ref info. new stuff to me but works hardware wise. it got to be gp12 to gp19? so new names for those pins only, no other options ? just those pins. hardware works ok. don't know how hdmi is referenced in the manual, if it is. why swap the even numbers? if I got it. Edited 2024-12-18 05:22 by stanleyella |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 9286 |
Coming in RC9. Geoff, please add to the manual MATH AES128 ENCRYPT/DECRYPT CBC/ECB/CTR key$/key(), in$/in(), out$/out() This command encrypts or decrypts the data in 'in' and puts the answer in 'out' using the AES128 encryption method specified The parameters can each be either a string, integer array, or float array with any mix possible The key must be 16 elements long (16*8=128bits) in and out must be a multiple of 16 elements long. When integer or float arrays are use for the 'key' or 'in' each element must be a number between 0 and 255 otherwise an error will be generated. In the case of 'out' being specified as a string, the string variable must exist and should be set to empty (DIM out$="") The maximum number of elements in 'in' and 'out' is 256 when defined as arrays or 128 if one or other is defined as a string Edited 2024-12-18 18:47 by matherp |
||||
| Page 8 of 9 |
|||||
 Print this page |
