FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support


New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Author Topic: Vinculum ii IDE asm and linker errors, need listing or map file outputs?  (Read 640 times)

xenon68

  • Newbie
  • *
  • Posts: 7
    • View Profile

I was getting error:
Assembler: Debug\cnc.asm line 5666: (error) A3015 value is greater than the operand size

in the assembler, but no way to actually determine where/what the error was.  There is no switch to enable a listing output from the assembler.  Reducing the amount of RAM used appears to have fixed there error, but I have no idea what amount of memory is being used by my code and the vnc2 libraries...

Is there a way to get the compiler/assembler/linker to output listings, or map information?  I don't see any switches to do that. There is a map that is produced, but it tells you nothing but what the chips capacity is...

After shrinking my RAM use to nothing, no I get this error:
(Debug\vnc2.obj) : (error) L0013 error in parameter section information

But no other output file to help diagnosis what this means...


Logged

FTDI Community

  • Administrator
  • Hero Member
  • *****
  • Posts: 800
    • View Profile

Hello,

All information on the VNC2 tools can be found in AN_151 Vinculum II User Guide:

https://ftdichip.com/wp-content/uploads/2020/08/AN_151_Vinculum-II_User_Guide.pdf

The asm error is a value of >255 being loaded into an 8 bit register.
The ASM file can have line numbers from the original C code inline.
Please check the command line options for VinC.exe:

Code: [Select]
VinC.exe
VinC [options] [file ...] [-L linker options]

  -E            Run the pre-processor and stop.
  -S            Stop processing after pre-processing and compilation.
  -c            Pre-process, compile and assemble but do not invoke linker.
  -O level      Specify optimisation for compiler.
  -d level      Specify debug output level for compiler.
  -D macro=defn Defines macro with optional defn in preprocessor.
  -U macro      Undefines macro in preprocessor.
  -I dir        Add a search directory for include files.
  -o file       Specify output filename.
  -l file       Specify log filename.
  --save-temps  Save all temporary files.
  --save-temp   Save temporary files: 'a' assembler, 'i' preprocessor,
                'o' object.
  --combine     Combine source files on command line into single input file
                for compiling.
  --library     Create a single output file for all source files on command
                line.
  -v            Verbose output of command lines for tools.
  -q            Quieten output of command lines for tools.
  --version     Display tool version.
  --all-versions        Display all tool versions.
  --max-warn limit      Limit the number of warnings displayed.
  --max-err limit       Limit the number of errors displayed.
  --help        Display this help message.
  -L            Process all following options as linker options.

The bin file can be up to 256 kB - 4 kB.

Best Regards,
FTDI Community
Logged

xenon68

  • Newbie
  • *
  • Posts: 7
    • View Profile

The VinL error L0013, although listed as an error in the AN_151 document does not provide any explanation of what the error means

(Debug\vnc2.obj) : (error) L0013 error in parameter section information

There is also a message "Error During Optimization", this is also not in the AN_151


Logged

FTDI Community

  • Administrator
  • Hero Member
  • *****
  • Posts: 800
    • View Profile

Hello,

Parameter section information could be to do with the size of the linker file.

Please contact your local support office where you can share your project and we can try to help with your issues:

https://ftdichip.com/technical-support/

Best Regards,
FTDI Community
Logged