STM32 Now Features 512KB Flash

stm32-connectivity-line.jpg
The venerable STM32 line of processors, featuring the ARM CORTEX-M3 core, have now been extended to include up to 512KB of flash memory on-board! That's a huge bonus for those Nav/AutoPilot projects that want to feature a lot of code!




Let's see who's the first DIY Droner to fill all that flash with new firmware features!

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • @Lew - yeah, breadboard is nice, but not helpful when you want to cram the prototype in a UAV. Debugging is pretty straightforward with Cortex-M3's built-in debugging over JTAG, and the board has a bunch of LEDs too. The board I am designing will have a bunch of prototyping spots too.

    Whether RTOS is a good idea or not depends entirely on application, so far I've found no need, but as you say it could make things easier, but then again it might not. At the moment, I don't see a need for RTOS in the forseable future of our UAV project, even with navigation, servo control and kalman filtering thanks to the glider being neutrally stable. But even with an unstable craft, I would have thought it would be better to have the raw throughput than the RTOS, but then again, I don't have any experience on the subject.

    If you want a beagleboard without the PC-centric connectivity, take a look at Gumstix boards, they even have a camera breakout board too. I may get myself one to play with if I have some time next year.
  • @Yuan - Regarding the BeagleBoard... I wish they made something similar, without all the PC-centric interfaces and such. Oh, and a micro JTAG connector would be nice, too (ala OpenPilot).
  • @Yuan - That's a nice little breakout board you've got there. I like a breadboard on-board, along with some basic I/O stuff (switches, indicators, etc). It makes prototyping much easier, and debugging with LED's comes in handy at times. I found that for an AHRS, MARG, IMU or INS, no RTOS is needed. But, if you start cramming other features onto the board (navigation, servo control, PPM decode/encode, etc) the RTOS makes life a lot simpler.

    Before starting my project, I contacted Zik Saleeba (Flying Fox) to find out how his choices had fared. He had to drop his project, due to being hired by a company that makes UAV's, but his parting words were "look at the CORTEX line... upward migration path."

    For object recognition, I'm not planning on anything fancy (at first). Thermal imaging, in the snow. Locate a cluster of pixels with a high heat signature, and take a snapshot of it (both thermal and regular). Let a human sort 'em out (was that a water pipeline, a deer, or a lost person?). Eventually, I'll try and expand it to wilderness rescue situations (lost campers, hikers, etc). We seem to get people lost in the snow here (Boise, ID) every year, so I'm starting with the more straightforward stuff.
  • @Lew - awesome, we're using a simple breakout board (NGX Blueboard LPC1768), there's no need for peripherals or RTOS, the LPC1768 itself costs just $11.40, and is definitely great value for performance. I'm currently designing a more compact breakout board for the LPC1768 as well (the board will actually be used by the research group that I'm part of for various projects, but I'll be trying to sneak some features into the design that'll be useful for us - spots for connecors to the GPS modules and the like, and hope nobody notices)

    We hope to incorporate a little computer vision into our UAV too but probably not advanced as body detection - starting out with horizon finding and IR beacon tracking for automated landing (mostly just Canny or Harris detectors rather than full-blown optical flow). Personally though, I'd like to move onto Cortex-M8, and I'm particularly interested in boards like Gumstix or Beagleboard.
  • @Yuan - Here's my STM32 development platform. The 72MHz clock and instruction set optimizations make it a good platform for running an RTOS, such as FreeRTOS, eCOS or uC/OS-II. The STM32F103ZET6 (512K) costs around $17.00 from DigiKey. As long as you don't need floating point, or can make due with the CORDIC fixed-point library, they're great. I was looking at the CORTEX-M4 (with floating point) as well as the "A" series, but another project has me working on the TI Delfino DSP chip (with floating point). However, TI is now coming out with a dual-processor micro, which has both a DSP and CORTEX in it! That may be an ideal platform for me; the CORTEX could integrate the navigation sensors, and the DSP could be available to do image recognition as well as optical flow.
  • @Lew - That looks awesome, I'll look into it. The main reason we're using LPC17xx is because that was the first ARM mcu I picked up, and I've basically stuck with them. Now going back and comparing with other Cortex-M3 mcu, it looks like the LPC1768's 100MHz clock and 512K flash makes it absurdly powerful compared to similarly priced Cortex-M3s (correct me if I'm wrong, I may be misreading the datasheets here).
  • PS - The STM32 has had 512KB flash available for quite some time now. The announcement was specific to the "value line" series of STM chips, which comprises their most power lean series of chips. These power misers now also come in 512KB flash versions.
  • @Yuan - I concur. It's actually a pleasure coding for ARM CORTEX based chips (STM32, LPC17xx, etc), and the assortment of I/O, timers, vectored interrupts and general design is fantastic. I chose the STM32 over the LPC because of the upward (compatible) migration path that is (and will be) available... including hardware floating point, multi-core processors and even hybrids (DSP + ARM chip: e.g., TI).

    Cortex-A9-MP-core_Big.gif

  • We're using an LPC1768 for our UAV project, it's also ARM Cortex-M3 chip featuring 512kb of flash. And having used it for a few months, I've found that Cortex-M3 to be pretty awesome, and I'm never going back to PICs ever again.

    I would highly recommend the STM32, LPC17xx and other Cortex-M3 microcontrollers to anyone - one great thing about ARM chips is that you're not locked into one supplier unlike PICs and Arduinos/ATMegas
  • Microchip has had this for a couple years now - but the arduino crowd will like it.
This reply was deleted.