Hello, We are using the i-Link pod with an STR912FAW44X6, RevH chip while running J-Flash and find that some of the chips do not halt and so we cannot "connect". In one instance we have working code in thr STR912 but we cannot halt it or verify the code in the chip. What are we doing wrong? How can I halt the STR912? Thanks for any help.
Steve
PS After working with an additional ARM chip, we found that part was suddenly also "unable to halt". This chip was previously OK and we could erase, program and verify. Now I cannot even erase that chip since I cannot connect to it. It seems like something isn't set or initialized properly in the j-Flash.
PPS Our firmware engineer is using a j-Trace pod with the IAR Embedded Workbench IDE which also confirms that the 2 ARM chips cannot be halted or put into a debug mode. Also he is using a completely different circuit board assembly from a different product. The fault follows the ARM chips, even though they are executing a known version of the software OK. I have even sped up the JTAG to 1MHz and set "rx 0". Any ideas on how to halt these chips?
Steve
PS After working with an additional ARM chip, we found that part was suddenly also "unable to halt". This chip was previously OK and we could erase, program and verify. Now I cannot even erase that chip since I cannot connect to it. It seems like something isn't set or initialized properly in the j-Flash.
PPS Our firmware engineer is using a j-Trace pod with the IAR Embedded Workbench IDE which also confirms that the 2 ARM chips cannot be halted or put into a debug mode. Also he is using a completely different circuit board assembly from a different product. The fault follows the ARM chips, even though they are executing a known version of the software OK. I have even sped up the JTAG to 1MHz and set "rx 0". Any ideas on how to halt these chips?