Hi, There is a problem with my batch file compilation which was working with uvision3. I have a bootloader and application code.
I am trying to generate .bin file by coping code to my ER_IROM1 area. I am getting some error which i have mentioned below.
C:\Development\midas\Project Config>del /q ..\\Bin C:\Development\midas\Project Config>move ..\\Objects\midas.bin\ER_IROM1 ..\\Bin\ER_IROM1 The directory name is invalid. C:\Development\midas\Project Config>rmdir ..\\Objects\midas.bin/s/q The directory name is invalid. C:\Development\midas\Project Config>ren ..\\Bin\ER_IROM1 midas.bin The system cannot find the file specified. "..\Objects\midas.axf" - 0 Error(s), 0 Warning(s).
And this is my batch file,
C:\Keil\ARM\ARMCC\bin\fromelf.exe --bin ..\\Objects\midas.axf --output ..\\Objects\midas.bin del /q ..\\Bin move ..\\Objects\midas.bin\ER_IROM1 ..\\Bin\ER_IROM1 rmdir ..\\Objects\midas.bin/s/q ren ..\\Bin\ER_IROM1 midas.bin
So the bin file is not generated..
Any inputs?
Hi,
I want to create a bin firmware file with base start address of on-chip IROM1:0x10000. I want to use this bin file for remote firmware upgrading.
It was an old project where that batch was built and used. Now when i tried to compile it using latest Uvision its not happening. I dont have my project hardware available with me to check.
In the help file i noted another method for generating .bin file using below method. Let me know what i am trying here will yield expected result?
C:\>c:\Keil\ARM\ARMCC\bin\fromelf.exe --bin --output=c:\Development\midas\Bin\midas.bin c:\Development\midas\Bin\midas.axf
Using above command in command prompt i am able to generate a bin file. But can not verify the result now. can anyone tell me above method is correct or not?
But it's the same command. Just that you now have rotated the order of the parameters, and possibly fixed the path to a real, existing path.
So what do you expect people to think/say?
Hi, What i want to know is that if i upgrade my board using firmware file(midas.bin) using IAP routine in my bootloader, will it be success in upgrading or not?
May be you should get some file viewing tools (hex editors, file managers, etc) and inspect the file for yourself?
Compare the output with similar output from the prior tool chain, or prior releases of the binary for your product.
No one here knows enough about your product, or can inspect it or the binary produced to given you a remote diagnosis.
If you're incapable of inspecting the file, and evaluating it's correctness, you are in a better position than us to test it, and try an upgrade.