Search Results

Search results 1-14 of 14.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • I'm not 100% we are talking about the same thing. in the ld script a memory region that is defined RO only means that this region if written to by the program should generate compile time\link time error. All flash regions should be defined RO according to best practice since write to flash is not done by copying from register to mem but using a controller + buffer. This is what i mean and this is why i want to make it read only, memory regions that are just memory mapped regions like bootloader…

  • any update if it's indeed a bug or i am doing something wrong ?

  • Thanks for the response. My problem is not with the placement itself in memory, at least not yet. My problem is the top part of the generated ld script and the fact that all sections are with permission '(wx)' is there a way to use the flasdh_placement.xml file or the section placement macro to change those permission to what they should be ? eventually, and correct me if i'm wrong, the executable is linked using gnu ld which means it uses the generated ld script, and so what matters is the gene…

  • Hi. i'm using version 4.18 of the segger arm studio. The Nordik SDK indeed uses segments, i also tried playing with them as well. it did not change the ld script. yes it's consistent with all samples i tried and i tried a few. indeed i am setting the memory map in the project options. For ref i'm using nordik SDK 15.2 example: nRF5_SDK_15.3.0_59ac345/examples/dfu/secure_bootloader/pca10056_ble/ the memory file i used instead of the segment is already published here, but you can see the segments …

  • Hi. I have the following memory map file: Source Code (9 lines) when it's processed to generate an ld script for gcc this is the header of the ld script: Source Code (10 lines) I verified using all kind of parameters and trying to use options->build->memory segment playing with various RWX permissions, i always get (RW) eventually in the ld script. i tried to look in the generated ld script to see if i see somewhere lese restrictions for read only sections but i cannot find any. i'm using segger…

  • you realize i asked here since i didn't find any ?

  • the SDK examples don't use segger linker, they use one file for memory map (xml) and one for section placement and symbols (again, xml) the icf file for segger linker as far as i understand also needs some other startup files (assemble files that uses symbols and maybe generate startup code based on the icf file) . i could not find any sample using it.

  • where ? i would love to take a look! Do you have link ? a ref ? tell me where in the SDK it resides or where in segger studio it resides ?

  • I was looking in the example directory of sdk 152. and 15.3, i looked for a SES project example that uses SEGGER Linker. Could not find any i tried using grep to look for one of the icf file in the segger studio 'sample' directory. non was found. also i tried to look for all '.icf' files in the examples directory of the sdk and remove all entries coming from IAR projects, nothing was left. So there is no sample projects in nordik SDK with SES and segger linker ? any github sample out there ?

  • Hi. i read the segger linker manual so i have an idea how and what sould be changed from the ld script. do i still need to remove the thumb.s from the project and import segger linker's .S file from the examples ? does the segger linker contains the _Start symbol instead ? Any other major changes i should consider ?

  • Hi. I have nrf52832 based board that i want to develop for with segger embedded studio. however when development is complete i want to run it's builds on jenkins (using docker container builder i build myself). Since i'm not going to install segger's tool on that container and since nordik sdk nicly builds with GCC\G++ and gnu linker i've like to run those on the CI. i've seen icf file which is quite similar to an ld script and i've seen the ability to export a makefile, only this makefile needs…

  • i donwngraded the segger tools to version 6.42, now JLinkRTTClient works but i still can't see logs!!!! trying to use JLinkRTTLogger results in getting: Brainfuck Source Code (20 lines)when i connected my j-link after upgrading to 6.46 the fw was updated too, could have defected it maybe ?

  • I've installed the new tools yesterday, JlinkRTTClient does not connect to the 19021 port for some reason, telnet does! after trying to connect with JlinkRTTClient i can't connect with telnet either, ss command shows 2 connections is state TIME_WAIT and FIN_WAIT: Source Code (4 lines)it worked just fine in the previous version. connecting to feather nrf52 (adafruit/nordic) using segger edu mini EDIT: I just checked and apparently i can't see logs in any app using JLinkRTTViewer, JLinkLogger and …

  • Hi. After arduino was enough i decided to go to bare metal programming. i have an Atmega32p mcu and i would like to program it using my j-link edu. I assume i can use JLinkExe to save a bin program from meme area 0, but: 1. how to i physically connect the j-link ? i mean which wire goes to which pin of the mcu ? 2. is it possible to use j-link with avrdude ? what type do i choose in avrdude ? 3. same question regarding debugging with gdb and how to wire j-link to the mcu to do so. * if need be i…