Search Results

Using the pex file did the trick! I just didn't find that project in all my hunting, hopefully this will help others.. I've got some different G series micros - please can you point me to a example or a jlinkscript file for any G4 series? While the pex file works, it would be nice to see what it does as I plan to have a bootloader, so it may need some edits, it may not.. Many thanks for the support - Top rate as always!

Some progress: Comparing registers on a working STM32F4 with the STM32G4, I noticed some registers are not getting initialized. I have managed to get a TRACECLK by forcing GPIOE values in the View->Registers windows. // MODER 0x00002AA0 // OSPEEDR 0x00003FF0 // PUPDR 0x00001550 (I had to hunt for a STM32G474VE.svd file) Could the startup macro be writing to the old/wrong base address for PORTE? Note that address mapping are different for the STM32F and the STM32G, see below: STM32G4 GPIOE Addres…

I have managed to get trace working using IAR, but unable to get trace working when importing .out file into Ozone. I just get 'no data' message in trace window. No activity on the TRACECLK. I (quickly) played around with Embedded Studio and seemed to get similar results. Also, seemingly no SWO trace either (View->Code Profile) My steps to repeat are as follows: Create Cube project using 8MHz crystal direct (no PLL) and 4pin TRACE Load into IAR 8.50.5 and verify trace - It works. (But not reliab…

Try as I might - and even with the exceptionally good support received from SEGGER, I'm unable to get my STM32446E-EVAL board to give reliable trace connection at the upper clock ranges. I have two J-Trace debuggers (HW V1.0) and even designed my own PCB board as a public domain project board to be 'The model of perfect ETM trace connector layout'. It was to overcome the 'issues' that were present on the EVAL board. (routing, track splits, no series termination). After all that, Same problem. Te…

You can mark as solved. In summary, I can confirm the J-Link Plus can be self powered where as the J-Trace Pro can't - Reasons stated above. My 'licence prompt' issue was solved when I swapped my JLink with a JLink Plus. Thanks for your help. I did however find that the default project *.flash file needs a few extra lines to setup clocks otherwise the JTrace Pro has problems talking to my AT91SAM7S256 device. I have included below in case you get caught out - as I did.. This is how if fails: - E…

OK - so now I've specified hex file, its asking for a licence. I'm in the process of sorting out a J-Link Plus box for this setup. I'll update my profile when it comes through. Jon.

Hi, Thanks for the reply. Its a black box with "J-Link-ARM" V5.3 Its date code is 06-18 (YY-MM). I think it pre-dates the -KS versions. I have updated the serial number in my profile. Although it is not prompting me for a licence, can you confirm it is covered. I'm in the process of updating the production code away from JLink.exe scripts to JFlash.exe command line driven. Its is planned for production machine so I want to make sure its legit before I roll out. Thanks.

Exactly as described here too.. forum.segger.com/index.php?page=Thread&threadID=1289 'Power on' in Commander works fine for me too.. I am using JFlash V6.16g with both the JLink and JTrace PRO. AT91SAM7S256 micro Options->Project Settings->Production->Enable target power->checked This is reflected in the saved project file (section pasted below) [PRODUCTION] AutoPerformsErase = 1 AutoPerformsProgram = 1 AutoPerformsSecure = 0 AutoPerformsStartApp = 0 AutoPerformsUnsecure = 0 AutoPerformsVerify =…