Forums

Hi Alexander,

This sort of issue is usually due to something in the user code that interfers with subsequent programming operations.  Examples include incorrect clock settings, selecting a clock source that does not exist, and reconfiguring GPIO that are required for the JTAG interface.  Please review your code for any of these conditions.

Can you program and re-program the blinky binary (unmodified) that comes with StellarisWare?

Please report the error message provided by the programming tools.  That might provide additional clues.

Hi Jonathan,

Let me add more information about issue.

The JTAG pins connected to JTAG pins only (directly to MCU)!

Yes, I've been tried "blinky" (pre-built by keil). The same bad result.

Best regards,

Alexander

A couple of questions:

When the programming is successful (the first time), does the application run correctly and are you able to see the LED flashing?

Does the application still run correctly after you attempt to re-program your target board?

Hi Jonathan,

I've done some experiments. Summarize:

1. The "blinky" working correctly (sorry for wrong message in previous post, I missed pin when I checked blinks by scope)
2. All other examples are failed.
3. If I add SysCtlClockSet(SYSCTL_SYSDIV_2_5 | SYSCTL_USE_PLL | SYSCTL_OSC_MAIN |  SYSCTL_XTAL_16MHZ); or other combination for SysCtlClockSet( ... ) I will receive the error: no re-write and application doesn't work.

So, I've troubles with PLL initialization. I'll try to check (solid another one) crystal and post result.

Best regards,
Alexander

Hi Jonathan,

Here is the update fore previous post.

I solid another one crystal (but 8Mhz instead of 16MHz) and it works! I try to solid another 16MHz when I'll find it.

However I've a few questions relates this topic.

1. Why broken crystal can block firmware update and "hardware reset" via JTAG? 
2. Why OpenOCD can not verify the firmware (you could find script below)? 

#----

source [find interface/luminary.cfg]
set WORKAREASIZE 0x4000
set CHIPNAME lm3s9b9x
source [find target/stellaris.cfg]

proc program_device () {
    # halt the processor
    halt
    #wait_halt
    # write file to flash memory
    cortex_m3 maskisr on
    flash write_image erase "./gcc/pnp_eth_can.bin" 0
    verify_image "./gcc/pnp_eth_can.bin"
    cortex_m3 maskisr off
    sleep 10
    #start execution of the program just downladed
    reset run
    sleep 10
    #exit OpenOCD
    shutdown
}
init
reset init
program_device ()

#----

The errors look like:

Error: checksum mismatch - attempting binary compare
diff 0 address 0x00000001. Was 0x08 instead of 0x01
diff 1 address 0x00000004. Was 0x4d instead of 0xe1
.....

Could you please help me how to modify script to verify image?

Best regards,
Alexander

Hi Alexander,

Alexander Chuikov

• Why broken crystal can block firmware update and "hardware reset" via JTAG? 

When your code runs, it's selecting and configuring the clock circuit.  If the clock is broken (a static level, or very wrong frequency) the MCU will not function until a power on reset.  The user code runs quickly before the programming tool can intercept the clock configuration. 

I'm not familiar with OpenOCD, but I will ask others here about your script question.

Hi Jonathan,

Thank you for detailed explanation. I'll wait instructions for OpenOCD.

Best regards,
Alexander

Hi Jonathan,

Thank you very much!

Best regards,
Alexander