Hi,
After playing around with the eval kit SAM4L-EK and trying it out with the Atmel Studio 6.1, we decided to go ahead and make a board using a SAM4LS4B.
I just got the board the other day and a couple of the Segger ATMEL SAM-ICE . I managed to hook up the debugger to the JTAG IF and I am able to connect to the board, doing flash erase, programming and flash readback without any problems.
Next I wanted to try and create some code and test out the debugger. That's where I am stuck now. The debugger seem to ignore all break points I set up before hitting go.
I checked the beginning of the content of the flash. The first value should be the stackpointer, that is located in RAM, good enough. The 2nd 32bit value is the reset vector, it points to address 0x271, so it should jump to address 0x270 in Thumb mode, where I can see the startup code is located.
All looks good, but I set a break point there, but it doesn't work. I find the processor doing a loop in some code in RAM? To get there though it should have passed the first breakpoint I set.
When I connected the SAM-ICE and started up Atmel studios, it updated the box. I then installed Segger tools, which again updated the box. I am pretty sure I have the newest and greatest available.
Anyone else experienced problems with this? Some obvious thing I am not doing? Do I configure the Segger SAM-ICE outside Atmel Studios? When the Segger flashes the SAM4LS, does transfers a flash algorithm to the processor's RAM? Is this the one it is stuck in?
I have been playing around with the SAM4L on the eval board too (SWD mode), and tried hooking it up to my SAM-ICE through the DEBUG pads on the underside and adding a jumper to a connector that selected the onboard JLINK or external interface. I measured all the SAM-ICE's input pins using the JLINK commander that can flick the pins, it looks like it is connected correctly. But the device programmer in Atmel studio still complains that the TDO is high all the time.
I am almost out of options at this point, not sure what to try next
I have to SAM-ICE, one with old firmware, and one with the latest and greatest.
Anyone with a bright idea or a simple explanation?
Danny
After playing around with the eval kit SAM4L-EK and trying it out with the Atmel Studio 6.1, we decided to go ahead and make a board using a SAM4LS4B.
I just got the board the other day and a couple of the Segger ATMEL SAM-ICE . I managed to hook up the debugger to the JTAG IF and I am able to connect to the board, doing flash erase, programming and flash readback without any problems.
Next I wanted to try and create some code and test out the debugger. That's where I am stuck now. The debugger seem to ignore all break points I set up before hitting go.
I checked the beginning of the content of the flash. The first value should be the stackpointer, that is located in RAM, good enough. The 2nd 32bit value is the reset vector, it points to address 0x271, so it should jump to address 0x270 in Thumb mode, where I can see the startup code is located.
All looks good, but I set a break point there, but it doesn't work. I find the processor doing a loop in some code in RAM? To get there though it should have passed the first breakpoint I set.
When I connected the SAM-ICE and started up Atmel studios, it updated the box. I then installed Segger tools, which again updated the box. I am pretty sure I have the newest and greatest available.
Anyone else experienced problems with this? Some obvious thing I am not doing? Do I configure the Segger SAM-ICE outside Atmel Studios? When the Segger flashes the SAM4LS, does transfers a flash algorithm to the processor's RAM? Is this the one it is stuck in?
I have been playing around with the SAM4L on the eval board too (SWD mode), and tried hooking it up to my SAM-ICE through the DEBUG pads on the underside and adding a jumper to a connector that selected the onboard JLINK or external interface. I measured all the SAM-ICE's input pins using the JLINK commander that can flick the pins, it looks like it is connected correctly. But the device programmer in Atmel studio still complains that the TDO is high all the time.
I am almost out of options at this point, not sure what to try next
I have to SAM-ICE, one with old firmware, and one with the latest and greatest.
Anyone with a bright idea or a simple explanation?
Danny