• AVR Freaks

Hot!dsPIC33EV256GM106 EZBL No Response Error

Author
CRoss
New Member
  • Total Posts : 8
  • Reward points : 0
  • Joined: 2012/04/20 11:38:54
  • Location: 0
  • Status: offline
2019/09/16 06:33:55 (permalink)
0

dsPIC33EV256GM106 EZBL No Response Error

I have an interesting issue that just came up. I have been using EZBL on one of our projects successfully for a couple years and through many software revision changes. However, we released what we versioned V2 of our software and now the bootloader is responding with "EZBL communications error: no target response" after it attempts to program the target with the new software. 

The interesting part is that our V1 can bootload fine from any version start point. But when ever we attempt to bootload V2 from any version start point, the error is thrown. ie, V2 to V1 works, but V1 to V2 doesn't work. I run the java command line from a .bat I created and receive the same error that I see when building in MPLab v4.2. I have tried 3 different XC16 compilers, v1.25 v1.31 v1.40. 
 
I checked the bootloader files in both projects with WinMerge and the only difference is the project locations and the build count.
It was to my understanding that the bootloader is basically a standalone piece of software that will then program a portion of memory with the actual project, and that the main project configuration wouldn't have any affect on how the bootloader functioned.

I am not necessarily looking for solutions, but rather some direction as what to look at next. My C experience I would consider entry level so bare with me.
#1

4 Replies Related Threads

    du00000001
    Just Some Member
    • Total Posts : 3076
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: dsPIC33EV256GM106 EZBL No Response Error 2019/09/16 07:47:10 (permalink)
    0
    It's not very clear what you did resp. didn't, but from what I seem to understand, you have
    • 2 versions of the trrget part of EZBL   with
    • differing "project locations". WTF is "project locations" meant to describe ?
    CRoss
    I checked the bootloader files ...

    Sure? Or should I interpret that as "I checked the bootloadable application hex files ..." ?

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #2
    CRoss
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Joined: 2012/04/20 11:38:54
    • Location: 0
    • Status: offline
    Re: dsPIC33EV256GM106 EZBL No Response Error 2019/09/16 13:08:11 (permalink)
    0
    project location is the file location of the MPLab X project on the PC.
     
    Bootloader files is referring to all of the EZBL files associated with implementing the EZBL into our project. meaning all of the files and folder structures in the ezbl_uart folder.
    #3
    CRoss
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Joined: 2012/04/20 11:38:54
    • Location: 0
    • Status: offline
    Re: dsPIC33EV256GM106 EZBL No Response Error 2019/09/18 08:46:40 (permalink)
    0
    I have discovered when bootloading the version that works, the PC side of the bootloader sends the wakeup key and BL2B then more data I have not deciphered. after this the PIC responds appropriately and bootloading finishes. When attempting to bootload the version that does not work, the PC side sends over the wakeup key and BL2B then it sends ~ 0x87 then all 0x00. the PIC never responds. 
    #4
    du00000001
    Just Some Member
    • Total Posts : 3076
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: dsPIC33EV256GM106 EZBL No Response Error 2019/09/18 09:02:23 (permalink)
    0
    Could it be the PIC responds with some version number (code) when receiving the wakeup key, and the PC software is not up to respond to the code of the newer BL version ?

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #5
    Jump to:
    © 2019 APG vNext Commercial Version 4.5