LeafLabs Garden » Topic: Accessing registers

LeafLabs Garden » Topic: Accessing registers http://forums.leaflabs.com/topic.php?id=268 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:24:24 +0000 http://bbpress.org/?v=1.0.2 <![CDATA[Search]]> q http://forums.leaflabs.com/search.php poslathian on "Accessing registers" http://forums.leaflabs.com/topic.php?id=268#post-2084 Wed, 27 Oct 2010 19:57:14 +0000 poslathian 2084@http://forums.leaflabs.com/ We do not strictly adhere to this, but I wouldnt be surprised if it were true. We usually try and use the register names from the documentation - not the STPerihLib. In general, for peripherals, we use the struct trick, but there are some places (in the bootloader and in the USB related code) where a quick write to a system or control register happens as a one off via #define, this is something that needs to be more strictly standardized, but I dont know of any glaring exceptions off the top of my head. gbulmer on "Accessing registers" http://forums.leaflabs.com/topic.php?id=268#post-2079 Wed, 27 Oct 2010 19:03:11 +0000 gbulmer 2079@http://forums.leaflabs.com/ UPVOTE! poslathian - Does LeafLabs code always use the same register names as ST use in their documentation? poslathian on "Accessing registers" http://forums.leaflabs.com/topic.php?id=268#post-2066 Wed, 27 Oct 2010 13:56:12 +0000 poslathian 2066@http://forums.leaflabs.com/ We dont expose the raw registers in the wirish library, but we do touch them all over in libmaple. Feel free to take a look at the code there to see "our" way of doing things. There are many alternatives for direct register access on Maple. <a href="https://github.com/leaflabs/libmaple" rel="nofollow">https://github.com/leaflabs/libmaple</a> The simplest thing to do when starting from scratch is: 1) identify the register address (32 bit number) from the st documentation 2) #define SOMEREG 0x12345678 3) *(uint32*)(SOMEREG) = 0xWhatever or 3) uint32 myNum = *(uint32*)(SOMEREG) The next best thing to do is to use structs to wrap large peripherals together like the GPIO example you described. Probably the thing you want to do is to include the appropriate libmaple file and reference our definitions. For example: <pre><code>#include "spi.h"</code></pre> will give you access to things like: <pre><code>SPI->CR1 = blah; or blah = SPI->CRCPR;</code></pre> libmaple doesnt current expose the i2c registers, because hw i2c isnt in the library yet. Feel free to jack whatever you like out of: <a href="https://github.com/leaflabs/libmaple/blob/i2c/libmaple/i2c.h" rel="nofollow">https://github.com/leaflabs/libmaple/blob/i2c/libmaple/i2c.h</a> which was a prototype from a while back. This is a good question in general, if people would like more documentation on this issue, upvote here General Tree on "Accessing registers" http://forums.leaflabs.com/topic.php?id=268#post-2055 Wed, 27 Oct 2010 08:33:30 +0000 General Tree 2055@http://forums.leaflabs.com/ Hi everyone. I just started working with maple, and i cant seem to figure out how i can refer to the register of the Chip. In arduino, you just had to write down the mane of the register, something like: DDRB=0x01; PORTB=0x01; In maple, however, when i try to write the names of the registers, as mentioned in the official STM32F103 reference manual, the compiler says they are not defined. After searching the forum, i found out how to refer to the GPIO registers, e.g: (GPIO_BASE)->ODR = 0x01; but i couldn't find any documentation about the full list of "names" for all the registers. More specifically, i'm trying to set up an I2C network, without using the library functions provided, and i can't access the relevant registers. Any help finding the full list of these register names will be much appreciated!