Dear Ytai and all,
Apologies for the long post. But I have marked my questions in* GREEN* and
errors are in *RED*
We had re-setup our whole environment and tried with fresh code.
It’s now: Linux Mint 64-bit with MPLAB X v3.51 with* xc16 compiler
v1.30(not the C30 compiler (V3.30c) --> is this okay?)*.
- The commands make-all don't work as I get a “command not found
error”-->probably incorrect environment. *But is this step still
required if we are using MPLAB to build code?*
>
>
>
>
>
>
> *Error:
> ===========================================libusb===========================================./make-all:
>
> line 17: prjMakefilesGenerator.sh: command not foundWARNING: failed to
> regenerate Makefiles.make: *** firmware/libusb: No such file or directory.
> Stop.FAILURE*
- Alternatively we traced the file prjMakefilesGenerator.sh and manually
ran the command for the module as:
> - /opt/microchip/mplabx/v3.51/mplab_ide/bin/prjMakefilesGenerator.sh
> ../firmware/libusb
>
- Output :
>
> - ERROR: Has EDS, but no <edc:ExtendedDataSpace>
>
- Still we used MPLab to build the modules with the following
settings:
- For building the Bootloader
- libadb device selected: PIC24FJ256GB206.-->build success
- -libbstack device selected: PIC24FJ256GB206.-->build success
- -libconn device selected: PIC24FJ256GB206.-->build success
- -libusb device selected: PIC24FJ256GB206_OTG.-->build success
- -Bootloader : SPRK0020.-->*build NOT successful*
- For building the App_layer_v1
- -libadb device selected: PIC24FJ256GB206.-->build success
- -libbstack device selected: PIC24FJ256GB206.-->build success
- -libconn device selected: PIC24FJ256GB206.-->build success
- -libusb device selected: PIC24FJ256GB206_OTG_ADB.-->build success
- -App_layer_v1 : IOIO0030.-->*build NOT successful*
- For App_layer_v1: Errors marked in RED, same error was seen for
building the boot-loader.
CLEAN SUCCESSFUL (total time: 54ms)
> make -f nbproject/Makefile-IOIO0030.mk SUBPROJECTS= .build-conf
> make[1]: Entering directory
> '/home/user/Desktop/park_git/ioio/firmware/app_layer_v1'
> make -f nbproject/Makefile-IOIO0030.mk
> dist/IOIO0030/production/app_layer_v1.production.hex
> make[2]: Entering directory
> '/home/user/Desktop/park_git/ioio/firmware/app_layer_v1'
> "/opt/microchip/xc16/v1.30/bin/xc16-gcc" digital.c -o
> build/IOIO0030/production/digital.o -c -mcpu=24FJ256GB206 -MMD -MF
> "build/IOIO0030/production/digital.o.d" -mno-eds-warn -g -omf=elf
> -DXPRJ_IOIO0030=IOIO0030 -no-legacy-libc -fno-short-double -O3 -I"."
> -I".." -I"../microchip/include" -I"../common" -DPLATFORM=1030 -DNDEBUG
> -msmart-io=1 -Wall -msfr-warn=off -std=gnu99
> "/opt/microchip/xc16/v1.30/bin/xc16-gcc" ../common/logging.c -o
> build/IOIO0030/production/_ext/1270477542/logging.o -c -mcpu=24FJ256GB206
> -MMD -MF "build/IOIO0030/production/_ext/1270477542/logging.o.d"
> -mno-eds-warn -g -omf=elf -DXPRJ_IOIO0030=IOIO0030 -no-legacy-libc
> -fno-short-double -O3 -I"." -I".." -I"../microchip/include" -I"../common"
> -DPLATFORM=1030 -DNDEBUG -msmart-io=1 -Wall -msfr-warn=off -std=gnu99
> "/opt/microchip/xc16/v1.30/bin/xc16-gcc" ../common/byte_queue.c -o
> build/IOIO0030/production/_ext/1270477542/byte_queue.o -c
> -mcpu=24FJ256GB206 -MMD -MF
> "build/IOIO0030/production/_ext/1270477542/byte_queue.o.d"
> -mno-eds-warn -g -omf=elf -DXPRJ_IOIO0030=IOIO0030 -no-legacy-libc
> -fno-short-double -O3 -I"." -I".." -I"../microchip/include" -I"../common"
> -DPLATFORM=1030 -DNDEBUG -msmart-io=1 -Wall -msfr-warn=off -std=gnu99
> "/opt/microchip/xc16/v1.30/bin/xc16-gcc" features.c -o
> build/IOIO0030/production/features.o -c -mcpu=24FJ256GB206 -MMD -MF
> "build/IOIO0030/production/features.o.d" -mno-eds-warn -g -omf=elf
> -DXPRJ_IOIO0030=IOIO0030 -no-legacy-libc -fno-short-double -O3 -I"."
> -I".." -I"../microchip/include" -I"../common" -DPLATFORM=1030 -DNDEBUG
> -msmart-io=1 -Wall -msfr-warn=off -std=gnu99
> "/opt/microchip/xc16/v1.30/bin/xc16-gcc" i2c.c -o
> build/IOIO0030/production/i2c.o -c -mcpu=24FJ256GB206 -MMD -MF
> "build/IOIO0030/production/i2c.o.d" -mno-eds-warn -g -omf=elf
> -DXPRJ_IOIO0030=IOIO0030 -no-legacy-libc -fno-short-double -O3 -I"."
> -I".." -I"../microchip/include" -I"../common" -DPLATFORM=1030 -DNDEBUG
> -msmart-io=1 -Wall -msfr-warn=off -std=gnu99
> "/opt/microchip/xc16/v1.30/bin/xc16-gcc" icsp.c -o
> build/IOIO0030/production/icsp.o -c -mcpu=24FJ256GB206 -MMD -MF
> "build/IOIO0030/production/icsp.o.d" -mno-eds-warn -g -omf=elf
> -DXPRJ_IOIO0030=IOIO0030 -no-legacy-libc -fno-short-double -O3 -I"."
> -I".." -I"../microchip/include" -I"../common" -DPLATFORM=1030 -DNDEBUG
> -msmart-io=1 -Wall -msfr-warn=off -std=gnu99
> "/opt/microchip/xc16/v1.30/bin/xc16-gcc" ../microchip/common/uart2.c -o
> build/IOIO0030/production/_ext/1537399865/uart2.o -c -mcpu=24FJ256GB206
> -MMD -MF "build/IOIO0030/production/_ext/1537399865/uart2.o.d"
> -mno-eds-warn -g -omf=elf -DXPRJ_IOIO0030=IOIO0030 -no-legacy-libc
> -fno-short-double -O3 -I"." -I".." -I"../microchip/include" -I"../common"
> -DPLATFORM=1030 -DNDEBUG -msmart-io=1 -Wall -msfr-warn=off -std=gnu99
> "/opt/microchip/xc16/v1.30/bin/xc16-gcc" adc.c -o
> build/IOIO0030/production/adc.o -c -mcpu=24FJ256GB206 -MMD -MF
> "build/IOIO0030/production/adc.o.d" -mno-eds-warn -g -omf=elf
> -DXPRJ_IOIO0030=IOIO0030 -no-legacy-libc -fno-short-double -O3 -I"."
> -I".." -I"../microchip/include" -I"../common" -DPLATFORM=1030 -DNDEBUG
> -msmart-io=1 -Wall -msfr-warn=off -std=gnu99
>
> *../common/logging.c:33:17: fatal error: PPS.h: No such file or
> directorycompilation terminated.*
> make[2]: *** [build/IOIO0030/production/_ext/1270477542/logging.o] Error
> 255
> make[2]: *** Waiting for unfinished jobs....
> nbproject/Makefile-IOIO0030.mk:219: recipe for target
> 'build/IOIO0030/production/_ext/1270477542/logging.o' failed
> ../common/byte_queue.c: In function 'ByteQueuePullToBuffer':
> ../common/byte_queue.c:65:23: warning: 'data2' may be used uninitialized
> in this function
> adc.c: In function '_CRCInterrupt':
> adc.c:181:7: warning: 'group_header_pos' may be used uninitialized in this
> function
> make[2]: Leaving directory
> '/home/user/Desktop/park_git/ioio/firmware/app_layer_v1'
> nbproject/Makefile-IOIO0030.mk:84: recipe for target '.build-conf' failed
> make[1]: Leaving directory
> '/home/user/Desktop/park_git/ioio/firmware/app_layer_v1'
> nbproject/Makefile-impl.mk:39: recipe for target '.build-impl' failed
> make[1]: *** [.build-conf] Error 2
> make: *** [.build-impl] Error 2
> BUILD FAILED (exit value 2, total time: 1s)
>
*I found out that the PPS.h file is in peripheral library. I downloaded
peripheral library for PPS.h header file but compiler still gives the same
error. So is my environment incorrect ? or i have not installed “peripheral
library” correctly? Os its it some other error? Any pointers will be
helpful.*
- As an long-shot we commented the include directive for PPS.h and tried
to build the code to get the following error:
/opt/microchip/xc16/v1.30/bin/bin/../bin/elf-ld: Warning: linker script did
> not specify CRT_STARTMODE file, default: crt_start_mode_normal
*dummy.gld.01:1203: undefined symbol `__reset' referenced in expression*
make[2]: *** [dist/IOIO0030/production/app_layer_v1.production.hex] Error
> 255
make[1]: *** [.build-conf] Error 2
make: *** [.build-impl] Error 2
nbproject/Makefile-IOIO0030.mk:395: recipe for target
> 'dist/IOIO0030/production/app_layer_v1.production.hex' failed
make[2]: Leaving directory
> '/home/user/Desktop/park_git/ioio/firmware/app_layer_v1'
nbproject/Makefile-IOIO0030.mk:84: recipe for target '.build-conf' failed
make[1]: Leaving directory
> '/home/user/Desktop/park_git/ioio/firmware/app_layer_v1'
nbproject/Makefile-impl.mk:39: recipe for target '.build-impl' failed
Any pointers are welcome. Thanks for patience. Will commit back firmware
building steps if they have changed to the repo if we are successfully.
On Sunday, January 22, 2017 at 10:53:49 AM UTC+5:30, Ytai wrote:
>
> This is not an inductor but a ferrite bead.
> Please build with XC16 using a clean clone. I don't want to waste time
> troubleshooting a non-standard environment.
>
> On Sat, Jan 21, 2017 at 6:03 AM, <[email protected] <javascript:>> wrote:
>
>> I'm asking this question because I'm in doubt that is this really a
>> Inductor ?
>> if yes then can you please explain me why are you using this because in
>> controller's datasheet there is no explanation of Indutor use.
>> and what's the exact value (given value in schematic is 300hm, 1.8A)
>>
>> On Saturday, January 21, 2017 at 4:46:59 PM UTC+5:30, [email protected]
>> wrote:
>>>
>>> hello ytai,
>>>
>>> can you tell me exact value of Inductor, connected with controller's
>>> avdd pin(19).
>>>
>>> thanks
>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "ioio-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected]
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/ioio-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"ioio-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/ioio-users.
For more options, visit https://groups.google.com/d/optout.
