Chris

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • April 23, 2013 at 11:08 pm in reply to: Did I blow up my board? #4054
    Chris
    Member

    Spoke to Riley tonite. Looks like it was the Lock Bits being set incorrectly that was stopping anything being written, either thru avrdude and Studio. No idea how they got set because until last week I didnt have a programmer that could tweak them 🙂

    The fix was to erase the chip using my new mkii thru Studio. I check all the fuses were per the wiki instructions and set all the lock bits to NOLOCK (and wrote them.)

    I could then flash anything I wanted to the card, including xboot (although it wouldn’t verify, but seemed to flash ok and I got the boot blink). I tried tinyg.hex directly thru Studio w/o xboot. I verified the card booted correctly in the terminal. I then went back and reflashed xboot (no verify) and then tried an avrdude flash of tinyg.hex thru the USB port and it took first time. Again I verified everything thru the terminal.

    I’m very happy with the level of support from Synthetos. You guys are awesome and go way beyond to help.

    Cheers

    Chris

    April 23, 2013 at 2:44 pm in reply to: Did I blow up my board? #4053
    Chris
    Member

    BTW. those values I posted ARE the values read by Studio 6.

    April 23, 2013 at 1:43 pm in reply to: Did I blow up my board? #4050
    Chris
    Member

    What values should I set them to?

    April 22, 2013 at 6:18 pm in reply to: Did I blow up my board? #4045
    Chris
    Member

    I got my MKII week before last and still have problems, can’t flash a new bootloader nor the tinyg firmware. Either thru ATMEL Studio or the command line.

    Doing some digging and curious what everyone else is seeing for Lock Bits. Can people post their Lock Bits as reported from the Device Programmer in Studio (I’m using version 6).

    For the lockbits the following are set on my board. If I’m reading it right it’s locked from writing or verifying anything.

    BLBB = RLOCK

    Read lock – (E)LPM executing from the application section is not allowed to read from the boot loader section. If the interrupt vectors are placed in the application section, interrupts are disabled while executing from the boot loader section.

    BLBA = WLOCK 

    Write lock – SPM is not allowed to write the application section.

    BLBAT = WLOCK 

    Write lock – SPM is not allowed to write the application table

    LB =  RWLOCK

    Read and write lock – programming and read/verification of the flash and EEPROM are disabled for the programming interface. The lock bits and fuses are locked for read and write from the programming interface

    • This reply was modified 11 years, 6 months ago by Chris.
    April 1, 2013 at 8:29 pm in reply to: Did I blow up my board? #3976
    Chris
    Member

    I’ve hit the same problem. I tried searching but couldn’t find your link. Can you post it? Thanks.

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)