Hello,
We noticed different behavior between J-Trace and I-Jet.
We use both with IAR.
It started on trying to trace code with stm32h743 eval board. we purchased j-trace for this issue, but it failed to trace code. Trying to do the same with I-Jet it succeeded without any issues.
The next thing we did is to move from eval board to our custom board.
The strange thing is that with I-Jet it does not go beyond
HAL_Init->HAL_InitTick->HAL_NVIC_EnableIRQ(TIM6_DAC_IRQn);
Immediately after thins function it gets continuous interrupts on TIM6, and does not get beyond HAL_Init.
(by the way, if I just program the application with I-Jet and attach to it after boot, everything works without issues, just the main steps with debugger get into problem).
Is there any idea why I-Jet behaves differently ?
Thank you,
