Brian Beuken

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 60 total)
  • Author
    Posts
  • in reply to: Switching to cross compiling #10740
    Brian Beuken
    Participant

    I made some progress which may help others.

    I decided to update my Raspberry pi toolchain (do this without a project loaded) and clean my PC side directories, then allow the suggested directories on sync sysroot to download to my PC

    at the end of the sync, I was informed some functions were not compatible with windows and was offered a fix, which I accepted.
    But sadly on 1st attempt to build, with short file names it still was unable to locate GLESv2 EGL and bcm_host, it just ffailed to find the ..\opt\vc\lib dir.

    I removed the short names and provided full directory names in the additional linker options and that passed the tool change test, but an attempt to compile for deploy, only provides a large list of DSO missing errors mostly coming from bcm_host.so but I was able to locate and add so it now looks like this

    D:\SYSProgs\arm-linux-gnueabihf\sysroot\opt\vc\lib\libGLESv2.so D:\SYSProgs\arm-linux-gnueabihf\sysroot\opt\vc\lib\libbcm_host.so D:\SYSProgs\arm-linux-gnueabihf\sysroot\opt\vc\lib\libEGL.so D:\SYSProgs\arm-linux-gnueabihf\sysroot\opt\vc\lib\libvchiq_arm.so d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/opt/vc/lib/libvcos.so

     

    I then realised that perhaps linking the static.a files was a mistake  and switched to .so file

    Finally, this worked, my project now does indeed compile and deploy, and run.

    It turns out with all .so files I didn’t need to add the 2 apparently missing DSO’s D:\SYSProgs\arm-linux-gnueabihf\sysroot\opt\vc\lib\libvchiq_arm.so d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/opt/vc/lib/libvcos.so

    it does deploy and run now, though I have not worked out how to send my projects assets to the target? There seems to be no auto synchronization process for that as exists on the build on target options?

     

     

     

     

     

    • This reply was modified 7 years, 9 months ago by Brian Beuken.
    • This reply was modified 7 years, 9 months ago by Brian Beuken.
    in reply to: Switching to cross compiling #10738
    Brian Beuken
    Participant

    hard coding the directories and removing the short names does allow it to compile, but the linker then reports a issue  related to an unresolved reference to

    vchiq_release_message in bcm_host

     

    Im going to attempt a complete upload of the Pi’s directories to see if that resolves this but it is confusing, that I cannot simply use synchronise sysroot, and have it look at the library directories and produce the correct settings?

     

    edit, a full sync of the entrie dir structure, short lib names still not found

    adding full path names, allows compile but link throws up countless undefined references

    So still unablet to successfully link or deploy to target.

     

     

    • This reply was modified 7 years, 9 months ago by Brian Beuken.
    in reply to: Switching to cross compiling #10736
    Brian Beuken
    Participant

    It provides a very long list of directories it attempt so find the missing files in .a and .so formats, and then reports a fail

     

    attempt to open failed
    attempt to open /opt/vc/lib/libGLESv2.so failed
    attempt to open /opt/vc/lib\libGLESv2.a failed
    attempt to open /usr/lib/arm-linux-gnueabihf/libGLESv2.so failed
    attempt to open /usr/lib/arm-linux-gnueabihf\libGLESv2.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/libGLESv2.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9\libGLESv2.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/libGLESv2.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf\libGLESv2.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/libGLESv2.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc\libGLESv2.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/lib/libGLESv2.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/lib\libGLESv2.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/arm-linux-gnueabihf/libGLESv2.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/arm-linux-gnueabihf\libGLESv2.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/libGLESv2.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib\libGLESv2.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf/libGLESv2.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf\libGLESv2.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/libGLESv2.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib\libGLESv2.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/q/gnu/linux/raspberry-jessie/out/arm-linux-gnueabihf/lib/libGLESv2.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/q/gnu/linux/raspberry-jessie/out/arm-linux-gnueabihf/lib\libGLESv2.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/local/lib/libGLESv2.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/local/lib\libGLESv2.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/lib/libGLESv2.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/lib\libGLESv2.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/lib/libGLESv2.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/lib\libGLESv2.a failed
    attempt to open /opt/vc/lib/libEGL.so failed
    attempt to open /opt/vc/lib\libEGL.a failed
    attempt to open /usr/lib/arm-linux-gnueabihf/libEGL.so failed
    attempt to open /usr/lib/arm-linux-gnueabihf\libEGL.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/libEGL.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9\libEGL.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/libEGL.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf\libEGL.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/libEGL.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc\libEGL.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/lib/libEGL.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/lib\libEGL.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/arm-linux-gnueabihf/libEGL.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/arm-linux-gnueabihf\libEGL.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/libEGL.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib\libEGL.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf/libEGL.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf\libEGL.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/libEGL.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib\libEGL.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/q/gnu/linux/raspberry-jessie/out/arm-linux-gnueabihf/lib/libEGL.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/q/gnu/linux/raspberry-jessie/out/arm-linux-gnueabihf/lib\libEGL.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/local/lib/libEGL.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/local/lib\libEGL.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/lib/libEGL.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/lib\libEGL.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/lib/libEGL.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/lib\libEGL.a failed
    attempt to open /opt/vc/lib/libbcm_host.so failed
    attempt to open /opt/vc/lib\libbcm_host.a failed
    attempt to open /usr/lib/arm-linux-gnueabihf/libbcm_host.so failed
    attempt to open /usr/lib/arm-linux-gnueabihf\libbcm_host.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/libbcm_host.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9\libbcm_host.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/libbcm_host.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf\libbcm_host.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/libbcm_host.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc\libbcm_host.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/lib/libbcm_host.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/lib\libbcm_host.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/arm-linux-gnueabihf/libbcm_host.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/arm-linux-gnueabihf\libbcm_host.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/libbcm_host.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib\libbcm_host.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf/libbcm_host.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf\libbcm_host.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/libbcm_host.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib\libbcm_host.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/q/gnu/linux/raspberry-jessie/out/arm-linux-gnueabihf/lib/libbcm_host.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/q/gnu/linux/raspberry-jessie/out/arm-linux-gnueabihf/lib\libbcm_host.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/local/lib/libbcm_host.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/local/lib\libbcm_host.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/lib/libbcm_host.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/lib\libbcm_host.a failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/lib/libbcm_host.so failed
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/lib\libbcm_host.a failed
    attempt to open /opt/vc/lib/libpthread.so failed
    attempt to open /opt/vc/lib\libpthread.a failed
    attempt to open /usr/lib/arm-linux-gnueabihf/libpthread.so failed
    attempt to open /usr/lib/arm-linux-gnueabihf\libpthread.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/libpthread.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9\libpthread.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/libpthread.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf\libpthread.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/libpthread.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc\libpthread.a failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/lib/libpthread.so failed
    attempt to open d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/lib\libpthread.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/arm-linux-gnueabihf/libpthread.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/arm-linux-gnueabihf\libpthread.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib/libpthread.so failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/lib\libpthread.a failed
    attempt to open d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf/libpthread.so succeeded
    opened script file d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf/libpthread.so
    opened script file d:/sysprogs/bin/../arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf/libpthread.so
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/lib/arm-linux-gnueabihf/libpthread.so.0 succeeded
    /lib/arm-linux-gnueabihf/libpthread.so.0 (d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/lib/arm-linux-gnueabihf/libpthread.so.0)
    attempt to open d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf/libpthread_nonshared.a succeeded
    d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/bin/ld.exe: cannot find : Invalid argument
    d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/bin/ld.exe: cannot find -lGLESv2
    d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/bin/ld.exe: cannot find -lEGL
    d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/bin/ld.exe: cannot find -lbcm_host
    collect2.exe: error: ld returned 1 exit status

     

    But, the files are indeed in place on my laptop in D:\SYSProgs\arm-linux-gnueabihf\sysroot\opt\vc\lib

    which is where the synchronisze sysroot put the directories, the list of failed directies does not include

    d:\sysprogs\bin\../arm-linux-gnueabihf/sysroot/opt/vc/lib  int its searches. Am I missing something obvious here?

     

     

    • This reply was modified 7 years, 9 months ago by Brian Beuken.
    in reply to: Switching to cross compiling #10720
    Brian Beuken
    Participant

    Im having a few problems I wonder if you can advise

    I sent up a cross compiling configuration and Synced sysroot to include all my relevent directories

    The compiler builds ok but the linker fails as its unable to find the 1st 3 of these libs GLESv2 EGL bcm_host pthread openal alut

    The directory (/usr/lib/arm-linux-gnueabihf) containing libGLESv2_static.a  and .so have been copied to my dev PC ok

    but the toolchain test fails with

    Tool arguments: -Wl,–start-group “C:\Users\Brian Beuken\AppData\Local\Temp\/VisualGDB_ToolchainTestProgram.o” -o “C:\Users\Brian Beuken\AppData\Local\Temp\/VisualGDB_ToolchainTestProgram” -Wl,-gc-sections -L/opt/vc/lib -L/usr/lib/arm-linux-gnueabihf -lGLESv2 -lEGL -lbcm_host -lpthread -lopenal -lalut -Wl,–end-group
    d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/bin/ld.exe: cannot find -lGLESv2
    d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/bin/ld.exe: cannot find -lEGL
    d:/sysprogs/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../arm-linux-gnueabihf/bin/ld.exe: cannot find -lbcm_host
    collect2.exe: error: ld returned 1 exit sta

    Im not sure why it fails to find the files, any ideas?

    • This reply was modified 7 years, 9 months ago by Brian Beuken.
    in reply to: Switching to cross compiling #10650
    Brian Beuken
    Participant

    That sounds like an excellent solution, I’ll try that this week and update you.

     

    in reply to: Debugging Raspberry Pi, almost impossible now #10584
    Brian Beuken
    Participant

    one of my students who is better with linux, suggested a cleaner faster approach, open a terminal and try this. It compiles much faster.

    wget https://ftp.gnu.org/gnu/gdb/gdb-7.12.tar.gz -P ~/Downloads/
    tar vxzf ~/Downloads/gdb-7.12.tar.gz -C ~/Downloads/
    sudo apt-get update
    sudo apt-get upgrade -y
    sudo apt-get install libreadline-dev -y
    sudo apt-get autoclean
    cd ~/Downloads/gdb-7.12
    ./configure –prefix=/usr –with-system-readline && make -j4
    sudo make -j4 -C gdb/ install
    sudo shutdown -r 0
    gdb –version

     

    in reply to: Debugging Raspberry Pi, almost impossible now #10582
    Brian Beuken
    Participant

    Sorry I meant GDB 7.7.1

     

    in reply to: Debugging Raspberry Pi, almost impossible now #10579
    Brian Beuken
    Participant

    I’ve managed to work out what to do, posting here for the benefit of others who like me may not be very comfortable with linux and are having debugging hangs. The Rasbian version of GDB seems to be faulty, its also a little old at version 7.8.xxx with a specific Rasbian build.

    Downloading the newer generic GDB (7.12.1) and unzipping it to a working folder was fine… then I tried to use

    ./configure –prefix=/usr –with-system-readline && make

    however it seems  the readline libs were missing so this failed.. so I installed them with, you should avoid my error, and install it before attempting the GDB build.

    sudo apt-get install libreadline-dev

    I repeated the configure/make process this time for a successful result (note it takes quite some time)

    This does not actually seem to replace the rasbian GDB, which still reported itsself as 7.8 Rasbian, but by then copying the new built version to a more accessable directory with
    sudo cp gdb/gdb /usr/local/bin/gdb

    After a reset, GDB now reports a new 7.12.1 version, not specific to Rasbian.

    I don’t really know the final copy step was needed, or if a reset was all that was needed, but regardless I now have a later generic GDB in place and it seems on initial tests on a piece of code that hanged every time, to be much more stable in fact I’ve single stepped through a very complex piece of code with no problems.
    Of course this may not be an ideal fix, if you need the specific Rasbian GDB, I do not know what functions it provides and may now be lost, but for the moment at least I am very happy not to be hanging the instant I trigger a breakpoint.
    I will report back if I find any issues with this fix.

     

     

    • This reply was modified 7 years, 9 months ago by Brian Beuken.
    in reply to: Debugging Raspberry Pi, almost impossible now #10578
    Brian Beuken
    Participant

    Thank you for the link.

    I will try to follow the methods used.

     

    in reply to: Debugging Raspberry Pi, almost impossible now #10575
    Brian Beuken
    Participant

    ok, I know nothing at all about linux, can you provide an idiots guide to let me do that?

     

    in reply to: Debugging Raspberry Pi, almost impossible now #10572
    Brian Beuken
    Participant

    A little digging found this

    http://gdb-prs.sourceware.narkive.com/a6QecxfF/bug-gdb-20143-new-arm-rpi2-debugging-top-fails-build-gdb-nrlhe3-gdb-7-7-1-dfsg-gdb-frame-c-472

     

    it would appear to be an issue with the target GDB, but I have no idea how to resolve, is there any work around or is there a way to revert to a known working version of GDB?

    in reply to: Debugging Raspberry Pi, almost impossible now #10571
    Brian Beuken
    Participant

    I managed to widen the window,

    /home/pi/dev/gdb-7.7.1+dsf/dsb/frame.c:472: internal-error get_frame_id: Assertion ‘fi->this_id.p’ failed

     

     

    in reply to: Debugging Raspberry Pi, almost impossible now #10570
    Brian Beuken
    Participant

     

    Ok I did that and it comes up with a list of timings but at the point of the GDB Timeout window the Session window reports and arroe at grame.c:472: internal-error: get_frame….. (I can’t scroll the window to see the rest)

    A Problem internal to GDB has been detected, further debugging may prove unreliable, Quit this debugging session (y or n)

    Brian Beuken
    Participant

    ok I’ll switch to msbuild and see what different that makes and report back.

     

    in reply to: Constant freezing on debugging #9777
    Brian Beuken
    Participant

    It just locks up totally, the whole of Visual Studio freezes. Sometimes it comes back, but more often it stays locked, I can see the network lights blinking in a regular fashion but not other activity

    After a while I have to power down the Raspberry, at which point I get the  taking too long dialogue. and I can then unfreeze VS.

     

    I have not tried killing any processes, I’ll see if that makes a difference when I try again later

     

Viewing 15 posts - 46 through 60 (of 60 total)