« first day (4914 days earlier)      last day (71 days later) » 

1:35 AM
@rdtsc I was a trade show and spoke with two CNC machine shops. The largest bar stock feeder they had was 1 5/8 inch for a CNC lathe. 1 1/4 inch for Swiss lathe.
 
 
4 hours later…
5:50 AM
@Lundin Does the contents of the EEPROM remain intact when the STM32 is reprogrammed through JTAG?
I tried to figure that out from the ST docs a few weeks ago, but I couldn’t find the definitive answer.
The reason I’m asking. I’ve worked with a different MCU family where the contents of the EEPROM is wiped during programming with ICD. I was told that they use EEPROM as a buffer during reprogramming.
We had calibration parameters in the EEPROM, and reloading the EEPROM every time was inconvenient during firmware development. So we added an external EEPROM and kept the calibration there.
 
6:13 AM
@NickAlexeev It typically depends on your setup. If the microcontroller source maps variables into the eeprom though non-standard means like __attribute((.section))__, @ or whatever it may be called for a given compiler, then they will be part of the linked executable. Some ICD programmers are smarter than others also and may allow you to just program a certain memory range.
In theory you could also track down the eeprom contents from the linker output (.hex, .s19 etc file) and delete it from there. Then it won't be programmed.
With Segger J-Link you can also fiddle around with this manually through the J-flash tool. I haven't used ST Link so no idea there. Other brands like PE Micro work though script and then you typically have to provide both the flash script and the eeprom script to it or both won't be programmed.
That being said, the normal use case is to always wipe and re-program the eeprom when you download a program. I've had some serious problems in the past years with a consultant who delivers a binary to me but without eeprom. And if I downloaded it without thinking into a board previously programmed, it will use the new program but the old eeprom settings. That has cost me weeks in trouble-shooting very strange bugs.
 

« first day (4914 days earlier)      last day (71 days later) »