0

I've set up a cross compiler using buildroot.
The target device is running Linux and it has a MIPS processor (it's a Dreambox dm500hd).
Buildroot configuration (only the things that I've changed):

  • Target configuration
    • Architecture: MIPS (little endian)
    • Architecture variant: Generic MIPS32
  • Toolchain configuration
    • [*] Enable C++ Support
    • [*] Enable compiler link-time-optimization support

I've followed the setup procedure and buildroot makes the compiler successfully (mips-linux-gcc and g++).
Hello World file (test-mips.cpp)

#include <iostream>

using namespace std;

int main() {
    cout << "hello world";
    return 0;
}

I can compile Hello World, but when I run it on the target device an error is thrown:

dm500hd:~$ ./test-mips
./test-mips: line 1: EL@4▒�P4: not found
./test-mips: line 1: syntax error: unexpected word (expecting ")")

The strange characters appear only if I build the compiler for little-endian: the error for programs compiled with big-endian is the same, but with spaces instead of ▒�.
I tried both little endian and big endian but the problem is the same. Have I done something wrong while configuring buildroot then?
Note: cat /proc/cpuinfo game me this result. Should I change the Architecture Variant?

system type             : BCM7413B1 STB platform
processor               : 0
cpu model               : Brcm4380 V4.4  FPU V0.1
BogoMIPS                : 403.45
cpu MHz                 : 405.010
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 32
extra interrupt vector  : yes
hardware watchpoint     : no
ASEs implemented        : mips16
shadow register sets    : 1
kscratch registers      : 0
core                    : 0
VCED exceptions         : not available
VCEI exceptions         : not available

processor               : 1
cpu model               : Brcm4380 V4.4  FPU V0.1
BogoMIPS                : 403.45
cpu MHz                 : 405.010
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 32
extra interrupt vector  : yes
hardware watchpoint     : no
ASEs implemented        : mips16
shadow register sets    : 1
kscratch registers      : 0
core                    : 0
VCED exceptions         : not available
VCEI exceptions         : not available
Axel Montini
  • 430
  • 6
  • 14

1 Answers1

2

Do you run on your target system the root filesystem generated by Buildroot ? Or do you just built your program with the Buildroot toolchain, and moved it to your existing filesystem on the target ?

In the latter case, then don't expect that to work out of the box. You have to make sure your program is ABI compatible with the reset of the system that already exists on your target system.

Thomas Petazzoni
  • 5,636
  • 17
  • 25
  • I really don't know if it's compatible, I'll try to install the generated fs and see if it works this way – Axel Montini Jul 22 '17 at 11:36
  • Thanks, installing the generated file system fixed the issue. Apparently the preinstalled software isn't ABI compatible with the programs compiled using buildroot's gcc/g++. – Axel Montini Jul 23 '17 at 13:03