Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
10 years ago

nallatech SDK problem

hi

There are some SDK (pcie385n_a7 and pcie385_d5).

But when I execute the helloworld program , I can not execute successfully.

I tried to execute other program , the same situation happened (ERROR: CL_INVALID_BINARY)

How to solve this problem ?

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

This shouldn't happen: 6ee4c670-6bf3-4db4-872e-fb383606a7e3

Error: dd00cd6b-c947-40ff-95a0-41bcf30dcc31

device_id = 0x4

Unrecognised card type, so can't instantiate appropriate Flash/UFM/UCD classes!

Querying platform for info:

==========================

CL_PLATFORM_NAME = Altera SDK for OpenCL

CL_PLATFORM_VENDOR = Altera Corporation

CL_PLATFORM_VERSION = OpenCL 1.0 Altera SDK for OpenCL, Version 14.0

Querying device for info:

========================

CL_DEVICE_NAME = pcie385n_d5 : Unknown

CL_DEVICE_VENDOR = Nallatech ltd

CL_DEVICE_VENDOR_ID = 4466

CL_DEVICE_VERSION = OpenCL 1.0 Altera SDK for OpenCL, Version 14.0

CL_DRIVER_VERSION = 14.0

CL_DEVICE_ADDRESS_BITS = 64

CL_DEVICE_AVAILABLE = true

CL_DEVICE_ENDIAN_LITTLE = true

CL_DEVICE_GLOBAL_MEM_CACHE_SIZE = 32768

CL_DEVICE_GLOBAL_MEM_CACHELINE_SIZE = 0

CL_DEVICE_GLOBAL_MEM_SIZE = 4294967296

CL_DEVICE_IMAGE_SUPPORT = false

CL_DEVICE_LOCAL_MEM_SIZE = 16384

CL_DEVICE_MAX_CLOCK_FREQUENCY = 1000

CL_DEVICE_MAX_COMPUTE_UNITS = 1

CL_DEVICE_MAX_CONSTANT_ARGS = 8

CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE = 1073741824

CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS = 3

CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS = 8192

CL_DEVICE_MIN_DATA_TYPE_ALIGN_SIZE = 1024

CL_DEVICE_PREFERRED_VECTOR_WIDTH_CHAR = 4

CL_DEVICE_PREFERRED_VECTOR_WIDTH_SHORT = 2

CL_DEVICE_PREFERRED_VECTOR_WIDTH_INT = 1

CL_DEVICE_PREFERRED_VECTOR_WIDTH_LONG = 1

CL_DEVICE_PREFERRED_VECTOR_WIDTH_FLOAT = 1

CL_DEVICE_PREFERRED_VECTOR_WIDTH_DOUBLE = 0

Command queue out of order? = false

Command queue profiling enabled? = true

Using AOCX: hello_world.aocx

ERROR: CL_INVALID_BINARY

Location: ../common/src/AOCL_Utils.cpp:391

Failed to create program with binary

""""

6 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    Hi,

    The BSP version that was used to create the file in flash must match the BSP version that you have installed on the host.

    You need to update the flash with the base.aocx file for the BSP you have installed on your host.

    Because you can't use the software utilities at this point (because of the firmware mismatch), you will need to update the flash via JTAG.

    Power the host down

    Connect USB-Blaster REV-C to 385 board and host

    https://www.youtube.com/watch?v=mggkjwetwsq

    https://www.youtube.com/watch?v=fvvwpibwimo

    Connect the USB cable to the host

    Power up the host

    When in OS, browse to BSP location; for example: /opt/altera/15.0/hld/boards/nalla_pcie/hardware/p385_hpc_d5

    Run the perl script to update the flash: "perl flash_recovery.pl base.aocx"

    This will take around 20min, when finished power down the host (a reboot will not be enough)

    Power up the host

    When in OS, run "aocl diagnose acl0" to verify everything is OK

    Thanks
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    hi

    I have done the step ( Connect the USB cable to the host)

    lspci (Unassigned class [ff00]: Altera Corporation Device ab00)

    But I entered the directory : /home/user/altera/14.0/hld/boards/nalla_pcie/hardware/p385_hpc_d5 and ran the perl flash_recovery.pl base.aocx

    The error messages showed that

    """"""""""""""""

    Error (209062): Flash Loader IP not loaded on device 0

    Error (209053): Unexpected error in JTAG server -- error code 5

    Error (209053): Unexpected error in JTAG server -- error code 89

    Error (209012): Operation failed

    Info (209061): Ended Programmer operation at Fri Jul 24 09:38:18 2015

    Error: Quartus II 64-Bit Programmer was unsuccessful. 4 errors, 0 warnings

    Error: Peak virtual memory: 1681 megabytes

    Error: Processing ended: Fri Jul 24 09:38:18 2015

    Error: Elapsed time: 00:00:05

    Error: Total CPU time (on all processors): 00:00:05

    Error: quartus_cpf failed at flash_recovery.pl line 92.

    """"""""""""""""

    How to solve the problem ?
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    When running the flash_recovery script, the board must be powered and connected to the JTAG programming cable as shown in the doc linked below. You must run the script from the computer the JTAG programming cable is plugged into with the USB cable. The board must be powered.

    Also, please make sure the USB config file is correctly setup:

    https://www.altera.com/support/support-resources/download/drivers/dri-usb_b-lnx.html

    You might also need to run as root.

    http://www.alteraforum.com/forum/attachment.php?attachmentid=8908&d=1400634781
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    Hi boyihuang,

    Are you now up and running?

    Did the above solve your issue?

    G
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    Thank for your help

    I could run the example successfully : )

    But I downloaded the examples(channelizer and Monte Carlo) , I could not complie the example successfully.

    It always showed " internal complie error "

    The board I used is nallatech pcie385N

    Tnanks
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    Great news on getting things running!

    Regarding your compilation issue: to get additional info about your "internal compile error", go to the compilation kernel folder and look into the <kernel>.log and the quartus_sh_compile.log you will find details about the issue.