• AVR Freaks

Hot!Exception reading device database

Author
d.
Junior Member
  • Total Posts : 113
  • Reward points : 0
  • Joined: 2009/08/05 00:10:47
  • Location: 0
  • Status: offline
2018/09/28 11:41:42 (permalink)
0

Exception reading device database

Anyone know what this means?
 
I copied a working v4.05 project to a new folder, then opened the new project in v5.05.  The conversion took place.  Doing a clean build in v5.05 I get:
 
Exception reading device database: null
com.microchip.crownking.Anomaly
at com.microchip.crownking.edc.PIC.<init>(PIC.java:138)
at com.microchip.crownking.edc.PICFactory.create(PICFactory.java:152)
at com.microchip.crownking.edc.PICFactory.get(PICFactory.java:126)
at com.microchip.crownking.edc.PICFactory.get(PICFactory.java:138)
at com.microchip.apps.ezbl.CommandAndBuildState.ReadArgs(CommandAndBuildState.java:558)
at com.microchip.apps.ezbl.MakeEditor.main(MakeEditor.java:86)
at com.microchip.apps.ezbl.Main.main(Main.java:113)
 
It then compiles all the files, and repeats the errors above.
 
Ideas?
 
Thanks,
 
Dave
#1

3 Replies Related Threads

    GeorgePauley
    Moderator
    • Total Posts : 1145
    • Reward points : 0
    • Joined: 2009/12/01 13:59:30
    • Location: Chandler AZ
    • Status: offline
    Re: Exception reading device database 2018/10/01 10:43:50 (permalink)
    +1 (1)
    MPLAB X had an issue attempting to read the device data file.  What device are you using?
    #2
    d.
    Junior Member
    • Total Posts : 113
    • Reward points : 0
    • Joined: 2009/08/05 00:10:47
    • Location: 0
    • Status: offline
    Re: Exception reading device database 2018/10/01 10:59:06 (permalink)
    0
    Hi George,
     
    Thanks for the reply.  First in response to your question, I've copied the project from one folder to another, changing the folder name (X project name).  I've done this before and never had a problem.  The correct device goes along with the project (PIC24FJ1024GB610).
     
    But I did find that the error is generated from within the makefile.  This is a (as yet unmodified) EZBL bootloader project and the error is in makefile.uart.mk.  This .mk file is automatically generated, but I haven't found from where.  I can delete it, and it is re-created but compiles with the same error:
     
    EZBL: Editing MakeFile-uart.mk to enable EZBL Bootloader generation
    "C:\Program Files (x86)\Microchip\MPLABX\v5.05\sys\java\jre1.8.0_144/bin/"java -jar "ezbl_integration/ezbl_tools.jar" --make_editor -conf=uart -min_free_psv=-1 -warn_free_psv=8192 -mcpu=24FJ1024GB610 -linkscript=,--script="ezbl_integration\ezbl_build_standalone.gld" -compiler_folder="C:\Program Files (x86)\Microchip\xc16\v1.34\bin" -java="C:\Program Files (x86)\Microchip\MPLABX\v5.05\sys\java\jre1.8.0_144/bin/" -project_name="Strip14Boot" -path_to_ide_bin="C:/Program Files (x86)/Microchip/MPLABX/v5.05/mplab_platform/platform/../mplab_ide/modules/../../bin/" -artifact="dist/uart/production/Strip14Boot.production.hex"
    Exception reading device database: null
    com.microchip.crownking.Anomaly
    at com.microchip.crownking.edc.PIC.<init>(PIC.java:138)
    at com.microchip.crownking.edc.PICFactory.create(PICFactory.java:152)
    at com.microchip.crownking.edc.PICFactory.get(PICFactory.java:126)
    at com.microchip.crownking.edc.PICFactory.get(PICFactory.java:138)
    at com.microchip.apps.ezbl.CommandAndBuildState.ReadArgs(CommandAndBuildState.java:558)
    at com.microchip.apps.ezbl.MakeEditor.main(MakeEditor.java:86)
    at com.microchip.apps.ezbl.Main.main(Main.java:113)
     
    So it doesn't appear to be an MPLAB-X issue.  Maybe I should create an EZBL ticket?
     
    Thanks for the reply.
     
    Dave
    #3
    d.
    Junior Member
    • Total Posts : 113
    • Reward points : 0
    • Joined: 2009/08/05 00:10:47
    • Location: 0
    • Status: offline
    Re: Exception reading device database 2018/10/03 15:46:21 (permalink)
    0
    I talked with Microchip support on a related issue and mentioned this problem.  They are aware there is a problem with EZBL with MPLAB-X v5.05, but don't know exactly what the problem is yet.  I'll assume that they understand the issue and will come up with a solution.
     
    In the meantime, I've verified that there is no problem with a v4.05 project, and converting that to a v5.05 project creates the problem.  I can work in v4.05 for the short term, but I will need to move on to v5.05 before implementing EZBL on my project.
     
    Dave
    #4
    Jump to:
    © 2019 APG vNext Commercial Version 4.5