Hi, our company bought two SIMtrace Hardware Kits. We want to use SIM forwarder https://github.com/kamwar/simlabTrace/wiki/res/bin/sim_forwarder-simtrace-at91sam7s128-flash_dfu.bin firmware in our project. but have problem with flashing it to the board.
in one way I installed toolchain as described at http://osmocom.org/projects/baseband/wiki/GnuArmToolchain
and made forwarder firmware - success1.
but any tries to flash it using dfu-util failed. tries was next: -------------------------- - from windows10 host using steps from https://github.com/kiibohd/controller/wiki/Loading-DFU-Firmware#windows - kii-dfu can`t flash it due to three dfu devices with NO serial numbers. Try using dfu-util with -a0 flag gives same result as later cases - DFU found, state idle, activate alternative=0 ... and nothing more. reruns not helps. reconnects with or w/o BOOTLOADER button gives same result - nothing. --------------------- - same win10 host with vmWare Ubuntu16.04 VM. tries to install using ubuntu. device shown on lsusb - dfu mode on. dfu-utils installed, toolchain too, firmware made OK. simtrace made too.
BUG1 experiment with simtrace gives output with wrong parsing of commands - may be you have to open bug case to resolve it. same results with usb2 on vm and usb3.
all tries to flash forwarder or reader to board failed on same place as before. tried with button at connect and using -ao and w/o button and using -i param (forgot number of interface for apps partition mb was -i1 ) - failed
- pure ubuntu 16.04 host. all above with same results. using usb3 port and usb2 extender. --------------------------------
Now the time to tell about second way - SAM-BA . here is another problem:
used http://osmocom.org/projects/simtrace/wiki/SIMtrace_Firmware
installed GnuArmToolchain http://osmocom.org/projects/baseband/wiki/GnuArmToolchain. as described on toolchain http://osmocom.org/projects/baseband/wiki/Toolchain link, included to PATH.
Trying to do:
git clone git://git.osmocom.org/openpcd.git cd openpcd/firmware make -f Makefile.dfu BOARD=SIMTRACE make BOARD=SIMTRACE DEBUG=1 TARGET=main_simtrace cat dfu.bin main_simtrace.bin > main_simtrace.samba cd ../..
failed on 3rd string: make -f Makefile.dfu BOARD=SIMTRACE - arm-elf-gcc not found! tries to rename arm-none-eabi gcc to arm-elf-gcc was not successful. so I cant produce your dfu.bin to use samba (I made it with success) with
cat dfu.bin my_forwarder.bin > my_forwarder.samba
Also, at the string cat dfu.bin main_simtrace.bin > main_simtrace.samba we see dfu.bin which is possibly dfu-boot-loader with wrong name which crashes brain of google so we have a BUG2: - to rename produced dfu.bin filename to something relative i.e. dfu-boot-loader-arm-SAM7.bin - to place link to binary of loader(s) at your instructions.
installed also crosstool-ng - but arm-elf-gcc not found too
So, we have fails using dfu-util and unmaking state of firmware which gives use of SAM-BA impossible due to insufficient dfu-boot-loader-arm-SAM7.bin aka dfu-bin.
This situation looks like failed "smoke test"...
Please help me to solve these issues.
Regards,
Alexandr
On 8 Feb 2017, at 16:25, Alexander Unger alexander.u@keepgo.com wrote:
Hi!
This situation looks like failed "smoke test"...
or just bitrot. The software was developed some time ago and you are using newer operating systems, tools, compilers. SIMtrace is a Free Software project and it lives by contributions.
- same win10 host with vmWare Ubuntu16.04 VM. tries to install using ubuntu. device shown on lsusb - dfu mode on. dfu-utils installed, toolchain too, firmware made OK. simtrace made too.
BUG1 experiment with simtrace gives output with wrong parsing of commands - may be you have to open bug case to resolve it. same results with usb2 on vm and usb3.
Apparently the dfu implementation in the bootloader and dfu-util are not compatible with each other.
http://lists.osmocom.org/pipermail/simtrace/2016-November.txt
We have a known working version and known broken, it should be reasonable to git bisect dfu-utils and then seeing what needs to be changed in dfu-util or the bootloader should be more clear then.
Now the time to tell about second way - SAM-BA . here is another problem:
used http://osmocom.org/projects/simtrace/wiki/SIMtrace_Firmware
installed GnuArmToolchain. as described on toolchain link, included to PATH.
Let me remove that link to OsmocomBB. The binary toolchain we referred to is long gone, the firmware predates the default usage of EABI.
E.g. change "Makefile" to use $(CROSS_COMPILE)cc and such and then see if make .. CROSS_COMPILE=arm-none-eabi- works then.
So, we have fails using dfu-util and unmaking state of firmware which gives use of SAM-BA impossible due to insufficient dfu-boot-loader-arm-SAM7.bin aka dfu-bin.
* dfu-util is known since November. Happy to accept patches * arm-elf-gcc.. wasn't aware of that but it is not clear that the EABI toolchain will generate a working binary.
https://osmocom.org/attachments/download/2147/main_simtrace_v05.samba
for the v05 files to be used with samba.
cheers holger
On 20 Feb 2017, at 00:23, Alexander Unger alexander.u@keepgo.com wrote:
Hey!
or just bitrot. I didn't said something bad about project... Sorry...
I didn't feel offended and think "bitrot" is more close to a fact. The simtrace firmware is a community project and has not been updated to work with latest compilers and tools.
E.g. using old code with new tools might or might not work or fail in other ways (e.g. compiles but doesn't run)
Is anywhere working executable of sam7 to flash our "brick"-card and revive it?
I don't know but sysmocom is using the utility to flash all the devices using SAM-BA.
<firmware.zip>
it should be a single Makefile for old and new compilers
regards