Thanks a lot! It helped
2015-03-15 23:24 GMT+02:00 Chris Johns :
> On 15/03/2015 1:35 am, Юрий Шевцов wrote:
>>
>> It fails and I don't why.
>
>
> Python development libraries are not installed. Please take a look at the
> various ways Python development libraries can be installed on Linux ..
> ht
Is there any final list of items? I have red through this thread
https://lists.rtems.org/pipermail/devel/2015-March/010175.html but I
didn't found any final list, except Joel's Sherrill suggestion
(https://lists.rtems.org/pipermail/devel/2015-March/010184.html).
Personally I would like to work on U
> On 3/16/2015 2:37 PM, Gedare Bloom wrote:
>> On Mon, Mar 16, 2015 at 3:21 PM, Joel Sherrill
>> wrote:
>>> I don't know if this has been posted or merged into the WIki.
>>> Alan, Gedare and I were discussing this earlier today. One thing
>>> to remember is that it is always possible something we
These are called USB HID :-)
2015-03-16 22:17 GMT+02:00 Joel Sherrill :
>
>
> On 3/16/2015 2:57 PM, Yurii Shevtsov wrote:
>>> On 3/16/2015 2:37 PM, Gedare Bloom wrote:
>>>> On Mon, Mar 16, 2015 at 3:21 PM, Joel Sherrill
>>>> wrote:
>>>>>
Patch:
diff --git a/testsuites/samples/hello/init.c b/testsuites/samples/hello/init.c
index d8fe450..8bf3604 100644
--- a/testsuites/samples/hello/init.c
+++ b/testsuites/samples/hello/init.c
@@ -28,7 +28,9 @@ rtems_task Init(
)
{
rtems_test_begin();
- printf( "Hello World\n" );
+ printf( "H
Hi)
Right now arm cross-compiler is being compiled. And of course I will
test Hello on actual RPi board. I would like to work with USB part of
task as I mentioned here
https://lists.rtems.org/pipermail/devel/2015-March/010462.html Which
part would yo like to take?
__
Since we are working around the same hardware, we definitely should
cooperate, share info and ideas. Feel free to ask questions. Inspire
each other!
Off-topic is allowed here, in small portions, of course ;-) I'm sure
we will be a good team!
P.S. Roll-call would be a great start for this thread)
__
commit 66ec94a3fc3c41470f90b7d20913ea1fafc019a9
make install prints this http://paste.kolibrios.org/show/394/
I copied _timeval.h (found it somewhere in rtems folder) to
rtemsbsd/include/rtems/bsd/sys/. It seemed like it helped but I got
new errors http://paste.kolibrios.org/show/395/
Result doesn'
I have this lines in FreeBSD driver:
| bcm2835_mbox_set_power_state(dev, BCM2835_MBOX_POWER_ID_USB_HCD, TRUE);
How should I replace it?
Thanks in advance)
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Joel, actually I have no idea. I just thought there is method
analogue, or somebody will point me to mailbox API
2015-06-01 22:44 GMT+03:00 Joel Sherrill :
>
>
> On 6/1/2015 2:32 PM, Yurii Shevtsov wrote:
>>
>> I have this lines in FreeBSD driver:
>>| bcm28
Since 'waf' requires four params and 'make' only three in config.inc,
I got confused with waf. Could anyone help me with waf params? Here is
my config.inc:
TARGET = arm-rtems4.11
BSP = c/raspberrypi/make
PREFIX = /home/gtament/development/rtems/src/b-rpi
Thanks in advance)
__
re. This path is exactly what is needed for
successful build
> See if this helps.
> Regards
>
>
>
> On Fri, Jun 5, 2015 at 10:47 PM, Yurii Shevtsov wrote:
>> Since 'waf' requires four params and 'make' only three in config.inc,
>> I got confused with waf.
Here is what I get now:
No valid arch/bsps found
where --rtems-bsps=arm/raspberrypi
also tried archs: armv6, arm-rtems4.11
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Ok, I figured it out, I should use path from rtems configure prefix
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
I compiled it from repo with latest commit
66ec94a3fc3c41470f90b7d20913ea1fafc019a9
Tried to run it on RPi with uboot. Boot approach is OK, because
testsuites from rtems samples are running normally. I thought ported
driver hangs system, but then I commented out USB init macro and also
added some p
This is "Please, pay attention" message. I really need help. Also I
still can't start working with the latest libbsd repo because of this
https://lists.rtems.org/pipermail/users/2015-June/029005.html
Thanks in advance, and excuse me, if my questions seem stupid
2015-06-13 13:56
Hello)
Now I have apps from libbsd testsuite running. But DWC OTG driver doesn't loads.
I added this lines to init01/test_main.c:
+SYSINIT_NEED_USB_CORE;
+SYSINIT_DRIVER_REFERENCE(bcm283x_dwcotg, nexus);
(I know it's bad hardcode)
If I run it. I get only this:
nexus0:
devctl: +nexus0 at o
This is ping message, with small update: the problem is not on the
linking stage, driver is linked to testsuite (checked with objdump)
2015-06-21 17:57 GMT+03:00 Yurii Shevtsov :
> Hello)
> Now I have apps from libbsd testsuite running. But DWC OTG driver doesn't
> loads.
> I ad
sd.txt about modifying code taken from freebsd.
> You also might find it more convenient to work on a branch instead of
> a master, and to avoid merge commits.
>
> Gedare
>
> On Thu, Jun 25, 2015 at 8:50 AM, Yurii Shevtsov wrote:
>> This is ping message, with small update: the pr
;
> }
>
> your device must get added. I would also set break points to the probe and
> attach functions of your device.
>
>
> On 25/06/15 14:50, Yurii Shevtsov wrote:
>>
>> This is ping message, with small update: the problem is not on the
>> linking s
; in console. So it doesn't step into loop.
Any ideas? Also I already had printfs in my driver's probe and attach,
also got no output.
> On 25/06/15 14:50, Yurii Shevtsov wrote:
>>
>> This is ping message, with small update: the problem is not on the
>> linking stage,
Any ideas? Maybe I did some typo? Maybe you can compile and try it in qemu?
2015-06-26 17:05 GMT+03:00 Yurii Shevtsov :
> 2015-06-25 16:00 GMT+03:00 Sebastian Huber
> :
>> I would set a break point to nexus_probe(). In this loop
>>
>> SET_FOREACH(nd, nexus) {
>>
ent section must be non-empty.
>
>
> On 27/06/15 16:39, Yurii Shevtsov wrote:
>>
>> Any ideas? Maybe I did some typo? Maybe you can compile and try it in
>> qemu?
>>
>> 2015-06-26 17:05 GMT+03:00 Yurii Shevtsov :
>>>
>>> 2015-06-25 16
Any news?
2015-06-29 19:50 GMT+03:00 Yurii Shevtsov :
> So, it is empty.
>
> .rtemsroset.bsd.nexus.begin
> 0x001104bc0x0 ./libbsd.a(rtems-bsd-nexus.c.16.o)
> 0x001104bc_bsd__start_set_nexus
> .rtemsr
ping
2015-07-01 17:20 GMT+03:00 Yurii Shevtsov :
> Any news?
>
> 2015-06-29 19:50 GMT+03:00 Yurii Shevtsov :
>> So, it is empty.
>>
>> .rtemsroset.bsd.nexus.begin
>> 0x001104bc0x0 ./libbsd.a(rtems-bsd-nexus.c.16
No I haven't. I tried to write driver stub, but I got same issueson
RPi. What are the qemu args? Can I run qemu in terminal?
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
And what to debug, if problem is on linkage stage? Or I misunderstood something?
2015-07-08 22:32 GMT+03:00 Yurii Shevtsov :
> No I haven't. I tried to write driver stub, but I got same issueson
> RPi. What are the qemu args? Can I run qemu
Ok, now the mechanism become clear. But still, why do I have troubles
with linker set??
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Which qemu build are you using? And what qemu args for xilinx zynq?
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
be non-empty.
>
>
> On 27/06/15 16:39, Yurii Shevtsov wrote:
>>
>> Any ideas? Maybe I did some typo? Maybe you can compile and try it in
>> qemu?
>>
>> 2015-06-26 17:05 GMT+03:00 Yurii Shevtsov :
>>>
>>> 2015-06-25 16:00 GMT+03:00 Sebastian Hub
and in what situation it can be empty.
2015-06-29 19:50 GMT+03:00 Yurii Shevtsov :
> So, it is empty.
>
> .rtemsroset.bsd.nexus.begin
> 0x001104bc0x0 ./libbsd.a(rtems-bsd-nexus.c.16.o)
> 0x001104bc_bsd__
correct name - no errors(warnings) and
no nexus.content section. How can you explain this??
2015-08-02 18:02 GMT+03:00 Joel Sherrill :
> On 08/01/2015 04:00 PM, Yurii Shevtsov wrote:
>>
>> During debugging of compiled Nexus module(driver) I found out that
>> content which suppo
Ping! Any news?
2015-08-05 18:29 GMT+03:00 Yurii Shevtsov :
> The problem is that rtemsroset.bsd.nexus.content doesn't exist in
> final elf. If I change driver's name in RTEMS_BSD_DEFINE_NEXUS_DEVICE
> macro, linker will throw an error
> (.rtemsroset.bsd.nexus.content+0x10
2015-08-06 23:36 GMT+03:00 Joel Sherrill :
>
>
> On 8/6/2015 3:22 PM, Yurii Shevtsov wrote:
>>
>> Ping! Any news?
>
>
> The people with experience with the libbsd code is quite small. :(
>
>>
>> 2015-08-05 18:29 GMT+03:00 Yurii Shevtsov :
>>>
What do you mean by "getting pulled"?
2015-08-06 23:48 GMT+03:00 Joel Sherrill :
>
>
> On 8/6/2015 3:42 PM, Yurii Shevtsov wrote:
>>
>> 2015-08-06 23:36 GMT+03:00 Joel Sherrill :
>>>
>>>
>>>
>>> On 8/6/2015 3:22 PM, Yurii Shevts
2015-08-07 0:08 GMT+03:00 Joel Sherrill :
>
>
> On August 6, 2015 3:57:40 PM CDT, Yurii Shevtsov wrote:
>>What do you mean by "getting pulled"?
>
>
> As I understood things, you had a linked executable but an empty section.
> Just curious if your devices were
Isn't this line enough?
SYSINIT_DRIVER_REFERENCE(bcm283x_dwcotg, nexus)
2015-08-07 0:23 GMT+03:00 Joel Sherrill :
>
>
> On 8/6/2015 4:16 PM, Yurii Shevtsov wrote:
>>
>> 2015-08-07 0:08 GMT+03:00 Joel Sherrill :
>>>
>>>
>>>
>>&g
15-08-07 0:34 GMT+03:00 Joel Sherrill :
>
>
> On 8/6/2015 4:29 PM, Yurii Shevtsov wrote:
>>
>> Isn't this line enough?
>> SYSINIT_DRIVER_REFERENCE(bcm283x_dwcotg, nexus)
>
>
> I was looking in nexus-devices.h since that is BSP specific.
> I wasn&#
Ping! Any news?
2015-08-07 0:41 GMT+03:00 Yurii Shevtsov :
> These macroses are placed here
> https://github.com/gtament/rtems-libbsd/blob/cf3f0fcafef3bcb9b0ec80d8c57e1304689ebace/rtemsbsd/include/machine/rtems-bsd-sysinit.h
> And of course I added proper lines to specific testsui
Ping! Any news?
2015-08-07 0:41 GMT+03:00 Yurii Shevtsov :
> These macroses are placed here
> https://github.com/gtament/rtems-libbsd/blob/cf3f0fcafef3bcb9b0ec80d8c57e1304689ebace/rtemsbsd/include/machine/rtems-bsd-sysinit.h
> And of course I added proper lines to specific testsui
I finally found the solution. All I need is to add
#include to a testsuite source
Now I have a rtemsroset.bsd.nexus.content section
2015-08-07 0:41 GMT+03:00 Yurii Shevtsov :
> These macroses are placed here
> https://github.com/gtament/rtems-libbsd/blob/cf3f0fcafef3bcb9b0ec80d8c57e130468
Hi)
For porting guide check this blogpost
http://ragustechblog.blogspot.in/2015/06/porting-driver-from-freebsd-to-rtems.html
Also read libbsd's README, especially "Rules for Modifying FreeBSD Source"
Can't say anything specific about USB HID and WLAN. Definitely WLAN will
require porting librarie
#x27;s actually 9.2 (from the readme)
>
> Please let me know how to get FreeBSD original code version which was used
> for libbsd porting work.
>
https://svnweb.freebsd.org/base/release/9.2.0/ It's Subversion
https://www.freebsd.org/doc/handbook/svn.html
>
> Best Regards,
&g
Ping
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
there how to use libbsd.py for adding new files(source, header files)
> easily ?
> Or, I want to know that libbsd.py file is used for which purpose.
>
You don't need any of *.py to do, what you want
> Best Regards,
> Thomas
>
> 2015-08-25 19:19 GMT+09:00 Yurii Shevtso
45 matches
Mail list logo
