Search Results

Quote from sridhar.jonnavittula: “Nordic nRF52840 PCA10056 ” On the Segger forum, don't expect people to necessarily know what that is. It's their USB Dongle: nordicsemi.com/Software-and-To…ment-Kits/nRF52840-Dongle As such, it doesn't have an on-board J-Link - so how are you connecting to it?

No - there is no way to tell that !

Quote from eyal.gal: “any github sample out there ? ” You realise that Github has a search facility ...

See: porting nrf52840 project from makefile\ld script to ses + icf segger linkker script.

Quote from SEGGER - Nino: “The display change in the debug terminal is intended and will stay that way ” OK - fair enough. At what version did it change? And does it also affect the standalone RTT viewer? Quote from SEGGER - Nino: “There was a bug in the Nordic SDK ” I'm using SDK v15.3.0, which is specified to work with SES v4.12 - was that before the change?

With Linker errors, the linker doesn't always know the exact source line number - just that it was within a certain function.

Cross-post: devzone.nordicsemi.com/f/nordi…spi-nor-flash-on-pca10056

Oh, sorry - I see what you're saying now!

All the SDK examples have the same structure: forum.segger.com/index.php/Att…a2c7d0878f57243d2bef2b1d1 The 'ses' folder contains the SES project

Nordic provide ready-to-go SES examples - I'd suggest looking at one (or more) of those ...

Thanks. What I see is that, with the exact same image running in the Target, the behaviour is different between SES v3.40 and SES v4.22. Do there's no difference in what the code is doing/sending - purely in the way that SES is (mis)interpreting it. I didn't update the J-Link drivers, etc.

except to say that it would be nice for the log file to be (optionally) timestamped ...

I guess this thread can be closed - as the question about the log file is resolved. I'll make a separate thread for the issue with the Debug Terminal display: forum.segger.com/index.php/Thr…minal-broken-v3-40-v4-22/

See: 'Debug Terminal' (RTT) Window - log to file? An nRF52 project initially created in v3.40 - the RTT logging to the Debug Terminal worked fine. I rebuilt the project in v4.22, unmodified (apart from adding a log file) and the Debug Terminal window does not work properly - lots of output just appears as blank lines. (looks like only lines which had an explicit \n show?) Close v4.22 Connect v3.40 to the running target (without reloading code, or restarting the target) and the v3.40 Debug Termin…

I just tried it in v4.22, with an unmodified nRF52 project from v3.40. I rebuilt the project, downloaded, and run. In the GUI window, I get a whole load of blank lines where v3.40 showed trace. (looks like only line which had an explicit \n show?) In the log file, all the content is there - but there's an awful lot of extra blank lines

Quote from TylerD: “Please tell me that there is something similar in Segger Studio? ” Yes - that would be nice!

But the compiler (and linker) are pedantic - so, if you get these wrong, you will get errors! Quote from TxCodeMonkey: “my code example clearly did not have the extern qualifier ” Which is why it is (or can be) a definition - rather than a declaration. In your OP, both of the screenshots seem to be the same - did you mean one of them to be different?

Quote from TxCodeMonkey: “I accidentally added the declaration of a variable in an include fil ” A declaration should cause no problems; you mean you accidentally added a definition ? c-faq.com/decl/decldef.html

forum.segger.com/index.php/Att…a2c7d0878f57243d2bef2b1d1

Is it the find that's not working, or the replace? I think that "look in all solution" just searches the folder containing the Project file, and any folders below that? So, if your headers are not there, you have to tell it the "top" folder to start searching from ...