CPU Identifier « LeafLabs Garden

LeafLabs Garden » Support » Maple IDE Support

CPU Identifier

(8 posts) (3 voices)

Started 3 years ago by Rei Vilo
Latest reply from mbolivar

Rei Vilo
Member

Hi!

Most of the Processing-based IDEs as LeafLabs MapleIDE have a unique identifier for the CPU.

Examples:
• Arduino: __AVR_ATmega328P__ __AVR_ATmega2560_
• chipKIT MPIDE: __32MX320F128H__ __32MX795F512L__
• Wiring: __AVR_ATmega644P__
• LaunchPad Energia: __MSP430G2452__ __MSP430G2553__ __MSP430G2231__
• MapleIDE: ?

What are the identifiers for MapleIDE and where are they defined?

This is critical for my embedXcode project, Xcode for embedded computing. Learn more about embedXcode at http://embedxcode.weebly.com/

Posted 3 years ago #
crenn
Moderator

*IDE Directory*/hardware/leaflabs/cores/maple/stm32.h

MCU_STM32F103RB LeafLabs Maple
MCU_STM32F103ZE LeafLabs Maple Native
MCU_STM32F103CB LeafLabs Maple Mini
MCU_STM32F103RE LeafLabs Maple RET6 edition

Posted 3 years ago #
Rei Vilo
Member

Thanks!

Posted 3 years ago #
mbolivar
LeafLabs

rei:

there are some changes to libmaple/stm32.h in the pipeline which will also make this easier. the development branch is wip-family-support:

https://github.com/leaflabs/libmaple/tree/wip-family-support/

we're updating the <libmaple/stm32.h> include to make it easier to interrogate libmaple about the current build target. new features include:

- STM32_MCU_SERIES: series for the current target. values are STM32_SERIES_F1, STM32_SERIES_F2, etc.
- (for STM32F1 targets): STM32_F1_LINE: line for the current target. values are STM32_LINE_PERFORMANCE, STM32_LINE_VALUE, etc.

thanks to anton eltchaninov, there's going to be value line support in the mainline libmaple tree! F2/F4 work is also getting closer. check out the code for more details. i've also started to update the documentation for this; for now, you can watch the leaflabs-docs branch libmaple-next for more:

https://github.com/leaflabs/leaflabs-docs/tree/libmaple-next

this work has been a long time coming. it's not ready for prime time yet, but we'll be sure to write a blog post when this branch is merged into master.

Posted 3 years ago #
Rei Vilo
Member

Two questions:

• Are you considering modifying the .build.mcu key —as in maple.build.mcu— in the boards.txt file?
• Are you considering using __STM32_SERIES_F1__ instead of STM32_SERIES_F1 for better readability?

Thank you!

Posted 3 years ago #
mbolivar
LeafLabs

• Are you considering modifying the .build.mcu key —as in maple.build.mcu— in the boards.txt file?

No; this is a libmaple-only change (and the Make-based libmaple build system doesn't use boards.txt files). Is there some reason to change those? For example, are they annoying you in some way?

• Are you considering using __STM32_SERIES_F1__ instead of STM32_SERIES_F1 for better readability?

No, and I don't think that's more readable.

Names with underscores before or after (and more so with _double_ underscores before _and_ after!) are often used to indicate that something special is going on. In fact, double-underscore identifiers are technically reserved for use by the compiler (though we do "cheat" and use them sometimes). If the AVR MCU identifiers are provided by avr-gcc, then that's one thing, but the STM32_SERIES_xxx are part of libmaple, and are just normal defines used to avoid magic numbers.

Posted 3 years ago #
Rei Vilo
Member

Thank you for your detailed answers.

• Are you considering modifying the .build.mcu key —as in maple.build.mcu— in the boards.txt file?

No; this is a libmaple-only change (and the Make-based libmaple build system doesn't use boards.txt files). Is there some reason to change those? For example, are they annoying you in some way?

Not at all.

I raised that question only to be ready for the next release, as embedXcode uses the .build.mcu key from boards.txt.

• Are you considering using __STM32_SERIES_F1__ instead of STM32_SERIES_F1 for better readability?

No, and I don't think that's more readable. [...]

The explanation is clear.

What's not easy to deal with is that none of the 6 IDEs —Arduino 0023 and 1.0, MPIDE, Energia, Wiring, MapleIDE— share the same norms, although all claim to be Processing- and Wiring-based or derived.

So you can imagine the complexity my embedXcode project has to cope with!

Posted 3 years ago #
mbolivar
LeafLabs

What's not easy to deal with is that none of the 6 IDEs —Arduino 0023 and 1.0, MPIDE, Energia, Wiring, MapleIDE— share the same norms, although all claim to be Processing- and Wiring-based or derived.

Yes, the situation is completely out of control. Thank you very much for your efforts to reconcile the various implementations!

Posted 3 years ago #

RSS feed for this topic

Reply

You must log in to post.