On 07/09/2014 02:38 AM, Vince Hsu wrote: > Hi Stephen, > > Sometimes I got the following errors with the tegra-uboot-flasher. > Re-executing the script might work. Sorry for the slow response; I was on vacation. ... > downloading miniloader to target at address 0x4000e000 (136920 bytes)... > miniloader downloaded successfully > tegrarcm: retreiving platform info > Traceback (most recent call last): ... > File "./tegra-uboot-flasher", line 49, in run > subprocess.check_call(cmd, cwd=cd) > File "/usr/lib/python2.7/subprocess.py", line 511, in check_call > raise CalledProcessError(retcode, cmd) > subprocess.CalledProcessError: Command '['/tmp/tmpcgEOsW/flasher.sh']' > returned non-zero exit status 1 I have not seen this. The error message simply means that the tegrarcm binary exited with a non-zero error code. I think you'll need to run the tegrarcm command under gdb (or add more debug prints) to find out why. Passing the --debug and --save-work-dir parameters to tegra-uboot-flasher will help you see exactly which commands and data files tegra-uboot-flasher is executing, so you can run the same thing manually. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
