Search Results
Search results 1-7 of 7.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Quote from SEGGER - Alex: “Hi all, now we have a final confirmation from CodeCourcery. It is a problem in the Sourcery G++ Lite version. It is not a problem on the GDBServer side. It will be fixed in a new version of Sourcery G++. - Alex” hi alex, thank you very much for the information. now we need to wait for the 'new' version best regards robert
-
hmmm, i am using a standard installation of eclipse and the gnuarm plugin. installing the segger sw is a matter of running the installation app. do not 'see' what could cause the problem. i will switch my development pc ... maybe i can reproduce the problem. or it works thanks for your help. robert
-
i am happy to do so. regards robert
-
upsla
Posthello, what i tried is to download the program into the internal flash memory. some bytes have been written but then the verify fails. this is my understanding. the device itself is a stm32f103vet6 regards robert
-
one step hurther
Posthello alex, SEGGER J-Link GDB Server V4.25g (beta) JLinkARM.dll V4.25g (DLL compiled Mar 29 2011 15:04:28) Listening on TCP/IP port 2331 J-Link connected Firmware: J-Link ARM Lite V8 compiled Jan 31 2011 18:38:46 Hardware: V8.00 S/N: 228001252 WARNING: CPU core not found. J-Link found 0 JTAG device, Total IRLen = 0 JTAG ID: 0x00000000 (ARM9) Free mode: To be used for non-commercial and evaluation purposes only. Connected to 127.0.0.1 Reading all registers Read 4 bytes @ address 0x00000000 (Data …
-
codesourcery
Postok, i switched over to a olimex jtag and encountered the same issue the the packet beeing to long. switching back to an the previous version of codesourcery did solve the problem parially. i can programm a stm32f103vet6 device but no success when debugging. to do so i had to kill previously allocated gdb instances. is there a config entry to er-use already running gdb instances? robert
-
hi, i am using a stm32f103vet6 - and you can quess it. i have the same problem. i tried different commands and setups - nu luck up to now. last we year we did use 4.10 and 4.14i with success programming a stm32w103. but i don't know how to go back from the firmware update which did come with 4.24g. robert