 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 : help micromite extrem
Page 1 of 2   |
|||||
| Author | Message | ||||
goc30 Guru  Joined: 12/04/2017 Location: FrancePosts: 435 |
Hi all I have a pic32Mz 100 pins with 5p ssd1963 TFT and an sdcard (adafruit MicroSd breakout ) micromite is V5.05.01 200mhz and i have 2 problems 1 - SdCard work correctly if I don't use CD pin (option sdcard 81,,,3), but if I use Cd pin, each time I have "Sdcard not detected". 2 - I put touch function (option Touch 80,82). When I use "Gui calibrate, first point is detected, but second point make an error ("Error : Touch hardware failure") I use SPI canal (first canal) thank for help |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10572 |
Sounds like the microsd may be wired with the CD pin inverted. By default he software assumes pin is grounded when card is inserted, set the pin number negative to invert the test. See MM+ manual. Touch (and SPI displays) are always on SPI2 |
||||
| goc30 Guru Joined: 12/04/2017 Location: FrancePosts: 435 |
thank for response ok but when i have pb with hardware connect with one type of proc, I don't think to read manual of other micromite versus in wich manual can i see this ? and is-it also true for pic32mx170 (28pins) who have no second spi??  |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10572 |
MMX manual page 3 MMX manual page 22, MM+ manual page 11. MM2 is of course different |
||||
| goc30 Guru Joined: 12/04/2017 Location: FrancePosts: 435 |
MMX page 3 is "content list" besides the ungraceful and slightly haughty side of your answer, I would point out that the manual mm+ is only for circuits pic32mx and not pic32mz, and therefore we are entitled to think that the use of ports is not necessarily identical and therefore there is no reason to go to a different manual. When i use a PIC i will not think to see the datasheet of an ARM. rather than requiring us to open 36 manuals, you could have used a function such as "copy/paste" to remove any ambiguity. and that would have made your manual more serious and more practical, because with all these versions, after a time, we don't know who does what and where to go for information. incidentally, in the new version, you can add that on the sdcard the cd signal is in negative logic, because this detail we can't know it. |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10572 |
The MMX is a port of the MM2/MM+ and the MMX manual describes the differences. That is always how it is going to be as otherwise whenever Geoff changes the core functionality multiple manuals would need to be updated. From the MM+ manual Of course you are perfectly entitled to copy/paste the manuals together yourself and I'm sure other users would be pleased if you did so and made the result freely available like I do with the MMX source, firmware, and existing manual. |
||||
| JohnS Guru Joined: 18/11/2011 Location: United KingdomPosts: 4133 |
Maybe not but if you have chosen some hardware with it turns out inverted signal it's maybe you who made the choice and ought to put some work in to cope with your choice. Or avoid the problem by not choosing that hardware. John |
||||
| JohnS Guru Joined: 18/11/2011 Location: United KingdomPosts: 4133 |
I missed those - is it really 36 manuals one needs to open? Would you mind listing them? John |
||||
| goc30 Guru Joined: 12/04/2017 Location: FrancePosts: 435 |
decidely you know how to answer only with contempt and arrogance. the kind of answer "you just have to do it yourself", while you know that I have neither the sources nor the original documentation (despite several requests), proves your contempt for the users and the high considering that you have of yourself. it's a shame, your product could be good but with reactions like yours, and your refusal to make a documentaiton worthy of the name, it does not envy to use it. |
||||
| robert.rozee Guru Joined: 31/12/2012 Location: New ZealandPosts: 2464 |
i think the phrase "of course" translates poorly into french, with far more emotional baggage than the original english writer intended. peter is a good guy, who enjoys tinkering with code, but doesn't find writing documentation so much fun. he has made a good deal of material available about the extensions and enhancements he has made to mmbasic, but that material is not well organized or in any single document. i think he is just saying that he has done the bits he enjoys doing, while leaving the other parts up to someone else to pick up. no contempt or arrogance, just no interest in writing a user manual. and after all, peter does what he does for free out of the goodness of his heart, so who are we to complain? cheers, rob :-) |
||||
panky Guru Joined: 02/10/2012 Location: AustraliaPosts: 1116 |
@goc, With the greatest respect, you are being both unfair in your criticism of Peter and quite unrealistic in your expectations about the MM Extreme. Peter has done a terrific job in porting MMBasic across to the MZ chip but he has done so on his own and, with Geoff's approval, made it available for anyone interested. It is NOT a commercial product nor was ever intended to be so. It is a hobbbyist item and it is entirely reasonable to expect that anyone interested in experimenting with it have both the ability and desire to spend their own time and effort if they choose to 'play' with the item. I have always found Peter to be extremely responsive to any questions but if the answers to your questions are to be found in the manuals or Backshed blogs, it is YOUR responsibility to read and comprehend. If this is something that you are unwilling or unable to do, may I respectfully suggest that you might like to move to some other micro that more suits your needs. panky. ... almost all of the Maximites, the MicromMites, the MM Extremes, the ArmMites, the PicoMite and loving it! |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10572 |
goc In your initial post you asked two questions which I replied to solving your issues. In the case of one of your questions the answer was in the MMX manual with no need to refer elsewhere. In the case of the other the answer is in the MM+ manual which I pointed out. I also pointed out that at the very beginning of the MMX manual it states that it is a supplementary manual to the MM2/MM+ manuals (at the top of the contents page 3) so there are a maximum of three manuals needed to cover all aspects of MMBasic on the MZ For very good reasons Geoff decided that the MM+ manual would be an add on to the MM2 and would not stand alone. I merely followed that precedent with the MMX. I make everything I do, source ,firmware, documentation, gerbers etc. freely available. If you want the source of the MMX manual that is fine - attached below. I can't give you the source of the MM2 or MM+ manuals as they are Geoff's and I don't have them. I'm not aware you have ever requested any documentation that exists that I haven't made available and my responses to you in this thread were nothing more than factual explaining my approach to the documentation and where information could be found. 2019-02-21_211905_Micromite_eXtreme_Manual_2.zip |
||||
| goc30 Guru Joined: 12/04/2017 Location: FrancePosts: 435 |
first: A good manual is a manual who give response of your ptoblem. When you must open 2,3 or more others manuals, you stop to read this manual and you put it in trashbox. second: when a system needs several nested objects you have a lot of risk so that this system does not work any more after a certain time. We see it with languages like the "C" where we spend 90% of the development time to have good libraries (see for example the Arduino IDE). It is the same with manuals, especially when everyone lives his own life (and I don't speak about last manuals's versus that you have, or not). So if we have to waste hours before knowing if all of the manual needed are synchronous (and therefore have confidence in the manual), we ignore this manual. thirdly When you use a type of circuit or processor (for example stm32h7), you do not necessarily have all the family of processors using micromite, so you do not necessarily have all the documentation with you. If I have a car model, I do not need to have all the manuals of all the cars of the same manufacturer. I have many others point about using many maunuals, but it will be too long and the most important is to understand that "good manual make good job" Certainly you answered my question, but there are different ways to answer, and I found your way rather unpleasant. ok but why if it is always, on your manual (page10-11), did-you put pin's function for display and NOT for touch and sd card ?? there this approximation who make confusion. it is also confus because in H7 manual you put pin's for touch and sd, why not in mmx manual? to finish this discussion, do not forget that you are still in the development phase, with possible bugs (one day I will talk about the problem with the font n ° 6), and so if people ask you questions it is maybe they have not read the (and especially the others) manuals but also maybe because there is a bug. So you can answer more kindly and with less contempt. |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10572 |
To work with the STM32H7 I have to use: STM32H7 refrence manual 3247 pages STM32H743 datasheet 231 pages STM32H7 HAL manual 1514 pages plus various STM32 Application Notes. The documentation for the PIC32MZ is similar, datasheet, reference manual, drivers reference, application notes. Perhaps I should just put them in the trashbox and discontinue work on the Armmite H7 and MMX? The manual structure for the Armmite H7/ MMX, MM+, and Micromite is not going to change. If you want to provide any additional text or corrections to include in the Armmite or MMX manual as others have done previously I would be happy to consider it. |
||||
| lizby Guru Joined: 17/05/2016 Location: United StatesPosts: 3470 |
I always have 4 micromite manuals open--mm2, mm+, pi, and H7. Sometimes also the mmx, though I've never used an mmx board. Plus various hardware pdfs and different shed forum topics. Yes, there is some confusion involved in not having everything in one place, but there's always the forum to ask and search (and not only Geoff and Peter answer), and I'd rather have the two main developers actually developing as long as what is developed is eventually documented somewhere. "Eventually" may be a long time (from the point of view of us users) as features evolve. PicoMite, Armmite F4, SensorKits, MMBasic Hardware, Games, etc. on fruitoftheshed |
||||
Quazee137 Guru Joined: 07/08/2016 Location: United StatesPosts: 600 |
And even with a good doc's it can still be hard to fine what you need. I an learning to use the ESP modules and guess what there is a ton of documents from many sources. There are times when I can not see what I need because there are so many. And at those times it great to have forum that I can state what I am trying to do and what I have tried to find out first. For me this has been the best as they all help. Even when they use the harsh rtfm. They always point to a page and after reading that page I know can always ask more. Try that at some forums and you'll feel dumb for ever asking. But never here!!!!! MMBasic and all the hardware that has come from it could use a wiki of its own. And with that the documentation could be done by the many. We just need the structure or format that Geoff, Mather and others that have added to the knowledge here would like. Mather PLEASE know we do appreciate YOUR time, YOUR effort and YOUR expertise. That YOU have done here THANK YOU ! |
||||
CaptainBoing Guru Joined: 07/09/2016 Location: United KingdomPosts: 2171 |
Such a Wiki exists +1 |
||||
| goc30 Guru Joined: 12/04/2017 Location: FrancePosts: 435 |
have-you armite refernece manual plus armite datasheet plus armite OS manual?? no!! to work with armite we need pic mx manual plus pic mz manual + stm32 manual It is not same thing (for your info, in begining of armite, I have read stm32h7 datasheet to know how I can connect my periperals chips if a day I decide to create my own langage, i use datasheet and app's notes and other, but now I am just a simple user, and simple user need simple manual, not more! One thing you do not want to understand: You can create your manual as you wish, it is your project, but the more your manual is complete, the more users will leave you alone, the more your manual is incomplete and confusing, the more you will waste users' time and the more they you will waste your time asking "useless" questions |
||||
| BrianP Senior Member  Joined: 30/03/2017 Location: AustraliaPosts: 292 |
+100 |
||||
| goc30 Guru Joined: 12/04/2017 Location: FrancePosts: 435 |
you're lucky because when you ask a question, you have a complete and polite answer, I'm entitled to the minimum without explanations and with a condescending look see scorn of the kind "what cretin he can not even read a manual". After that it becomes tiring. question to know if I appreciate the work done on these projects or not, if you read my different posts here, you would know that I too said "bravo" to the authors and may times Finally, if I came on this forum it is also in the idea of sharing (I have 40 years of experience in industrial computing). But by being treated of high, it does not want to participate. For example: at the beginning of the project H7, and following problems with the ssd1963 display, I made and put here a small graphic test and benchmark program. What happened ?: nothing, not even a comment. after that does not make you want to continue! |
||||
| Page 1 of 2 |
|||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
