Cassio,

It looks to me like there's something missing in your 
CMakeLists.txt<https://github.com/clubcapra/LMS1xx/blob/master/CMakeLists.txt>. 
I miss the *install(...) *after this 
line<https://github.com/clubcapra/LMS1xx/blob/master/CMakeLists.txt#L15>
.


El viernes, 25 de octubre de 2013 18:27:25 UTC+2, Cássio Volcan escribió:
>
> Hi,
>
> I'm glad to say that the ros packages I've tried (roscpp_tutorials, 
> ros-comm, chatter and all this communicate very well with other machines) 
> are totally working on my (Arm) board. Thanks so much for the help until 
> now.
>
> So my next step is to record data from Sick LMS 2xx, 5xx and 1xx and 
> provide a map by it.
>
> I was taking a look at [1] and attempting to understand how I would set 
> parameters to it, but I'm not sure about it, yet. Because* *I keep not 
> able to create a new recipe with my own changes on code, like here [2] even 
> trying to use the Víctor's Tutorials [3]. Any advice?
>
> I was also trying to create a sicktoolbox and sicktoolbox_wrapper 
> [4][5][6] recipes, but It is not working until now. Someone thought to 
> create it?
>
> Please, take a look on my sicktoolbox_git.bb (just trying to create a 
> recipe to LMS1xx [7]):
>
> DESCRIPTION = "Laser drivers for Hokuyo and SICK laser rangefinders."
>
> SECTION = "devel"
>
> LICENSE = "TODO"
>
> LIC_FILES_CHKSUM = 
> "file://package.xml;beginline=16;endline=16;md5=2feaf30a620f46f06a4b016624acf46f"
>
> SRC_URI[md5sum] ="7e8b0cf12770756baff4aec8ed7958df"
>
> DEPENDS = "roscpp roscpp-serialization sensor-msgs"
>
> SRC_URI = "https://github.com/clubcapra/LMS1xx/archive/master.zip";
>
> SRCREV = "${AUTOREV}"
>
> S = "${WORKDIR}/git"
>
> inherit catkin
>
>
> And this errors appears:
>
> cassio@cassio-Ubuntu:~/projetos/my_poky/build-atmel$ bitbake sicktoolbox
> Loading cache: 100% |##############################################| ETA: 
>  00:00:00
> Loaded 1908 entries from dependency cache.
> Parsing recipes: 100% |############################################| Time: 
> 00:00:01
> Parsing of 1461 .bb files complete (1457 cached, 4 parsed). 1867 targets, 
> 45 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION        = "1.21.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-12.04"
> TARGET_SYS        = "arm-poky-linux-gnueabi"
> MACHINE           = "at91sam9x5ek"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.5+snapshot-20131025"
> TUNE_FEATURES     = "armv5 thumb dsp arm926ejs"
> TARGET_FPU        = "soft"
> meta-atmel        = "master:cf93c5213df976be11416a2857e62738175f8f04"
> meta              
> meta-yocto        
> meta-yocto-bsp    = "master:505114c13d29799a25379f7ce720d632616d8776"
> meta-ros          = "master:cc10dee5696e914273a8548f85b0c12043919cac"
> meta-oe           = "(nobranch):2a463dddcf76d7fa437e96f6cf0210143e97a904"
>
> NOTE: Preparing runqueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> ERROR: Function failed: do_install (log file is located at 
> /home/cassio/projetos/my_poky/build-atmel/tmp/work/arm926ejste-poky-linux-gnueabi/sicktoolbox/git-r0/temp/log.do_install.9578)
> ERROR: Logfile of failure stored in: 
> /home/cassio/projetos/my_poky/build-atmel/tmp/work/arm926ejste-poky-linux-gnueabi/sicktoolbox/git-r0/temp/log.do_install.9578
> Log data follows:
> | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 
> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
> | DEBUG: Executing shell function do_install
> | NOTE: make -j 3 
> DESTDIR=/home/cassio/projetos/my_poky/build-atmel/tmp/work/arm926ejste-poky-linux-gnueabi/sicktoolbox/git-r0/image
>  
> install
> | make: *** No rule to make target `install'.  Stop.
> | ERROR: oe_runmake failed
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_install (log file is located at 
> /home/cassio/projetos/my_poky/build-atmel/tmp/work/arm926ejste-poky-linux-gnueabi/sicktoolbox/git-r0/temp/log.do_install.9578)
> ERROR: Task 2 
> (/home/cassio/projetos/my_poky/meta-ros/recipes-ros/sicktoolbox/
> sicktoolbox_git.bb, do_install) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 1244 tasks of which 1243 didn't need to be 
> rerun and 1 failed.
> No currently running tasks (919 of 1250)
>
> Summary: 1 task failed:
>   /home/cassio/projetos/my_poky/meta-ros/recipes-ros/sicktoolbox/
> sicktoolbox_git.bb, do_install
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
> Sorry about so many question in a simple post.
>
> Thanks again!
>
> [1] 
> https://github.com/bmwcarit/meta-ros/tree/master/recipes-ros/slam-gmapping
> [2] http://thebattlegoeson.blogspot.com.br/2011/06/xyz.html
> [3] https://github.com/vmayoral/diving-meta-ros
> [4] https://github.com/rhuitl/laser_drivers
> [5] https://github.com/ros-drivers/sicktoolbox
> [6] https://github.com/ros-drivers/sicktoolbox_wrapper
> [7] https://github.com/clubcapra/LMS1xx
>
> Em sexta-feira, 11 de outubro de 2013 02h39min46s UTC-3, Lukas Bulwahn 
> escreveu:
>>
>>  Dear Cassio,
>>
>> the problem you report looks very similar to Issue 62 [1], which I 
>> reported a couple months ago.
>> This timeout on start up would also explain why the KeyboardInterrupt 
>> nondeterministically occurs at different code locations and sometimes 
>> occurs not at all.
>>
>> I will try out your suggestion to see if it also resolves the issue that 
>> I reported on the qemu virtual machine.
>>
>> Thanks for reporting the problem and the solution to it.
>>
>> To your second point: 
>>
>> The "core-image-ros-roscore" image only provides the packages to start 
>> and run roscore.
>>
>> However, if you have a look at the core-image-ros-roscore.bb file, you 
>> can extend that image simply by adding more packages, e.g., rosrun, rosbash 
>> and your own ROS packages, to IMAGE_INSTALL.
>>
>> Then your image should have those packages installed as well. Please 
>> report if some of them still have missing runtime dependencies. We have not 
>> tested all of the ROS packages in isolation and might have missing some 
>> dependencies.
>>
>> Lukas
>>
>> [1] https://github.com/bmwcarit/meta-ros/issues/62
>>
>>
>> On 10/10/2013 01:43 PM, Cássio Volcan wrote:
>>  
>>  Dear Lukas and Víctor
>>  
>>  
>>  Error ocurred when I tried to run roscore. The process could not 
>> contact master,  as can be seen below:
>>
>>   root@at91sam9x5ek:~# roscore  
>>   ... logging to 
>> /home/root/.ros/log/412f3d34-3103-11e3-b9d9-5162d3e8cd9f/roslaunch-at91sam9x5ek-856.log
>>  Checking log directory for disk usage. This may take awhile.
>>   Press Ctrl-C to interrupt
>>  Done checking log file disk usage. Usage is <1GB.
>>  2;roscore
>>  started roslaunch server http://at91sam9x5ek:34199/
>>  ros_comm version 1.9.49
>>  
>>   SUMMARY
>>  ========
>>  
>>   PARAMETERS
>>   * /rosdistro
>>   * /rosversion
>>  
>>   NODES
>>  
>>   auto-starting new master
>>  process[master]: started with pid [873]
>>  ERROR: could not contact master [http://at91sam9x5ek:11311/]
>>  [master] killing on exit
>>  Traceback (most recent call last):
>>    File "/usr/bin/rosmaster", line 35, in <module>
>>       rosmaster.rosmaster_main()
>>    File "/usr/lib/python2.7/site-packages/rosmaster/main.py", line 73, 
>> in rosmaster_main
>>      configure_logging()   
>>    File "/usr/lib/python2.7/site-packages/rosmaster/main.py", line 57, 
>> in configure_logging
>>      _log_filename = rosgraph.roslogging.configure_logging('rosmaster', 
>> logging.DEBUG, filename=filename)
>>    File "/usr/lib/python2.7/site-packages/rosgraph/roslogging.py", line 
>> 106, in configure_logging
>>      logging.config.fileConfig(config_file, 
>> disable_existing_loggers=False)
>>    File "/usr/lib/python2.7/logging/config.py", line 78, in fileConfig
>>       handlers = _install_handlers(cp, formatters)
>>    File "/usr/lib/python2.7/logging/config.py", line 156, in 
>> _install_handlers
>>      h = klass(*args)
>>    File "/usr/lib/python2.7/site-packages/rosgraph/roslogging.py", line 
>> 146, in __init__
>>      from rospy.rostime import get_time, is_wallclock
>>     File "/usr/lib/python2.7/site-packages/rospy/__init__.py", line 49, 
>> in <module>
>>      from .client import spin, myargv, init_node, \
>>    File "/usr/lib/python2.7/site-packages/rospy/client.py", line 51, in 
>> <module>
>>      import roslib
>>    File "/usr/lib/python2.7/site-packages/roslib/__init__.py", line 54, 
>> in <module>
>>      import roslib.stacks
>>    File "/usr/lib/python2.7/site-packages/roslib/stacks.py", line 46, in 
>> <module>
>>      import roslib.packages
>>    File "/usr/lib/python2.7/site-packages/roslib/packages.py", line 47, 
>> in <module>
>>      from subprocess import Popen, PIPE
>>    File "/usr/lib/python2.7/subprocess.py", line 432, in <module>
>>      import pickle
>>    File "/usr/lib/python2.7/pickle.py", line 165, in <module>
>>      __all__.extend([x for x in dir() if re.match("[A-Z][A-Z0-9_]+$",x)])
>>    File "/usr/lib/python2.7/re.py", line 137, in match
>>      return _compile(pattern, flags).match(string)
>>    File "/usr/lib/python2.7/re.py", line 228, in _compile
>>       cachekey = (type(key[0]),) + key
>>  KeyboardInterrupt 
>>  
>>  
>>  So I fixed the error increasing  the _TIMEOUT_MASTER_START = 10.0 
>> #seconds from python2.7/site-packages/roslaunch/launch.py to 15.0 seconds.
>>
>>  About the rosrun and rostopic, how can I run some executable like 
>> Publisher and Subscriber example without it? Either am I doing something 
>> wrong? I've done bitbake core-image-ros-roscore, but there is no rosrun and 
>> rostopic, for example. Have you done recipes for that on meta-ros?  
>>
>>  I was taking a look on Víctor's tutorials and attempt do provide a 
>> recipe from my issues, but I have no "opkg install *.ipkg" on my board. I 
>> was reading how to bitbake some image to be able to use that, but I do not 
>> have answers yet
>>
>>   
>> 

Reply via email to