EDIT: and of course, as I expected, flashing hung.
my hardware
Proxmark3 RFID instrument
bootrom: master/v2.3 2016-09-19 20:28:38
os: master/v2.3 2016-09-19 20:28:38
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8
uC: AT91SAM7S512 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 512K bytes. Used: 183707 bytes (35%). Free: 340581 bytes (65%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
When I executed flasher for bootrom update, it just hung in 2nd run. Of course, both leds (red, yellow) are on. I found similar case and the resolution was to comment out two lines in Makefile.common. It's already applied.
root@c63dd1e29cbf:~# ./client/flasher /dev/ttyACM0 -b ./bootrom/obj/bootrom.elf
Loading ELF file './bootrom/obj/bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00000bf0->0x00000bf0) [RWX] @0x298
Waiting for Proxmark to appear on /dev/ttyACM0. Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on /dev/ttyACM0.^C
root@c63dd1e29cbf:~# mknod /dev/ttyACM0 c 166 0
root@c63dd1e29cbf:~# ./client/flasher /dev/ttyACM0 -b ./bootrom/obj/bootrom.elf
Loading ELF file './bootrom/obj/bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00000bf0->0x00000bf0) [RWX] @0x298
Waiting for Proxmark to appear on /dev/ttyACM0. Found.
^C
docker run -it ubuntu bash
Oracle VM virtualbox 5.1.16 (w extension pack)
-> docker-machine upgrade default
-> docker version
Client:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Tue Apr 26 23:44:17 2016
OS/Arch: windows/amd64
Server:
Version: 17.03.0-ce
API version: 1.26
Go version: go1.7.5
Git commit: 3a232c8
Built: Tue Feb 28 07:52:04 2017
OS/Arch: linux/amd64
$ docker version
Client:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Tue Apr 26 23:44:17 2016
OS/Arch: windows/amd64
Server:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Wed Apr 27 00:34:20 2016
OS/Arch: linux/amd64
$ docker version
time="2017-03-15T10:18:29+01:00" level=inf
not available on Windows"
Client:
Version: 17.03.0-ce
API version: 1.26
Go version: go1.7.5
Git commit: 60ccb22
Built: Thu Mar 2 01:11:00 2017
OS/Arch: windows/amd64
Server:
Version: 17.03.0-ce
API version: 1.26 (minimum version 1.12)
Go version: go1.7.5
Git commit: 3a232c8
Built: Tue Feb 28 07:52:04 2017
OS/Arch: linux/amd64
Experimental: false
docker run -it --device="/dev/ttyACM0" --privileged -v $HOME/Downloads:/opt/proxmark3/Data iceman1001/proxmark3:1.7.0 /bin/sh
docker run -it iceman1001/proxmark3:1.7.0 sh
C:\Program Files\Docker Toolbox\docker.exe: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \"sh\": executable file not found in $PATH".
docker run -it iceman1001/proxmark3:1.7.0 /bin/sh
C:\Program Files\Docker Toolbox\docker.exe: Error response from daemon: oci runtime error: container_linux.go:247: start
ing container process caused "exec: \"/bin/sh\": stat /bin/sh: no such file or directory".
I wonder if you can add a runtime command at commandprompt, to execute a "/sh" for you
]]>Without ways of reproducing your problem, there is very little I can help with.
]]>Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory".
]]>