Hi Rakesh,
Do you have any idea regarding using PRU to access the
flash ??
Thanks,
pratap
On Wednesday, August 20, 2014 at 3:39:12 AM UTC-5, rakesh.safir wrote:
>
> Hi Cmicali,
>
> I was successfuly able to access the ddr from C code through a little
> workaround though. I kept the OCP initialisation in inline assembly and
> rest of the code in C.
> It works like a charm :)
>
> Really for your help. Your example helped me solve the access issue.
>
> Cheers !!
> Rakesh
>
>
>
> On Tuesday, August 19, 2014 6:07:09 PM UTC+5:30, cmicali wrote:
>>
>> Rakesh,
>>
>> Sorry - when we did all the PRU work the c/c++ PRUSS compiler was not
>> available yet, so I haven't looked at it yet. Our code was pretty timing
>> sensitive so using pru assembly was probably the right way to go anyway.
>>
>> -c
>>
>>
>> On Tuesday, August 19, 2014 3:31:17 AM UTC-4, rakesh.safir wrote:
>>>
>>> Hi Cmicali,
>>>
>>> Really appreciate your help. I was able to run the example successfully.
>>>
>>> The linux side code for memory allocation was the same as suggested by
>>> you. Same was suggested on the post
>>>
>>> http://hipstercircuits.com/beaglebone-pru-ddr-memory-access-the-right-way/
>>>
>>>
>>> I'm trying to achieve the same through C/C++ toolchain for PRU-ICSS.
>>> There seems to be some issue in the way we access control registers in C.
>>> There seems some way through linker script. Can you or anybody else give
>>> me some pointers on how to access control registers in C Code.
>>>
>>> Cheers !!
>>> Rakesh
>>>
>>>
>>>
>>>
>>>
>>> On Monday, August 18, 2014 9:09:28 PM UTC+5:30, cmicali wrote:
>>>>
>>>> That file is in the repo, you can find it here:
>>>> https://github.com/sagedevices/am335x_pru_package/blob/master/pru_sw/example_apps/sage_pru.hp
>>>>
>>>> But yes, you are right on those constants.
>>>>
>>>> #define MEM_PRU_DATA0_BASE 0x00000000
>>>>> #define MEM_PRU_DATA1_BASE 0x00002000
>>>>> #define MEM_PRU_SHARED_BASE 0x00010000
>>>>
>>>>
>>>>
>>>> On Monday, August 18, 2014 7:38:32 AM UTC-4, TJF wrote:
>>>>>
>>>>> I didn't check all your code (*../sage_pru.hp* is missing, so I don't
>>>>> know how MEM_PRU_DATA0_BASE is defined).
>>>>>
>>>>> But: From the PRU-0 point of view, the address of DRam-0 is *0x0*
>>>>> (and DRam-1 is 0x2000).
>>>>>
>>>>>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
