>
>
>
> *Ah, ok got it. Page 25 of the PRU reference manual table 92 I2C1
> 0x4802_A000 == base address for i2c1*
>
On Thu, Mar 3, 2016 at 9:56 AM, Micka wrote:
> Hi,
>
> William, I don't get it ..
>
> Where do you see that the constant C2 == 0x4802_A000
>
>
> Le lun. 2 nov. 2015 à 01:27, Wi
Hi,
William, I don't get it ..
Where do you see that the constant C2 == 0x4802_A000
Le lun. 2 nov. 2015 à 01:27, William Hermans a écrit :
> Ah, ok got it. Page 25 of the PRU reference manual table 9
>
> 2 I2C1 0x4802_A000 == base address for i2c1
>
> On Sun, Nov 1, 2015 at 5:06 PM, Willia
Thx GianFranco,
I managed to understand your code, which is well made.
My first test was to verify if I was able to compile the program and see if
something goes out of the I2C 1.
And yes it works ! I saw something on the scope.
Now, I have to modify your code to be able to use the AD7997.
Th
What kind of script ?? Can you post that? I would have thought mux-clock is
done in a gel file
Sent from Yahoo Mail on Android
From:"Gianfranco Rosso"
Date:Wed, Nov 4, 2015 at 6:47 AM
Subject:Re: [beagleboard] Re: I2C driver by PRU
hello Micka,
in attach you'll find the ar
On Sun, 1 Nov 2015 17:06:02 -0700, you wrote:
>By the way, I keep seeing stuff like "C2" in PASM assembly in regard to the
>PRU's. Wish I could figure out what it is . . . Seems to be some sort of
>constant "register" ? And there is more than just C2, but I have not found
>any reference to those y
Ah, ok got it. Page 25 of the PRU reference manual table 9
2 I2C1 0x4802_A000 == base address for i2c1
On Sun, Nov 1, 2015 at 5:06 PM, William Hermans wrote:
> By the way, I keep seeing stuff like "C2" in PASM assembly in regard to
> the PRU's. Wish I could figure out what it is . . . Seems to
By the way, I keep seeing stuff like "C2" in PASM assembly in regard to the
PRU's. Wish I could figure out what it is . . . Seems to be some sort of
constant "register" ? And there is more than just C2, but I have not found
any reference to those yet :/
On Sun, Nov 1, 2015 at 5:01 PM, William Herm
Hi Micka,
I do not think he is using and driver. When speaking of the I2C module, I
believe hes speaking of the physical on chip module. But this . . .
#define I2C1_BASEC2//base registri I2C1 nella
tabella
translated from Italian to English . . . *I2C1 base registers
Hi,
I'm interested by what you have done. I want to use i2c to read analog
value from a component.
The first solution that I found was to bitbang the i2c. But you, you use
the i2c driver which is nice.
Could you give us the peace of asm code that you use to interface with the
MCP23017. And if y
I've also posted this in I2C topic, the solution is there:
http://beagleboard.org/Community/Forums/?place=msg%2Fbeagleboard%2FDAXyYJOrDIc%2FDZ8WKkRWaC0J
Il giorno lunedì 13 luglio 2015 09:49:20 UTC+2, Gianfranco Rosso ha scritto:
>
> I want to manage the I2C1 module by the PRU, in order to inter
FIXED ! :-)
It happens that the I2C1 module was not activated into the PRCM (Power,
Reset and Clock Management): the module clocks was not supplied (both
interface and functional) as it was hold in idle status.
So module registers was not really accessible (and of course the module
function was
Just for completeness, I2C1 module seems correctly active and working:
root@beaglebone:~# i2cdetect -l
i2c-0 i2c OMAP I2C adapterI2C adapter
i2c-1 i2c OMAP I2C adapterI2C adapter
i2c-2 i2c OMAP I2C adapter
I finally installed CCS6 and use USB100v2 JTAG interface (after soldering
the header into BBB pads).
It looks like as I2C1 module never goes out of reset status: RDONE flag
into I2C_SYSS register is always 0 even after writing I2C_EN=1 into I2C_CON
register (and also, SRST=0 into register I2C_S
13 matches
Mail list logo
