Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Command line compiling issue
27-11-2013, 10:59 PM, (This post was last modified: 27-11-2013, 11:20 PM by niki_m.)
#1
Command line compiling issue
I'm using the IDE compiler from the command line & everything works perfectly for the P8 compiles, but on P32, compilation reports that 0 bytes have been used.

I checked the hex files & everything looks okay (I don't have a P32 to test with).

Can anyone check that the hex files are correct??? I just need to know if this is a reporting bug or something more serious...


The command I used to test was:

pinguino.py --generic220 -f examples/02.Digital/keypad32.pde

Quote:Board: GENERIC32MX220F032
Proc.: 32MX220F032B
File : examples/02.Digital/keypad32.pde
preprocessing ...
compiling ...
linking ...
compilation done
code size: 0 / 24575 bytes (0% used)
OK

Tested with rev 952 on Linux.
Reply
28-11-2013, 03:11 PM,
#2
RE: Command line compiling issue
Hi,
The compilation seems to be right but the code size calculation is wrong.
Addresses are relatives in boards.py (memstart and memend) and virtual in Hex file.
The virtual start address is defined in p32/lkr/your_board/procdefs.ld. For ex : _ebase_address = 0x9D003000 for a PIC32 Pinguino 220.
Solution ? : in boards.py, replace memstart and memend by memstart += _ebase_address value and memend += _ebase_address value
Something like that :
Code:
class GENERIC32MX220F032:
    name='GENERIC32MX220F032'
    arch=32
    bldr='microchip'
    proc='32MX220F032B'
    board='GENERIC32MX220F032'
    vendor=MICROCHIP_ID
    product=P32_ID
    ebase = 0x9D003000
    memstart=ebase + 0x00000
    memend=ebase + 0x08000
    shortarg='-n'
    longarg='--generic220'

I don't have time to solve that today. Sorry ...
It is easier to complain than it is to do, but it is better to do than it is to complain.
Reply
28-11-2013, 05:06 PM,
#3
RE: Command line compiling issue
Okay, thanks for letting me know Regis! If it could be fixed within the next few weeks, that would be great!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)