LeafLabs Garden » Topic: is there a board specific constant defined?

LeafLabs Garden » Topic: is there a board specific constant defined? http://forums.leaflabs.com/topic.php?id=10467 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:07:45 +0000 http://bbpress.org/?v=1.0.2 <![CDATA[Search]]> q http://forums.leaflabs.com/search.php tlgosser on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-25689 Fri, 03 May 2013 11:23:20 +0000 tlgosser 25689@http://forums.leaflabs.com/ In other words it only compiles what's needed for the specific target. tlgosser on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-25688 Fri, 03 May 2013 10:57:01 +0000 tlgosser 25688@http://forums.leaflabs.com/ If you don't want to waste a few cycles you can make your choice precompiler with an #if directive. These are all just workflow choices and I tend to be very lazy. If you can figure out how to use those option bytes please post how you did it. tdc218 on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-25680 Thu, 02 May 2013 21:48:48 +0000 tdc218 25680@http://forums.leaflabs.com/ tlgosser - Hiding a board definition value somewhere in flash would probably work fine for a small project but I don't think it would scale well for a larger program as this is a significant trade off of a one time decision during compilation versus many bazillions of run time decisions. Also the program would have to carry all of the code for all of the boards it might need to run on, whereas the former only compiles what's needed for the specific target. gbulmer - thank you for the info on the option bytes - definitely an interesting tidbit. tlgosser on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-25582 Tue, 30 Apr 2013 22:46:07 +0000 tlgosser 25582@http://forums.leaflabs.com/ Interesting. That looks like something to try on a rainy day. Of course the lazy thing to do is just tie an extra pin to ground or something as an identifier and I often go that route! gbulmer on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-25579 Tue, 30 Apr 2013 10:12:39 +0000 gbulmer 25579@http://forums.leaflabs.com/ tlgosser - "So the option bytes are here... 0x1FFF F800 -0x1FFF F80F." Yes, the "Option Bytes" are 16 bytes in the "Information block". They are described in PM0075 "Programming manual", "STM32F10xxx Flash memory microcontrollers": <a href="http://www.st.com/web/en/resource/technical/document/programming_manual/CD00283419.pdf" rel="nofollow">http://www.st.com/web/en/resource/technical/document/programming_manual/CD00283419.pdf</a> The option bytes are described in Table 9. "Description of the option bytes" on page 20. They are rather obscure. Using them is mentioned in RM0008 (search for "option bytes") but I don't think that explains what they are, or how to program them. For example, they are mentioned as containing nRST_STDBY and nRST_STOP. The most helpful statement is "For further information on the User Option Bytes, refer to the STM32F10xxx Flash programming manual." "Is it just those 2 bytes that are available for user data?" Yes, AFAIK. Other bytes control write protection of Flash memory, configure the watchdog timer, and how stop and standby work. "How would you write to just those two bytes?" Section 2.3.5 "Option byte programming" describes the process, which is basically the same as programming Flash memory, except their is an extra bit (OPTPG bit in the FLASH_CR) which must be set. tlgosser on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-25556 Tue, 30 Apr 2013 00:27:07 +0000 tlgosser 25556@http://forums.leaflabs.com/ I've never heard of this. So the option bytes are here... 0x1FFF F800 -0x1FFF F80F. EEPROM.h makes us erase and program an entire flash page in order to write data. Although we can read words anywhere. Is it just those 2 bytes that are available for user data? How would you write to just those two bytes? gbulmer on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-25534 Mon, 29 Apr 2013 17:37:30 +0000 gbulmer 25534@http://forums.leaflabs.com/ I believe there are two 'option bytes' for user data at 0x1FFFF804 which would keep that magic-number out of Flash, which might make things simpler. tlgosser on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-25428 Sat, 27 Apr 2013 18:58:27 +0000 tlgosser 25428@http://forums.leaflabs.com/ //To read your board's 'label': #include <EEPROM.h> uint16 AddressWrite = 0x10; uint16 DataRead = 0; void setup(void){ EEPROM.read(AddressWrite, &DataRead); } void loop(void){ delay(3000);//let the serial monitor wake up SerialUSB.print("Confirmed. Board No.: "); SerialUSB.println(DataRead, HEX); } tlgosser on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-25427 Sat, 27 Apr 2013 18:57:08 +0000 tlgosser 25427@http://forums.leaflabs.com/ /* It is also possible to write a permanent identifier to flash memory for each board - a number that stays in memory even when you load a new program. This way you can write code for ALL of your boards in one program! But only run one set of instructions. I find this makes things dramatically simpler. To write an identifier you will need to put this eeprom lib in your 'libraries' folder: <a href="http://akb77.com/g/stm32/maple-eeprom-emulation-library/" rel="nofollow">http://akb77.com/g/stm32/maple-eeprom-emulation-library/</a> */ //Program to write a permanent 'label' on your board: #include <EEPROM.h> uint16 DataWrite = 9;//lets just say this is board no. 9 uint16 AddressWrite = 0x10; void setup(void){ EEPROM.write(AddressWrite, DataWrite); } void loop(void){} tlgosser on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-25426 Sat, 27 Apr 2013 18:24:59 +0000 tlgosser 25426@http://forums.leaflabs.com/ Maple's predefined values can be helpful since they are portable: BOARD_LED_PIN, BOARD_BUTTON_PIN, and the SPI and serial USART serial pins. <a href="http://leaflabs.com/docs/lang/api/board-values.html" rel="nofollow">http://leaflabs.com/docs/lang/api/board-values.html</a> tdc218 on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-24507 Sun, 14 Apr 2013 12:19:57 +0000 tdc218 24507@http://forums.leaflabs.com/ @ala42 - thanks very much, this appears to work. @iainism - the point is to be able to compile the same project for different boards without having to change anything other that the make command line (or the BOARD environment variable). I had been doing something similar to what you suggest, but this required me to change two things every time I switch boards. I can't tell you how many times I'd forget to change the pin defs and got some seriously weird (and time consuming to troubleshoot) symptoms as a result. ala42 on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-24361 Wed, 10 Apr 2013 17:43:20 +0000 ala42 24361@http://forums.leaflabs.com/ In the libmaple boards.h file you find <pre><code>#ifdef BOARD_maple #include "maple.h" #elif defined(BOARD_maple_native) #include "maple_native.h" #elif defined(BOARD_maple_mini) #include "maple_mini.h" #elif defined(BOARD_maple_RET6)</code></pre> Check if these defines also work in your main code. iainism on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-24353 Wed, 10 Apr 2013 07:40:01 +0000 iainism 24353@http://forums.leaflabs.com/ I may be missing the point here, but can't you 'just' create a header file for each hardware configuration? i.e. /pathTo/RET6/hwSpecific.h ----------------- #define MyPin 3 #define otherRet6Stuff /eof /pathTo/mini/hwSpecific.h ----------------- #define MyPin 5 #define otherMiniStuff /eof main.c then has "#include <hwSpecific.h>" with the include path being varied between /pathTo/mini/ and /pathTo/RET6/ as required by setting up the makefile (or command line, but seriously, use a makefile) appropriately. tdc218 on "is there a board specific constant defined?" http://forums.leaflabs.com/topic.php?id=10467#post-24311 Sun, 07 Apr 2013 19:48:20 +0000 tdc218 24311@http://forums.leaflabs.com/ Is there a value defined that I can use to determine what board I'm compiling for? Eg something like: #ifdef BOARD_RET6 #define MyPin 3 #endif #ifdef BOARD_Mini #define MyPin 5 #endif I'm using the Unix command line tool chain if it make any difference.