I am new to embedded systems.I am working on a project where i have to program Tm4c123gh6pm chip from debugger of another tiva C series launchpad.I am connecting TCk,TMS,TD0,TD1 and ground pin of Tiva C series launchpad to other Tm4c123gh6pm . My instructor has said i have to use Uniflash to upload Hex file to Tiva C series launchpad so that i can program other Tm4c123gh6pm(which is without debugger).I donot understand why am i using uniflash, when i can just download flash through keil in to Tiva C series launchpad and then in to other Tm4c123gh6pm.When i tried to do the same with Keil to program other tm4c123gh6pm through launcpad (after removing jumper) following error occurs(JTAG could not be detected), but when the same program is uploaded to llaunchpad(jumper inserted) no error occurs.
When the same thing (after removing jumper) is done to program other Tm4c123gh6pm is done through Uniflash it is successful.
Why is there difference between flashing through KEil vs flashing through uniflash. I have googled internet but couldnot get any answer.
Does it support JTAG or just the SWD subset? Pins must be wired correctly, target needs to be powered and functional. Perhaps the firmware in the debugger is different or incompatible? Needs different drivers? Keil has a U-Link debugger, they code for that, other third party debuggers are dependent on drivers, functionality and wiring. If any part of the chain breaks the whole thing won't work, host of reasons why things don't work, you'll need to diagnose your own situation.
I have checked all connections but why is it that same hex file generated by keil when uploaded through uniflash gives correct result(expected data comes) but when same code is directly downloaded through keil gives no result. This is really strange.why should there be difference.
What does your instructor think?
I'd suppose it is not running the code downloaded, perhaps due to a jumper or option setting, causing it to run code from ROM rather than FLASH