Forum
Could not compile stylesheet for timeless. Using last compiled stylesheet.
Offline
Monday, January 26 2015, 04:56 PM
This is a formal record of an issue that Ananth is helping me out with: eMote 1.0.9 (CLR attached) becomes unresponsive when loaded onto a mote, and no programs can be deployed onto the eMote. I have reproduced this problem with two different .NOWs using the "Hello World" and "Radio Signal Meter" app notes.
Responses (6)
  • Accepted Answer

    Monday, January 26 2015, 04:57 PM - #Permalink
    I'm sorry, the CLR could not be attached since .axf was reported as an unsupported format.
    The reply is currently minimized Show
  • Accepted Answer

    Samraksh
    Monday, January 26 2015, 07:11 PM - #Permalink
    Dhrubo, I recommend you compress the .axf to a .zip, you should be able to attach that. If you can attach it I (or somebody) can test it out.

    You are saying that the CLR itself is unresponsive immediately after loading, not that it is unresponsive after programming an application, correct?

    Can you briefly outline your setup for loading? I notice that you tried to attach an AXF file, so you were presumably trying to load through GDB? While this is possible, typically we only support loading the CLR through MFDeploy. If you were trying to program the CLR through GDB in a naive way, it will not work, which is why I bring it up. So can you verify how you loaded?
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 26 2015, 07:23 PM - #Permalink
    Nathan, please find the .zip file in the attachment. You are right, the 1.0.9 CLR itself is unresponsive immediately after loading it (conversely, the 1.0.11_R12 version becomes unresponsive after a program using it is made to receive packets; I'll post this issue separately). I do not have the hex file for 1.0.9, so I used the following gdb commands after attaching an ARM-USB-TINY JTAG:

    cmd window# 1
    openocd-0.5.0.exe -f interface/olimex-jtag-tiny.cfg -f target/stm32xl.cfg


    cmd window# 2
    C:\CodeSourcery4.7.3\CodeSourcery\bin\arm-none-eabi-gdb.exe C:\eMote_1_0_9\tinyclr.axf
    target remote localhost:3333
    monitor reset halt
    monitor stm32f1x mass_erase 1
    load


    Thanks,
    Dhrubo.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 26 2015, 07:24 PM - #Permalink
    Nathan, please find the .zip file in the attachment. You are right, the 1.0.9 CLR itself is unresponsive immediately after loading it (conversely, the 1.0.11_R12 version becomes unresponsive after a program using it is made to receive packets; I'll post this issue separately). I do not have the hex file for 1.0.9, so I used the following gdb commands after attaching an ARM-USB-TINY JTAG:

    cmd window# 1
    openocd-0.5.0.exe -f interface/olimex-jtag-tiny.cfg -f target/stm32xl.cfg

    cmd window# 2
    C:\CodeSourcery4.7.3\CodeSourcery\bin\arm-none-eabi-gdb.exe C:\eMote_1_0_9\tinyclr.axf
    target remote localhost:3333
    monitor reset halt
    monitor stm32f1x mass_erase 1
    load

    Thanks,
    Dhrubo.
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Samraksh
    Monday, January 26 2015, 08:10 PM - #Permalink
    Thanks Dhrubo, that is exactly what I wanted to know.

    So the way you are trying to load with GDB cannot work. When you do the mass erase you are also erasing the bootloader (TinyBooter). Without the bootloader the CLR never gets started. So to get back to normal operation you'd need to load TinyBooter from GDB, then either load TinyCLR (without erasing, which doesn't always work) or preferably load TinyCLR from MFDeploy with the hex file.

    There is a GDB hack to get TinyCLR working without Tinybooter. From GDB, use the command "monitor reg pc 0x80201f8" then "continue". This is a hardware debugging command that allows you to skip directly to TinyCLR that you can use for testing.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 26 2015, 08:39 PM - #Permalink
    Thanks very much, Nathan.

    Regards,
    Dhrubo.
    The reply is currently minimized Show
Your Reply