Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Hi! I'm trying to measure the temperature using a Pt100 probe. I used a LM317 to drive 218
  2. I'm sorry, I forgot to specify that it was working a few tries earlier, I flashed some code to it too. Then suddenly this started.
  3. Hello everybody! If I try to open $ mspdebug rf2500 on my Arch Linux desktop to connect to a MSP430G2553 mounted on a G2 Rev 1.5 Launchpad, I have this error, which takes a minute to show up: $ mspdebug rf2500 MSPDebug version 0.22 - debugging tool for MSP430 MCUs Copyright (C) 2009-2013 Daniel Beer <dlbeer@gmail.com> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Trying to open interface 1 on 023 rf2500: can't open device: Permission denied rf2500: failed to open RF2500 device
  4. Ah, makes sense. Another doubt, in the C programs, a SysCtlClockSet sets up the core frequency. What sets it up in this case, and what is the value?
  5. Sorry for opening this topic again, but had a little doubt: In your example code, the main program loop .Lloop has the mov instruction, so it would be executed repeatedly by the microprocessor. If we had a few more instructions there, say: ... .align 4 rst_handler: .Lloop: mov r1, #11 mov r2, #11 add r1, r2 sub r2, r1 b .Lloop ... All the instructions, including the arithmetic instructions, would be executed repeatedly, if I'm not wrong, and would make it CPU intensive. I also noticed that every time I halt it with telnet/gdb, it is executing a diff
  6. I tried to telnet into OpenOCD, turns out the port is 4444, and issued halt. The command to check registers was reg <register>: > reg r1 r1 (/32): 0x00000014 And it worked! Thanks for the heads up about telnet, I didn't know you could do that! Apparently it has LOTS of commands there, so I won't miss GDB. EDIT: Just tried it with GDB too, but with monitor reset before info registers and, as expected, r1 was set to 0x14. Thanks a lot! (gdb) info reg r1 r1 0x14 20
  7. Hi, just tried the code above, and still gdb shows all 0x0's. This is what I've been doing: arm-none-eabi-as -mcpu=cortex-m4 -mthumb -o add.o add.S arm-none-eabi-ld -s -o add.axf add.o arm-none-eabi-objcopy -O binary add.axf add.bin lm4flash add.bin I suspect its something stupid that I've been overlooking. Could you please point out? Thanks!
  8. Hey, thanks a bunch for the document, and now the ready code! Read up a bit but couldn't figure earlier, now its very clear. Thanks there and sorry for the delay.
  9. Hello, First post here! I'm trying my hand at ARM Assembly, so after reading up the basics for GNU toolkit, I came up with some simple code to set r1 to 20: .globl _start _start: MOV r1,#20 loop: b loop After compiling and linking it with arm-none-eabi-as and arm-none-eabi-ld respectively and converting it from axf to bin using arm-none-eabi-objcopy, I flashed it to the Launchpad using lm4flash. Then using OpenOCD, I connected gdb to the board and tried info registers to see if r1 was indeed set to 20, however the relevant line in the output was: r1
  • Create New...