Search Results
Search results 1-20 of 164.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hello Bjarne, could you please open a support ticket for your request? segger.com/support/technical-support/ (Product name = Flasher) Best regards Arne
-
J-Scope's jraw content
SEGGER - Arne - - General
PostHello Marco, yes, the sequence is also important. Regards Arne
-
J-Scope's jraw content
SEGGER - Arne - - General
PostHello Marco, these files do not have any metadata, it is just a dump of the incoming data stream. A small hint could be the file size: It must be a whole multiple of the sample block size. The sample block size would be for example 6 Bytes, if you have one 4 Byte variable and one 2 Byte variable. Without having a detailed look into the source, I'd suspect you specified something, which is not a whole multiple and that caused the crash. Is that correct? Regards Arne
-
J-Scope problems
SEGGER - Arne - - General
PostHello Philipp, the message indicates that it could not load JLinkARM.dll Probably some policies do not allow this on your PC, if J-Scope is not run as admin. You could try to copy the JLinkARM.dll to J-Scope's directory, maybe this works without admin rights, Best regards Arne
-
Quote from pavel4: “Hello I'm setting up a production programming where we need to flash three images per target, e.g. bootloader, configuration, firmware. This post asks a similar question but I don't think batch programming would work since the second file is not flashed from the next available address after the first file [SOLVED] Flasher Pro/Portable Standalone - Flashing multiple .hex files in to a single target I also want to avoid merging the images to a single file since one of the files…
-
Hello, I will close this thread, since you also opened a support ticket. Could you please avoid contacting us via multiple channels for the same topic? This might increase the handling time for support requests by generating unnecessary overhead. Thank you. Regards Arne
-
Hello, Flash memory, as it is used on the Flasher ATE, has a limited write endurance. We do not want to wear out the Flash memory by writing excessive log files. If you already have access to the TCP terminal with the detailed messages, why would you like to have these saved into a log file? Best regards Arne
-
Hello, the Flasher does not support "read-modify-write", therefore you'd need to create a second minimal data file which only contains the affected sector. This will be even faster than the "read-modify-write" procedure, because reading is not necessary. Best regards Arne PS: If you have additional questions, please use our technical support system: segger.com/support/technical-support/
-
Hello, yes, you can use multiple channels in the way you described. But every data packet has to contain data for each channel (8/12 bytes in your case). If you want to write your own application, I recommend our SDK: segger.com/products/debug-prob…nk/technology/j-link-sdk/ Best regards Arne
-
[ABANDONED] Flasher Portable Plus needs two attempts to fully program a Renesas microcontroller
PostHello, we are working on that. Since you get a positive result after the second programming attempt, we did not give it a high priority. Best regards Arne
-
Hello Tal, Could you please update the SDK? The current API provides access to CPU registers: // // API version v1.1 and higher // U32 (*pfReadReg) (U32 RegIndex); void (*pfWriteReg) (U32 RegIndex, U32 Value); For now, it should also be possible to use standard memory allocation, but we recommend to use the functions provided by the SDK. Best regards Arne
-
Hi Bjarne, file extensions are not to be added for universal flashloader projects, because it uses an .uni file instead of cfg/dat. So the extension .uni needs to be added to tell the flasher not to add wrong file extensions. Port 42 means the TCP port 42. Every module has a target channel on port 40+[module no.] This channel is used to get detailed information about the programming process. Regards Arne