• AVR Freaks

Hot!Ask for example testing.

Author
Post
Essentials Only Full Version
mian.qi
Starting Member
  • Total Posts : 60
  • Reward points : 0
  • Joined: 2020/02/16 19:52:58
  • Location: 0
  • Status: offline
2020/11/27 18:39:03 (permalink)
0

Ask for example testing.

I built this example(https://microchipdevelope...ld-comparison-example) on PIC18F57Q43 Curiosity Nano board, what I have altered are:
 
1. RA0 for POT.
2. UART for EUSART
3. RF0/RF1 for TX/RX.
 
but, I no data output either in CoolTerm or Data Visualizer.

All the problems not have been resolved are the same big.
#1

8 Replies Related Threads
    ric
    Super Member
    • Total Posts : 29435
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: online
    Re: Ask for example testing. 2020/11/27 19:29:00 (permalink)
    4 (1)
    So what is your question?
    You have not shown your altered code, so there's no way we can comment on what you did.
     

    I also post at: PicForum
    Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
    NEW USERS: Posting images, links and code - workaround for restrictions.
    To get a useful answer, always state which PIC you are using!
    #2
    dan1138
    Super Member
    • Total Posts : 4157
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: Ask for example testing. 2020/11/27 22:04:26 (permalink)
    0
    @ric,

    The Original Poster's(OP) problem is using a tutorial for the PIC16F18555 and wants to use the PIC18F57Q43.

    @mian.qi,

    I have worked through the tutorial and targeted the PIC18F57Q43. It seems to work in the MPLABX simulator, but I do not have a PIC18F57Q43 Curiosity Nano board to test it with.

    Give this code a try in your hardware, it may even work.
    post edited by dan1138 - 2020/11/27 22:06:15

    Attachment(s)

    18F57Q43_ADCC_MCC_v545.zip (86.04 KB) - downloaded 21 times
    #3
    mian.qi
    Starting Member
    • Total Posts : 60
    • Reward points : 0
    • Joined: 2020/02/16 19:52:58
    • Location: 0
    • Status: offline
    Re: Ask for example testing. 2020/11/27 22:42:22 (permalink)
    0
    The zip file is too big for attachment, so I couldn't attach it, my question is there was no output either in CoolTerm or Data Visualizer.
     
    When I tested the code, there was a device not recognized error.

    post edited by mian.qi - 2020/11/27 23:02:58

    Attached Image(s)


    All the problems not have been resolved are the same big.
    #4
    dan1138
    Super Member
    • Total Posts : 4157
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: Ask for example testing. 2020/11/28 01:04:22 (permalink)
    0
    mian.qi
    The zip file is too big for attachment, so I couldn't attach it, my question is there was no output either in CoolTerm or Data Visualizer.
     
    When I tested the code, there was a device not recognized error.

    The image you attached is too low resolution, it is unreadable.
     
    If the text in the MPLABX output window is ASCII then copy and paste that text in your post.
     
    DO NOT POST A SCREEN SHOT OF MPLABX COMPILER DIAGNOSTICS!
     
    #5
    mian.qi
    Starting Member
    • Total Posts : 60
    • Reward points : 0
    • Joined: 2020/02/16 19:52:58
    • Location: 0
    • Status: offline
    Re: Ask for example testing. 2020/11/28 02:20:40 (permalink)
    0
    make -f nbproject/Makefile-default.mk SUBPROJECTS= .build-conf
    make[1]: Entering directory 'C:/Users/MQ/Downloads/18F57Q43_ADCC_MCC_v545/18F57Q43_ADCC_MCC_v545.X'
    make -f nbproject/Makefile-default.mk dist/default/production/18F57Q43_ADCC_MCC_v545.X.production.hex
    make[2]: Entering directory 'C:/Users/MQ/Downloads/18F57Q43_ADCC_MCC_v545/18F57Q43_ADCC_MCC_v545.X'
    "C:\Program Files\Microchip\xc8\v2.31\bin\xc8-cc.exe" -mcpu=MCV20USB -c -fno-short-double -fno-short-float -memi=wordwrite -O0 -fasmfile -maddrqual=ignore -xassembler-with-cpp -mwarn=-2 -Wa,-a -DXPRJ_default=default -msummary=-psect,-class,+mem,-hex,-file -ginhx032 -Wl,--data-init -mno-keep-startup -mno-download -mdefault-config-bits -std=c99 -gdwarf-3 -mstack=compiled:auto:auto:auto -o build/default/production/mcc_generated_files/pin_manager.p1 mcc_generated_files/pin_manager.c 
    "C:\Program Files\Microchip\xc8\v2.31\bin\xc8-cc.exe" -mcpu=MCV20USB -c -fno-short-double -fno-short-float -memi=wordwrite -O0 -fasmfile -maddrqual=ignore -xassembler-with-cpp -mwarn=-2 -Wa,-a -DXPRJ_default=default -msummary=-psect,-class,+mem,-hex,-file -ginhx032 -Wl,--data-init -mno-keep-startup -mno-download -mdefault-config-bits -std=c99 -gdwarf-3 -mstack=compiled:auto:auto:auto -o build/default/production/mcc_generated_files/adcc.p1 mcc_generated_files/adcc.c 
    "C:\Program Files\Microchip\xc8\v2.31\bin\xc8-cc.exe" -mcpu=MCV20USB -c -fno-short-double -fno-short-float -memi=wordwrite -O0 -fasmfile -maddrqual=ignore -xassembler-with-cpp -mwarn=-2 -Wa,-a -DXPRJ_default=default -msummary=-psect,-class,+mem,-hex,-file -ginhx032 -Wl,--data-init -mno-keep-startup -mno-download -mdefault-config-bits -std=c99 -gdwarf-3 -mstack=compiled:auto:auto:auto -o build/default/production/mcc_generated_files/mcc.p1 mcc_generated_files/mcc.c 
    "C:\Program Files\Microchip\xc8\v2.31\bin\xc8-cc.exe" -mcpu=MCV20USB -c -fno-short-double -fno-short-float -memi=wordwrite -O0 -fasmfile -maddrqual=ignore -xassembler-with-cpp -mwarn=-2 -Wa,-a -DXPRJ_default=default -msummary=-psect,-class,+mem,-hex,-file -ginhx032 -Wl,--data-init -mno-keep-startup -mno-download -mdefault-config-bits -std=c99 -gdwarf-3 -mstack=compiled:auto:auto:auto -o build/default/production/mcc_generated_files/uart1.p1 mcc_generated_files/uart1.c 
    "C:\Program Files\Microchip\xc8\v2.31\bin\xc8-cc.exe" -mcpu=MCV20USB -c -fno-short-double -fno-short-float -memi=wordwrite -O0 -fasmfile -maddrqual=ignore -xassembler-with-cpp -mwarn=-2 -Wa,-a -DXPRJ_default=default -msummary=-psect,-class,+mem,-hex,-file -ginhx032 -Wl,--data-init -mno-keep-startup -mno-download -mdefault-config-bits -std=c99 -gdwarf-3 -mstack=compiled:auto:auto:auto -o build/default/production/mcc_generated_files/device_config.p1 mcc_generated_files/device_config.c 
    "C:\Program Files\Microchip\xc8\v2.31\bin\xc8-cc.exe" -mcpu=MCV20USB -c -fno-short-double -fno-short-float -memi=wordwrite -O0 -fasmfile -maddrqual=ignore -xassembler-with-cpp -mwarn=-2 -Wa,-a -DXPRJ_default=default -msummary=-psect,-class,+mem,-hex,-file -ginhx032 -Wl,--data-init -mno-keep-startup -mno-download -mdefault-config-bits -std=c99 -gdwarf-3 -mstack=compiled:auto:auto:auto -o build/default/production/mcc_generated_files/interrupt_manager.p1 mcc_generated_files/interrupt_manager.c 
    "C:\Program Files\Microchip\xc8\v2.31\bin\xc8-cc.exe" -mcpu=MCV20USB -c -fno-short-double -fno-short-float -memi=wordwrite -O0 -fasmfile -maddrqual=ignore -xassembler-with-cpp -mwarn=-2 -Wa,-a -DXPRJ_default=default -msummary=-psect,-class,+mem,-hex,-file -ginhx032 -Wl,--data-init -mno-keep-startup -mno-download -mdefault-config-bits -std=c99 -gdwarf-3 -mstack=compiled:auto:auto:auto -o build/default/production/main.p1 main.c 
    ::: error: (2043) target device was not recognized
    ::: error: (2043) target device was not recognized
    (908) exit status = 1
    (908) exit status = 1
    make[2]: *** [build/default/production/mcc_generated_files/pin_manager.p1] Error 1
    make[2]: *** Waiting for unfinished jobs....
    ::: error: (2043) target device was not recognized
    make[2]: *** [build/default/production/mcc_generated_files/adcc.p1] Error 1
    nbproject/Makefile-default.mk:171: recipe for target 'build/default/production/mcc_generated_files/pin_manager.p1' failed
    nbproject/Makefile-default.mk:163: recipe for target 'build/default/production/mcc_generated_files/adcc.p1' failed
    ::: error: (2043) target device was not recognized
    (908) exit status = 1
    ::: error: (2043) target device was not recognized
    ::: error: (2043) target device was not recognized
    make[2]: *** [build/default/production/mcc_generated_files/mcc.p1] Error 1
    (908) exit status = 1
    nbproject/Makefile-default.mk:179: recipe for target 'build/default/production/mcc_generated_files/mcc.p1' failed
    (908) exit status = 1
    (908) exit status = 1
    make[2]: *** [build/default/production/mcc_generated_files/uart1.p1] Error 1
    make[2]: *** [build/default/production/mcc_generated_files/device_config.p1] Error 1
    make[2]: *** [build/default/production/mcc_generated_files/interrupt_manager.p1] Error 1
    nbproject/Makefile-default.mk:155: recipe for target 'build/default/production/mcc_generated_files/uart1.p1' failed
    nbproject/Makefile-default.mk:187: recipe for target 'build/default/production/mcc_generated_files/device_config.p1' failed
    nbproject/Makefile-default.mk:195: recipe for target 'build/default/production/mcc_generated_files/interrupt_manager.p1' failed
    (908) exit status = 1
    nbproject/Makefile-default.mk:203: recipe for target 'build/default/production/main.p1' failed
    make[2]: Leaving directory 'C:/Users/MQ/Downloads/18F57Q43_ADCC_MCC_v545/18F57Q43_ADCC_MCC_v545.X'
    nbproject/Makefile-default.mk:91: recipe for target '.build-conf' failed
    make[1]: Leaving directory 'C:/Users/MQ/Downloads/18F57Q43_ADCC_MCC_v545/18F57Q43_ADCC_MCC_v545.X'
    nbproject/Makefile-impl.mk:39: recipe for target '.build-impl' failed
    ::: error: (2043) target device was not recognized
    make[2]: *** [build/default/production/main.p1] Error 1
    make[1]: *** [.build-conf] Error 2
    make: *** [.build-impl] Error 2

    BUILD FAILED (exit value 2, total time: 944ms)


    All the problems not have been resolved are the same big.
    #6
    ric
    Super Member
    • Total Posts : 29435
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: online
    Re: Ask for example testing. 2020/11/28 03:30:35 (permalink)
    5 (2)
    Always start with the first reported error, which was:
     
    ::: error: (2043) target device was not recognized


    Looking back, the target device is "MCV20USB"
    Shouldn't that be "PIC18F57Q43" ?
     

    I also post at: PicForum
    Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
    NEW USERS: Posting images, links and code - workaround for restrictions.
    To get a useful answer, always state which PIC you are using!
    #7
    mian.qi
    Starting Member
    • Total Posts : 60
    • Reward points : 0
    • Joined: 2020/02/16 19:52:58
    • Location: 0
    • Status: offline
    Re: Ask for example testing. 2020/11/28 03:31:09 (permalink)
    2 (1)
    It is Sunday tomorrow, I wish you two have rest, so you needn't answer my question before Monday.
    My question is: I tried the fourth example - ADCC Spike Detection in this Application Note "TB3263 - Getting Started With ADCC for PIC18", my files are attached as txt file. I thought I have fixed all the holes in it, and the files could be built and programed into PIC18F57Q43 Curiosity Nano board. But I the output in CoolTerm and Data Visualizer COM5(the serial and CDC port in my computer) were all empty.

    Attachment(s)

    ADCC_Spike_Detection.zip (25.65 KB) - downloaded 22 times

    All the problems not have been resolved are the same big.
    #8
    dan1138
    Super Member
    • Total Posts : 4157
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: Ask for example testing. 2020/11/28 11:40:11 (permalink)
    4.5 (2)
    mian.qi
    It is Sunday tomorrow, I wish you two have rest, so you needn't answer my question before Monday.
    My question is: I tried the fourth example - ADCC Spike Detection in this Application Note "TB3263 - Getting Started With ADCC for PIC18", my files are attached as txt file. I thought I have fixed all the holes in it, and the files could be built and programed into PIC18F57Q43 Curiosity Nano board. But I the output in CoolTerm and Data Visualizer COM5(the serial and CDC port in my computer) were all empty.

    Your problem is that you are still using examples for a controller that is different from the hardware you have.
     
    Perhaps you will need more experience before you can find and fix the small differences between the PIC18F47Q10 and the PIC18F57Q43.
     
    Based on the low resolution screen shot you attached to post#4 you seem to be using MPLABX v5.30.
     
    The PIC18F57Q43 may not be fully supported by MPLABX v5.30 so you may need to use a newer release.
    #9
    Jump to:
    © 2021 APG vNext Commercial Version 4.5