On 07/20 04:51, Nikos Chantziaras wrote:
> On 19/07/17 19:57, [email protected] wrote:
> > Hi,
> >
> > My Buspirate v36a needs a newer firmware.
> > Unfortunately the flasher software is only
> > available in 32bit and I run a 64bit modern
> > Gentoo.
>
> Is this the tool?
>
> https://github.com/DangerousPrototypes/Bus_Pirate/blob/master/package/BPv3-firmware/pirate-loader_lnx
>
> That is a dynamically linked executable. I just ran it on my 64-bit Gentoo:
>
>
> $ ./pirate-loader_lnx
> +++++++++++++++++++++++++++++++++++++++++++
> Pirate-Loader for BP with Bootloader v4+
> Loader version: 1.0.2 OS: Linux
> +++++++++++++++++++++++++++++++++++++++++++
>
> pirate-loader usage:
>
> ./pirate-loader --dev=/path/to/device --hello
> ./pirate-loader --dev=/path/to/device --hex=/path/to/hexfile.hex [
> --verbose
> ./pirate-loader --simulate --hex=/path/to/hexfile.hex [ --verbose
>
>
Now it this case changes from "weird" to "mysterious":
I downloaded that file. Here it has the checksum (md5)
97122ea9062bbabcd04b2ffdee7b1bb8 pirate-loader_lnx
"file pirate-loader_lnx"says:
pirate-loader_lnx: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.8, with
debug_info, not stripped
but "ldd" states:
ldd ./pirate-loader_lnx
not a dynamic executable
How can "dynamically linked" and "not a dynamic executable" can be
true simultanously?
By the way: Executing that version prints
zsh: no such file or directory: ./pirate-loader_lnx
[1] 13112 exit 127 ./pirate-loader_lnx
(I tried this bash with the same rsult. Seems not to be a shell
interference here...)
Now it looks like a problem on my system...but everything works fine
here (beside the already reported problems while compiling
screen/lynx)....
Cheers
Meino
