ARM Microcontroller Design Contest 2015

Welcome to the forum for the ARM Microcontroller Design Contest! Post your questions regarding the hardware, software or terms of the contest here. Members of the Keil Marketing Team will monitor this forum and will answer your questions.

 
  • Are university students from the United States allowed to participate? I'm not sure if this contest is region locked and I'd like to check before the proposal submission.

    Also, I apologize if this isn't the case, but is this page the actual forum? Do we make subtopics here for discussion or directly post comments such as this one?

    Thank you.

  • Hello to all,

    the "Contest Rules" say that we will receive a development board, but not a debugger.

    So, in case my proposal will be accepted, can I use my LPC-Link?

    TIA

    Clemente

  • Hello Ronobird,

    everybody is allowed to participate. The contest is not region locked. Also, if you have questions, just post them here and somebody from the team will answer it.

    Kind regards,

    Christopher

  • Hello Clemente,

    Most of the development boards come with an on-board debugger. The LPC Xpresso is an exception, but we have made sure that everybody will receive and additional LPCLink. If you have one already, of course you can use that as well.

    Kind regards,

    Christopher

  • Hello, My name is Dimitar Tomov, I'm B.Eng in Automation and Embedded Developer. I have a project, which I want to get to the next level, i.e develop it even further. And I have 2 question about my application into the Contest:

    1. Can such a project be proposal in this contest ?

    Info: As this is actually a project of mine, I have already build, but I look forward to Develop more, i.e Advanced Version of it.

    Build a new prototype of this ( Advanced ) Version 2, which to be one, two steps away from becoming an actual product OR used in real products.

    I.e be applicable, practical and so on.

    2. How crucial is the time of application in the contest - i.e sooner is better or doesn't matter ?

    As my Documentation about the current version (i.e V1) of the project is mostly in my native language ( Bulgarian ), I'll take time to translate the Documents I've wrote so far. Source Code & Schematics of course are in English ;-) As most of my notes, but the actual technical documents I have wrote - explanations, description, presentations, etc are mostly in Bulgarian.

    Thank You for Your time :-)

  • Hello Dimitar,

    in principle, we are open to every proposal that you might send us. If you want to enhance your current project, that is fine as well. The only thing that you need to use is CMSIS-Driver and the Middleware as this contest is supposed to show the advantages of both. Which controller are you using in your project? Depending on the device, more or less drivers are available.

    As for the timeline, you just need to make sure to have the project ready by June 30th as this is the deadline for submissions.

    I would suggest to sign up and we will check your proposal!

    Kind regards,

    Christopher

  • Of course :-) Great !

    My Hardware is exactly the STM32F429I-Discovery board.

    I use a lot of CMSIS-Driver and Middleware, specifically provided

    by ST for STM32F4 series of MCU through STM32F4Cube :-)

    I use it for base to start and accelerate my development.

    And to be honest it did accelerated my development, but at 2nd stage.

    At the beginning You actually have to invest more time, because of ...

    errors, bugs, etc, misconfiguration, missing or too much options ;-)

    Not 1 Ready-To-Use Abstraction is actually ready for immediate use :-)

    Here's a brief lists of the CMSIS-Drivers + STM32F4Cube-Drivers I use:

    1. ADC

    2. DAC

    3. USB

    4. DMA ...

    4.1. DMA for ADC

    4.2. DMA for DAC

    4.3. DMA for USB (it's a separate DMA controller)

    5. DSP -> FIR filter

    6. DSP -> Main App. Algorithm

    7. DSP -> Generating Samples for DAC

    8. GPIO -> simple Stepper Motor Control

    Middleware:

    9. USB MSC

    10. FATFS

    And other Drivers from CMSIS & STM32F4Cube and Middleware.

    NVIC, OSC, RCC, etc drivers are too obvious to mention in that list

    BTW: I like the OSS idea, only 1 Q - OSHW too or that is by choice ?

    BTW2: I actually can relate my project as ... type or to 1 of the templates:

    The USB Data Logger template is very close to my project, yet a bit different

    ( USB Data Logger )

    I'll submit my application in the following 48 hours.

    Again - Thank You for Your time christopherseidl !

  • Hello Dimitar,

    if you are accepted, you will receive 1 piece of the hardware of your choice (in your case I believe the STM32F429I Discovery kit).

  • Yes :-) It looks almost too good to be true :-) Too perfect, because my STM32F429I-Discovery board is now one of the parts in the prototype ( V1 ) and I want to keep it the way it is - working, ~100% stable, and as a base to go forward; to develop the 2nd Version :-) I.e for the new prototype of V2 I will need a 2nd STM32F429I-Discovery board

  • Hello-

    My name is Tom Skwara with MobileApp Systems in Orchard Park, NY USA.  I'm working on a project called ProtoPLC for Raspberry Pi, with the project's tagline being "ProtoPLC for Raspberry Pi is the ultimate add-on board for prototyping industrial solutions using the latest Raspberry Pi boards."  The project really is a system of hardware and software consisting of the following:


    • Raspberry Pi 2 Model B Single Board Computer
    • ProtoPLC Add-on Board
    • ProtoPLC Run-time System (RTS)
    • Proto Armour for Raspberry Pi Protective Enclosure

    In-a-nutshell, we are basically adding an ARM Cortex-M4 real-time engine to a Raspberry Pi, outfitting it with industrial I/O and power, and wrapping it all in a protective aluminum enclosure.  There are already a few boards on the market, but our solution differentiators are:


    • Includes an ARM MCU for real-time operation independent of the Raspberry Pi.
    • Includes industrial interface to process I/O and typical industrial power supply levels.
    • Integrates with thousands of rugged Proto Armour case products deployed around the world.
    • Is completely open-source: both hardware and software.
    • MCU is an ARM Cortex-M4 class device from STMicroelectronics.
    • The RTS is developed using CMSIS-RTOS and Keil RTX (project compiles under 32K).

    Similar to a previous post from Dimitar indicated, some work has already been done developing a prototype a board as a proof-of-concept rather than a finished product.  Several days ago we launched a Kickstarter campaign, mostly to bring awareness to the project and better understand market interest.  Here is a link to that campaign where more information can be found:

    ProtoPLC for Raspberry Pi by MobileApp Systems — Kickstarter

    My first question(s) is around MDK-ARM.  For my entire career, I've only used Keil tools for MCU development and am quite pleased with the experience and results.  For this project we've considered all available toolchains and are leaning heavily on MDK-Lite.  Given that our code compiles in less than 32K and that we are essentially giving away the source code, are there any licensing restrictions preventing us from selling a commercial product that was built on the free Lite version of MDK?  And on a related note, is the MDK-ARM license in the competition perpetual or limited to the duration of the contest?  If we exceed 32K is there something in-between MDK-Lite and MDK-ARM that would be affordable to our target audience (engineering students, researchers, junior engineers)?

    Secondly, since we are basically using the Raspberry Pi as the 'Middleware' layer and the MCU for low-level I/O drivers, ADC, etc., does this project fit in with the spirit of the contest?

    Thank you in advance!

    Tom Skwara

    MobileApp Systems

    Mobile Applications on a Mission

    Makers of Proto Armour for Raspberry Pi

    Explore Proto Armour / www.protoarmour.com

  • Hello Tom,

    that's quite the project you're working on, I hope it will be successful.

    To answer your questions:

    • There are no restrictions for commercial development with MDK-Lite, so feel free to sell your product built with it.
    • The license that is provided for the ARM MCU Design Contest is a 6 month temp license that will fall back to MDK-Lite status after that period.
    • We have several options for lower cost licenses, among them highly discounted educational licenses and term licenses.
  • Adding the Silicon Partners who are supporting the contest to the thread so it will appear to their followers

    Freescale Infineon Technologies NXPSTMicroelectronics

  • - What is the limit date to register

    - Can team participate?

  • Hello Asgard,

    there's no fixed date for registering. When we've run out of kits, we will close the registration. It will be on a first come, first serve basis. And yes, you can participate as a team, but you will get only one hardware platform and one software license.