This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Diego Fernandez Alonso diegoferalonso at gmail.comHi Holger; Thanks for the mail, I was on Holidays, now I'm trying to continue with the solution. >I well, what do you get when you run the above command on Ubuntu? On Ubuntu you can install >an arm???..binutils package as well, then use CROSS_COMPILE=arm???- before invoking the >dvnixload. Of course replace ??? with the right name. I don’t use Ubuntu. I followed a guide for installing an ARM Cross-Compilation but the problem is the same. http://docs.kali.org/development/arm-cross-compilation-environment apt-get install git-core gnupg flex bison gperf libesd0-dev build-essential zip curl libncurses5-dev zlib1g-dev gcc-multilib g++-multilib dpkg --add-architecture i386 apt-get update apt-get install ia32-libs cd ~ mkdir -p arm-stuff/kernel/toolchains cd arm-stuff/kernel/toolchains git clone git://github.com/offensive-security/gcc-arm-eabi-linaro-4.6.2.git export ARCH=arm export CROSS_COMPILE=~/arm-stuff/kernel/toolchains/gcc-arm-eabi-linaro-4.6.2 /bin/arm-eabi- Everything was ok. Now I launch the command: root at kali:~# ./dvnixload -p /dev/ttyUSB0 ubl-sysmobts-v2.elf u-boot-sysmobts-v2.elf -d 5 dvnixload info: Using cross compiler "/root/arm-stuff/kernel/toolchains/gcc-arm-eabi-linaro-4.6.2/bin/arm-eabi-" dvnixload debug1: Running command: test -f ubl-sysmobts-v2.elf dvnixload debug1: Running command: file ubl-sysmobts-v2.elf | grep ELF 1> /dev/null 2>&1 dvnixload debug1: Running command: test -f u-boot-sysmobts-v2.elf dvnixload debug1: Running command: file u-boot-sysmobts-v2.elf | grep ELF 1> /dev/null 2>&1 dvnixload debug2: baud_rate_index = 6 dvnixload info: Expecting messages: [BOOTME] [BOOTPSP] [I_ME] dvnixload debug3: [0] 0x20 dvnixload debug3: [1] 0x42 dvnixload debug3: [2] 0x4F dvnixload debug3: [3] 0x4F dvnixload debug3: [4] 0x54 dvnixload debug3: [5] 0x4D dvnixload debug3: [6] 0x45 dvnixload debug3: [7] 0x00 dvnixload debug1: Reading: [BOOTME] dvnixload info: [BOOTME] received dvnixload debug1: Running command: /root/arm-stuff/kernel/toolchains/gcc-arm-eabi-linaro-4.6.2/bin/arm-eabi-objcopy -R .ddrram -R .selfcopy --gap-fill 0xFF -S -O binary ubl-sysmobts-v2.elf /tmp/ubl.bin 2>&1 dvnixload debug2: run_cmd_get_string() dvnixload debug2: CMD = "/root/arm-stuff/kernel/toolchains/gcc-arm-eabi-linaro-4.6.2/bin/arm-eabi-readelf -h ubl-sysmobts-v2.elf | grep 'Entry point' | sed 's/.*\(0x[0-9a-f]*\)/\1/'" dvnixload debug2: OUTPUT count is 1 dvnixload info: Sending ACK sequence dvnixload debug2: Sending size = 8 dvnixload debug3: [00] 0x20 dvnixload debug3: [01] 0x20 dvnixload debug3: [02] 0x20 dvnixload debug3: [03] 0x20 dvnixload debug3: [04] 0x41 dvnixload debug3: [05] 0x43 dvnixload debug3: [06] 0x4B dvnixload debug3: [07] 0x00 dvnixload debug2: Written 8 characters dvnixload info: Sending CRC ($BC258B07) dvnixload debug2: Sending size = 8 dvnixload debug3: [00] 0x42 dvnixload debug3: [01] 0x43 dvnixload debug3: [02] 0x32 dvnixload debug3: [03] 0x35 dvnixload debug3: [04] 0x38 dvnixload debug3: [05] 0x42 dvnixload debug3: [06] 0x30 dvnixload debug3: [07] 0x37 dvnixload debug2: Written 8 characters dvnixload info: Sending size ($00002A88 bytes) dvnixload debug2: Sending size = 4 dvnixload debug3: [00] 0x32 dvnixload debug3: [01] 0x41 dvnixload debug3: [02] 0x38 dvnixload debug3: [03] 0x38 dvnixload debug2: Written 4 characters dvnixload info: Sending entry point ($00002214) dvnixload debug2: Sending size = 4 dvnixload debug3: [00] 0x32 dvnixload debug3: [01] 0x32 dvnixload debug3: [02] 0x31 dvnixload debug3: [03] 0x34 dvnixload debug2: Written 4 characters dvnixload info: Sending termination sequence dvnixload debug2: Sending size = 4 dvnixload debug3: [00] 0x30 dvnixload debug3: [01] 0x30 dvnixload debug3: [02] 0x30 dvnixload debug3: [03] 0x30 dvnixload debug2: Written 4 characters dvnixload info: Expecting messages: [BEGIN] dvnixload debug3: [0] 0x20 dvnixload debug3: [1] 0x42 dvnixload debug3: [2] 0x4F dvnixload debug3: [3] 0x4F dvnixload debug3: [4] 0x54 dvnixload debug3: [5] 0x4D dvnixload debug3: [6] 0x45 dvnixload debug3: [7] 0x00 dvnixload debug1: Reading: [BOOTME] dvnixload debug3: [0] 0x20 dvnixload debug3: [1] 0x42 dvnixload debug3: [2] 0x4F dvnixload debug3: [3] 0x4F dvnixload debug3: [4] 0x54 dvnixload debug3: [5] 0x4D dvnixload debug3: [6] 0x45 dvnixload debug3: [7] 0x00 dvnixload debug1: Reading: [BOOTME] dvnixload debug3: [0] 0x00 dvnixload debug3: [0] 0x12 dvnixload debug3: [1] 0x05 dvnixload debug3: [2] 0x0D dvnixload debug1: Reading: [ ] dvnixload debug3: [0] 0x51 dvnixload debug3: [1] 0x35 dvnixload debug3: [2] 0x15 dvnixload debug3: [3] 0x01 dvnixload debug3: [4] 0x20 dvnixload debug3: [5] 0x42 dvnixload debug3: [6] 0x4B dvnixload debug3: [7] 0x98 dvnixload debug3: [8] 0x54 dvnixload debug3: [9] 0x4D dvnixload debug3: [10] 0x45 dvnixload debug3: [11] 0x00 dvnixload debug1: Reading: [Q5 BK�TME] dvnixload debug3: [0] 0x20 dvnixload debug3: [1] 0x86 dvnixload debug3: [2] 0x4F dvnixload debug3: [3] 0x4C dvnixload debug3: [4] 0x54 dvnixload debug3: [5] 0x4D dvnixload debug3: [6] 0x8A dvnixload debug3: [7] 0x00 dvnixload debug1: Reading: [�OLTM�] dvnixload debug3: [0] 0x20 dvnixload debug3: [1] 0x42 dvnixload debug3: [2] 0x4D dvnixload debug3: [3] 0x4F dvnixload debug3: [4] 0x54 dvnixload debug3: [5] 0x4D dvnixload debug3: [6] 0x45 dvnixload debug3: [7] 0x00 dvnixload debug1: Reading: [BMOTME] dvnixload debug3: [0] 0x20 dvnixload debug3: [1] 0x42 dvnixload debug3: [2] 0x4F dvnixload debug3: [3] 0x4F dvnixload debug3: [4] 0x54 dvnixload debug3: [5] 0x4D dvnixload debug3: [6] 0x45 dvnixload debug3: [7] 0x00 dvnixload debug1: Reading: [BOOTME] dvnixload debug3: [0] 0x20 dvnixload debug3: [1] 0x42 dvnixload debug3: [2] 0x4F dvnixload debug3: [3] 0x4F dvnixload debug3: [4] 0x54 dvnixload debug3: [5] 0x4D dvnixload debug3: [6] 0x45 dvnixload debug3: [7] 0x00 Again the message [BEGIN] is being expected, but only [BOOTME] is received. I'm not sure if maybe I should use the recovery mode pressing the reset button for trying by other way. Thanks so much. Diego. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20150824/23ad7098/attachment.htm>