You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While reviewing fileio.c I could not help noticing that memory offsets of some parts are not dealt with correctly and can cause segmentation faults when writing Intel Hex or Motorola S-Record files:
BTW, avrdude does not support AVR32 well in reality, since only one chip is supported.
Previously Joerg mentioned that we do not want to spend time on avr32 as the family is not popular and kind of obsoleted. So I closed the old enhancement feature requests (without PR) for avr32.
But of course we should fix the issue of this particular avr32 chip supported (I can not test since I do not have board with this chip). And in case people raise PR and with good test results, we may incorporate the PR.
There are actually two closed issue with patches for AVR32.
While reviewing
fileio.c
I could not help noticing that memory offsets of some parts are not dealt with correctly and can cause segmentation faults when writing Intel Hex or Motorola S-Record files:The text was updated successfully, but these errors were encountered: