Hello!
I am trying my first steps with mps430-gcc on a development board with
some peripherals and a 5438a MCU.

So far I was pretty successful bringing up the device, initializing
clocks, UART, toggle some LEDs, nice. Since I am planning to use the
BTStack Bluetooth stack later on I am using the large memory model
already (-mmemory-model=large). I am using
        msp430-gcc (GCC) 4.7.0 20120322 (mspgcc dev 20120716)

Then I extended my testcode with some SPI init code, a ~1kbyte buffer in
RAM and a polling SPI write of that buffer to the SPI - BANG!

After programming that program using a FET the program did not run as
expected (it hung pretty soon after startup for some reason) and after
that I get on startup the following error from mspdebug using tilib:

MSP430_Initialize: /dev/ttyACM3
Firmware version is 30203015
MSP430_VCC: 1800 mV
MSP430_OpenDevice
tilib: MSP430_OpenDevice: Security Fuse has been blown (error = 30)
tilib: device initialization failed

So I now can not get any access to the CPU anymore.

Since this eval board is very valuable for me and I will most likely not
get another one I am almost in panic!
Did I brick my board!?
Is there any way to recover from this situation? Please tell me yes!

Oh man, this is bad...

Any hint would be really very welcome!
Thanks in advance!

Cheers
  nils

-- 
kernel concepts GmbH      Tel: +49-271-771091-12
Sieghuetter Hauptweg 48
D-57072 Siegen            Mob: +49-176-21024535
http://www.kernelconcepts.de

------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Reply via email to