Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
PIC24FJ64GA104 Issue
#6
(2015-12-22, 11:07:01)cinpezzo Wrote:
(2015-12-21, 22:46:24)Mikael Gustavsson Wrote: Try setting fcy to 4000000. From the datasheet:
Quote:The processor clock source is divided by two to produce the internal instruction cycle clock, FCY.

Now it communicate perfectly!! Thanks!!

Now I have an other problem related to "bl protection tripped"
Using the GUI in debug mode it shows the following print:

     Searching for bl . . . .
     Found PIC24FJ64GA104 fw ver. 4.0.3
     Boot loader placement/size: 2/1
     Waiting for the boot loader to be ready...ok
     Hex file successfully parsed in 0ms
     Writing flash....
           Erasing page 0 @ 0x0000...ok
           Writing row 0 @ 0x0000...ok
           Writing row 1 @ 0x0080...ok
           Writing row 2 @ 0x0100...ok
           [.........]
           Writing row 327 @ 0xA380...ok
           Erasing page 41 @ 0xA400...ok
           Writing row 328 @ 0xA400...bl protection tripped
           Write flash failed
     Closing port
     Tx 63,9kB / Rx 375 bytes / 39s
     Write failed

Loading the fw it shows the following print:

     Parsing hexfile...
     File timestamp: 13/12/2015 11:14:39 AM
     Opening hexfile...ok
     Validating hexfile...ok
     Application vector address: 0xA3FC
     Application address: 0x200
     Last row containing configs was found in hex file, last page has been disabled. Consult the main manual for more information.
     Main flash page 0 is used, 0x00 - 0x3FF
     Main flash row 0 is used, 0x00 - 0x7F
     Main flash row 1 is used, 0x80 - 0xFF
     Main flash row 2 is used, 0x100 - 0x17F
      [.........]
     Main flash row 342 is used, 0xAB00 - 0xAB7F
     Main flash row 343 is used, 0xAB80 - 0xABFF
     Bootloader is located in the main flash
     Bootloader start address: 0xA400
     Bootloader end address: 0xA7FF
     Bootloader start page: 41
     Bootloader end page: 41
     Bootloader start row: 328
     Bootloader end row: 335
     Hex file successfully parsed in 56ms


I'm using the following fuses on the pic:

config __CONFIG4, DSWDTPS_DSWDTPSF & DSWDTOSC_LPRC & DSBOREN_ON & RTCOSC_LPRC & DSWDTEN_ON
config __CONFIG3, WPDIS_WPDIS & WPFP_WPFP41 & WUTSEL_LEG & WPEND_WPENDMEM & WPCFG_WPCFGDIS & SOSCSEL_IO
config __CONFIG2, IESO_OFF & IOL1WAY_OFF & FNOSC_PRIPLL & I2C1SEL_PRI & POSCMOD_XT & OSCIOFNC_ON & FCKSM_CSDCMD
config __CONFIG1, WDTPS_PS32768 & ICS_PGx3 & FWPSA_PR128 & WINDIS_OFF & GWRP_OFF & GCP_OFF & FWDTEN_OFF & JTAGEN_ON


What could be the cause of this issue???

Thanks!!!


I understood the problem...I was trying with an hex file uploaded from pic via PicKit3 so its size match the size of the pic memory and it overwrites the bootloader memory area; so this caused the "bl protection tripped" error. Using a compiled hex file with smaller size the bootloader works perfectly.
Thanks for your great support!!

Nicola
Reply


Messages In This Thread
PIC24FJ64GA104 Issue - by cinpezzo - 2015-12-13, 23:07:06
RE: PIC24FJ64GA104 Issue - by Mikael Gustavsson - 2015-12-18, 20:51:06
RE: PIC24FJ64GA104 Issue - by cinpezzo - 2015-12-19, 14:16:19
RE: PIC24FJ64GA104 Issue - by Mikael Gustavsson - 2015-12-21, 22:46:24
RE: PIC24FJ64GA104 Issue - by cinpezzo - 2015-12-22, 11:07:01
RE: PIC24FJ64GA104 Issue - by cinpezzo - 2015-12-22, 16:55:35
RE: PIC24FJ64GA104 Issue - by Mikael Gustavsson - 2015-12-23, 17:16:33

Forum Jump:


Users browsing this thread: 1 Guest(s)