On Wed, 01 May 2013 20:55:35 +0100
"Adam D. Barratt" <a...@adam-barratt.org.uk> wrote:
> On Tue, 2013-04-30 at 19:23 +0200, Attila Kinali wrote:
> > The current interrupt table code definitions in the gcc-msp430 and
> > msp430mcu
> > packages will lead to generate tables that go far into a reserved region
> > of the MSP430 devices in case of the MSP430FR5xxx devices.
> > Apperantly this region contains the passwords and lock code for device.
> > Ie once this region is written to and the device reset, access over
> > JTAG becomes impossible.
>
> Unfortunately I think it's now too late to fix this before the release.
Yeah. I felt bad about opening a critical bug this short before the
release. But breaking devices is something that shouldnt happen.
> I'd be happy to accept the patch in a point release, but would
> appreciate some input from the maintainer here - should we ship the
> package as-is and fix the problem in the first point release, or remove
> the package (and msp430-libc) from wheezy? The removal would not be a
> regression, as neither package is in squeeze.
I would not remove the packages from wheezy, that would be unwarranted.
Maybe an intermediate solution would be to change the description of
the packages to contain a warning for the FRAM based devices. And then
fix it in the point realease in 2 or 3 months.
Attila Kinali
--
The people on 4chan are like brilliant psychologists
who also happen to be insane and gross.
-- unknown
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
