On Sun, Mar 10, 2019 at 8:30 PM John Dammeyer <jo...@autoartisans.com> wrote: > > > > > -----Original Message----- > > From: Chris Albertson [mailto:albertson.ch...@gmail.com] > > > > What market share gives a product familty is suport for a while eco > > system. For example I think the basic Arduino is not the best or > > most usfull platform but because it is so popular there is so much > > suport for it. ANy device likey has an Arduino library written for > > it and by know just about anyone can program an Arduno. > > The ESP8266 also has a nice following and Arduino support. > > > > Markit share gives you a wider base of support. . > > Totally agree! > > > > On Sun, Mar 10, 2019 at 4:26 PM John Dammeyer <jo...@autoartisans.com> > > wrote: > > > > > I upgraded the System Workbench for STM32 on my WIN-7 > > > > that was the root of the problem. That system is far to complex and > > forces you to learn how each version of the chip works in too much > > detail. > > > > Too true. The level of support for Microchip still exceed many of the other > systems. Having said that I'd still rather use MPLAB-8 compared to MPLAB-X > but I can see why Microchip had to go in that direction. Android and their > stupid little icons for everything currently rule the world and lately > everything has to have an android look and feel. > > > take that same STM32 and plug it into the Arduino IDE then simply do > > file->example->blink and press the "load" icon and the LED blinks. > > > > On ARM's embed system it is about the same, you select the blinky > > example, click "compile" then drag the *.bin file to the STM32 device > > and the LED blinks. > > > The biggest complaint about the Arduino is how effectively the IDE cleans up > after a compile. You can't really install breakpoints or single step through > the machine code to see where it's going wrong. > > > Arduino is best if the program logic can fit in one loop, mbed gives > > to a full RTOS. > > > > The System Workbench is almost never needed. It is used only if you > > are needing to do some very esoteric things wi the STM32 chip. > > > I disagree there. But it could be we work on different kinds of projects.
If you use What Arm Holding (those are the folks in the UK who own the ARM architecture) calls their "preffered development system" then you can drag the "blinky" demo to the STM32 chip and the LED blinks. You can also set breakpoints and step through lines of source code, read and modify memory. It all runs either on their ODE or you can set it up on Eclipse. If you use their IDE it is about as easy as Arduino. Another big deal is the source code runs on the full family of ARM M chips. You can do all this on Mac. Linux or Windows and the software open source. ARM does not make chips, they sell linces the STM, TI and everyone else so their motivation is to make the ARM chips so easy to use that everying will use them. You are correct about the lack of debug with Arduino. but they is intended only for the most simple uses andtheir target users would not know how to use a debugger. Arm's eMbed is targeted at professionals who are developing "edge devices", robots and so on. About the ICE, all ARM processors have hardware debuggers built-in. This helps a LOT with the case you described where you must debugging in the field. Just any notebook PC and a USB cable. I do remember the days when every chips needed it's own special hardware develpment system. Bt now JTAG works. > > One of my projects was located in the shop where I didn't have easy access to > the hardware. I had to do the debugging and testing with print statements > and add commands to the interactive monitor to figure out why the mix of a > number of pseudo intelligent systems weren't behaving. When I was able to > get it back into the lab and connect to the ICE where I could throw in break > points debugging became easier and faster. > > Both techniques worked. One just required hours while the other one required > minutes. > > I thought I'd lost my STM32F4 Discovery kit but just found it in the box with > the STMBL Servo parts. It's listed as one of the debugging modules for the > STMBL. In order to compile the code for the STMBLs two processors I ended up > creating a custom 16GB MicroSD for a Pi3B and wrote up a document exactly how > to 'make' a version and download it into the STMs on the STMBL. No IDE > required because I'm not really working with the code. Just doing a GIT for > the latest version and running make. But that was 11 months ago. Hard to > say if what I wrote up will make sense. > > So I will try to get the IDE working with the discovery kit. But truthfully, > I like the PIC32 better. > > John > > > > > > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Chris Albertson Redondo Beach, California _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
