Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HDMI2USB target is broken on the Opsis #54

Closed
mithro opened this issue Sep 14, 2015 · 4 comments
Closed

HDMI2USB target is broken on the Opsis #54

mithro opened this issue Sep 14, 2015 · 4 comments

Comments

@mithro
Copy link
Member

mithro commented Sep 14, 2015

See https://travis-ci.org/timvideos/HDMI2USB-misoc-firmware/jobs/80203042

Release 14.7 - ngdbuild P.20131013 (lin64)
Copyright (c) 1995-2013 Xilinx, Inc.  All rights reserved.

Command Line:
/home/travis/build/timvideos/HDMI2USB-misoc-firmware/build/Xilinx/opt/Xilinx/14.
7/ISE_DS/ISE/bin/lin64/unwrapped/ngdbuild -uc
opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf opsis_hdmi2usb-hdmi2usbsoc-opsis.ngc
opsis_hdmi2usb-hdmi2usbsoc-opsis.ngd

Reading NGO file
"/home/travis/build/timvideos/HDMI2USB-misoc-firmware/build/misoc/build/opsis_hd
mi2usb-hdmi2usbsoc-opsis.ngc" ...
Gathering constraint information from source properties...
Done.

Annotating constraints to design from ucf file
"opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf" ...
WARNING:NgdBuild - The value of SIM_DEVICE on instance 'PLL_ADV_1' of type
   PLL_ADV has been changed from 'VIRTEX5' to 'SPARTAN6' to correct
   post-ngdbuild and timing simulation for this primitive.  In order for
   functional simulation to be correct, the value of SIM_DEVICE should be
   changed in this same manner in the source netlist or constraint file.
WARNING:NgdBuild - The value of SIM_DEVICE on instance 'PLL_ADV_2' of type
   PLL_ADV has been changed from 'VIRTEX5' to 'SPARTAN6' to correct
   post-ngdbuild and timing simulation for this primitive.  In order for
   functional simulation to be correct, the value of SIM_DEVICE should be
   changed in this same manner in the source netlist or constraint file.
WARNING:NgdBuild - The value of SIM_DEVICE on instance 'PLL_ADV_3' of type
   PLL_ADV has been changed from 'VIRTEX5' to 'SPARTAN6' to correct
   post-ngdbuild and timing simulation for this primitive.  In order for
   functional simulation to be correct, the value of SIM_DEVICE should be
   changed in this same manner in the source netlist or constraint file.
Resolving constraint associations...
Checking Constraint Associations...
WARNING:ConstraintSystem - TNM : GRPsys_clk was distributed to a DCM but new TNM
   constraints were not derived. This TNM is used in the following user groups
   or specifications:
   <TIMESPEC "TSise_sucks7" = FROM "GRPpix0_clk" TO "GRPsys_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(145)]
   <TIMESPEC "TSise_sucks8" = FROM "GRPsys_clk" TO "GRPpix0_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(146)]
   <TIMESPEC "TSise_sucks9" = FROM "GRPpix1_clk" TO "GRPsys_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(147)]
   <TIMESPEC "TSise_sucks10" = FROM "GRPsys_clk" TO "GRPpix1_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(148)]
   <TIMESPEC "TSise_sucks11" = FROM "GRPusb_clk" TO "GRPsys_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(153)]
   <TIMESPEC "TSise_sucks12" = FROM "GRPsys_clk" TO "GRPusb_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(154)]

INFO:ConstraintSystem:178 - TNM 'GRPbase50_clk', used in period specification
   'TSbase50_clk', was traced into DCM_CLKGEN instance DCM_CLKGEN_1. The
   following new TNM groups and period specifications were generated at the
   DCM_CLKGEN output(s): 
   CLKFX: <TIMESPEC TS_hdmi_out0_clocking_clk_pix_unbuffered = PERIOD
   "hdmi_out0_clocking_clk_pix_unbuffered" TSbase50_clk HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPclk100', used in period specification
   'TSclk100', was traced into BUFIO2 instance BUFIO2. The following new TNM
   groups and period specifications were generated at the BUFIO2 output(s): 
   DIVCLK: <TIMESPEC TS_hdmi2usbsoc_clk100b = PERIOD "hdmi2usbsoc_clk100b"
   TSclk100 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPclk100', used in period specification
   'TSclk100', was traced into DCM_CLKGEN instance DCM_CLKGEN. The following new
   TNM groups and period specifications were generated at the DCM_CLKGEN
   output(s): 
   CLKFX: <TIMESPEC TS_base50_clk = PERIOD "base50_clk" TSclk100 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord0_hdmi_in_clk_p', used in period
   specification 'TSrecord0_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_1. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s): 
   CLKOUT1: <TIMESPEC TS_hdmi_in0_pll_clk1 = PERIOD "hdmi_in0_pll_clk1"
   TSrecord0_hdmi_in_clk_p / 2 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord0_hdmi_in_clk_p', used in period
   specification 'TSrecord0_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_1. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s): 
   CLKOUT0: <TIMESPEC TS_hdmi_in0_pll_clk0 = PERIOD "hdmi_in0_pll_clk0"
   TSrecord0_hdmi_in_clk_p / 10 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord0_hdmi_in_clk_p', used in period
   specification 'TSrecord0_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_1. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s): 
   CLKOUT2: <TIMESPEC TS_hdmi_in0_pll_clk2 = PERIOD "hdmi_in0_pll_clk2"
   TSrecord0_hdmi_in_clk_p HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord1_hdmi_in_clk_p', used in period
   specification 'TSrecord1_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_2. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s): 
   CLKOUT1: <TIMESPEC TS_hdmi_in1_pll_clk1 = PERIOD "hdmi_in1_pll_clk1"
   TSrecord1_hdmi_in_clk_p / 2 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord1_hdmi_in_clk_p', used in period
   specification 'TSrecord1_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_2. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s): 
   CLKOUT0: <TIMESPEC TS_hdmi_in1_pll_clk0 = PERIOD "hdmi_in1_pll_clk0"
   TSrecord1_hdmi_in_clk_p / 10 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord1_hdmi_in_clk_p', used in period
   specification 'TSrecord1_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_2. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s): 
   CLKOUT2: <TIMESPEC TS_hdmi_in1_pll_clk2 = PERIOD "hdmi_in1_pll_clk2"
   TSrecord1_hdmi_in_clk_p HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered', used in
   period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered', was traced
   into PLL_ADV instance PLL_ADV_3. The following new TNM groups and period
   specifications were generated at the PLL_ADV output(s): 
   CLKOUT1: <TIMESPEC TS_hdmi_out0_clocking_pll_clk1 = PERIOD
   "hdmi_out0_clocking_pll_clk1" TS_hdmi_out0_clocking_clk_pix_unbuffered / 2
   HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered', used in
   period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered', was traced
   into PLL_ADV instance PLL_ADV_3. The following new TNM groups and period
   specifications were generated at the PLL_ADV output(s): 
   CLKOUT0: <TIMESPEC TS_hdmi_out0_clocking_pll_clk0 = PERIOD
   "hdmi_out0_clocking_pll_clk0" TS_hdmi_out0_clocking_clk_pix_unbuffered / 10
   HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered', used in
   period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered', was traced
   into PLL_ADV instance PLL_ADV_3. The following new TNM groups and period
   specifications were generated at the PLL_ADV output(s): 
   CLKOUT2: <TIMESPEC TS_hdmi_out0_clocking_pll_clk2 = PERIOD
   "hdmi_out0_clocking_pll_clk2" TS_hdmi_out0_clocking_clk_pix_unbuffered HIGH
   50%>

INFO:ConstraintSystem:178 - TNM 'hdmi2usbsoc_clk100b', used in period
   specification 'TS_hdmi2usbsoc_clk100b', was traced into PLL_ADV instance
   PLL_ADV. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s): 
   CLKOUT3: <TIMESPEC TS_hdmi2usbsoc_pll_3_ = PERIOD "hdmi2usbsoc_pll_3_"
   TS_hdmi2usbsoc_clk100b / 2 PHASE 2.916666667 ns HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi2usbsoc_clk100b', used in period
   specification 'TS_hdmi2usbsoc_clk100b', was traced into PLL_ADV instance
   PLL_ADV. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s): 
   CLKOUT5: <TIMESPEC TS_hdmi2usbsoc_pll_5_ = PERIOD "hdmi2usbsoc_pll_5_"
   TS_hdmi2usbsoc_clk100b / 0.5 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi2usbsoc_clk100b', used in period
   specification 'TS_hdmi2usbsoc_clk100b', was traced into PLL_ADV instance
   PLL_ADV. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s): 
   CLKOUT0: <TIMESPEC TS_hdmi2usbsoc_pll_0_ = PERIOD "hdmi2usbsoc_pll_0_"
   TS_hdmi2usbsoc_clk100b / 4 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi2usbsoc_clk100b', used in period
   specification 'TS_hdmi2usbsoc_clk100b', was traced into PLL_ADV instance
   PLL_ADV. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s): 
   CLKOUT4: <TIMESPEC TS_hdmi2usbsoc_pll_4_ = PERIOD "hdmi2usbsoc_pll_4_"
   TS_hdmi2usbsoc_clk100b HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi2usbsoc_clk100b', used in period
   specification 'TS_hdmi2usbsoc_clk100b', was traced into PLL_ADV instance
   PLL_ADV. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s): 
   CLKOUT2: <TIMESPEC TS_hdmi2usbsoc_pll_2_ = PERIOD "hdmi2usbsoc_pll_2_"
   TS_hdmi2usbsoc_clk100b / 2 PHASE 3.194444444 ns HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'base50_clk', used in period specification
   'TS_base50_clk', was traced into DCM_CLKGEN instance DCM_CLKGEN_1. The
   following new TNM groups and period specifications were generated at the
   DCM_CLKGEN output(s): 
   CLKFX: <TIMESPEC TS_hdmi_out0_clocking_clk_pix_unbuffered_0 = PERIOD
   "hdmi_out0_clocking_clk_pix_unbuffered_0" TS_base50_clk HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered_0', used
   in period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered_0', was
   traced into PLL_ADV instance PLL_ADV_3. The following new TNM groups and
   period specifications were generated at the PLL_ADV output(s): 
   CLKOUT1: <TIMESPEC TS_hdmi_out0_clocking_pll_clk1_0 = PERIOD
   "hdmi_out0_clocking_pll_clk1_0" TS_hdmi_out0_clocking_clk_pix_unbuffered_0 /
   2 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered_0', used
   in period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered_0', was
   traced into PLL_ADV instance PLL_ADV_3. The following new TNM groups and
   period specifications were generated at the PLL_ADV output(s): 
   CLKOUT0: <TIMESPEC TS_hdmi_out0_clocking_pll_clk0_0 = PERIOD
   "hdmi_out0_clocking_pll_clk0_0" TS_hdmi_out0_clocking_clk_pix_unbuffered_0 /
   10 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered_0', used
   in period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered_0', was
   traced into PLL_ADV instance PLL_ADV_3. The following new TNM groups and
   period specifications were generated at the PLL_ADV output(s): 
   CLKOUT2: <TIMESPEC TS_hdmi_out0_clocking_pll_clk2_0 = PERIOD
   "hdmi_out0_clocking_pll_clk2_0" TS_hdmi_out0_clocking_clk_pix_unbuffered_0
   HIGH 50%>

Done...

INFO:NgdBuild:1222 - Setting CLKIN1_PERIOD attribute associated with PLL
   instance PLL_ADV_1 to 12.000000 ns based on the period specification
   (<TIMESPEC "TSrecord0_hdmi_in_clk_p" = PERIOD "GRPrecord0_hdmi_in_clk_p" 12
   ns HIGH 50%;> [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(161)]).
INFO:NgdBuild:1222 - Setting CLKIN1_PERIOD attribute associated with PLL
   instance PLL_ADV_2 to 12.000000 ns based on the period specification
   (<TIMESPEC "TSrecord1_hdmi_in_clk_p" = PERIOD "GRPrecord1_hdmi_in_clk_p" 12
   ns HIGH 50%;> [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(164)]).
WARNING:NgdBuild:1212 - User specified non-default attribute value (20.000000)
   was detected for the CLKIN_PERIOD attribute on DCM "DCM_CLKGEN_1".  This does
   not match the PERIOD constraint value (10 ns.).  The uncertainty calculation
   will use the non-default attribute value.  This could result in incorrect
   uncertainty calculated for DCM output clocks.
INFO:NgdBuild:1222 - Setting CLKIN1_PERIOD attribute associated with PLL
   instance PLL_ADV_3 to 20.000000 ns based on the period specification
   (<TIMESPEC TS_hdmi_out0_clocking_clk_pix_unbuffered = PERIOD
   "hdmi_out0_clocking_clk_pix_unbuffered" TSbase50_clk HIGH 50%>).
WARNING:NgdBuild:1440 - User specified non-default attribute value (20.000000)
   was detected for the CLKIN1_PERIOD attribute on PLL "PLL_ADV_3".  This does
   not match the PERIOD constraint value (10 ns.).  The uncertainty calculation
   will use the PERIOD constraint value.  This could result in incorrect
   uncertainty calculated for PLL output clocks.
Checking expanded design ...
WARNING:NgdBuild:440 - FF primitive 'FDPE_7' has unconnected output pin
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<15>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<14>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<13>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<12>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<11>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<10>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<9>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<8>' has no legal driver

Partition Implementation Status
-------------------------------

  No Partitions were found in this design.

-------------------------------

NGDBUILD Design Results Summary:
  Number of errors:     0
  Number of warnings:  15

Writing NGD file "opsis_hdmi2usb-hdmi2usbsoc-opsis.ngd" ...
Total REAL time to NGDBUILD completion:  45 sec
Total CPU time to NGDBUILD completion:   44 sec

Writing NGDBUILD log file "opsis_hdmi2usb-hdmi2usbsoc-opsis.bld"...

NGDBUILD done.
Release 14.7 - Map P.20131013 (lin64)
Copyright (c) 1995-2013 Xilinx, Inc.  All rights reserved.
Using target part "6slx45tfgg484-3".
Mapping design into LUTs...
Writing file opsis_hdmi2usb-hdmi2usbsoc-opsis_map.ngm...
Running directed packing...
Running delay-based LUT packing...
Updating timing models...
WARNING:Timing:3159 - The DCM, DCM_CLKGEN_1, has the attribute DFS_OSCILLATOR_MODE not set to PHASE_FREQ_LOCK. No phase relationship exists
   between the input clock and CLKFX or CLKFX180 outputs of this DCM. Data paths between these clock domains must be constrained using
   FROM/TO constraints.
WARNING:Timing:3159 - The DCM, DCM_CLKGEN, has the attribute DFS_OSCILLATOR_MODE not set to PHASE_FREQ_LOCK. No phase relationship exists
   between the input clock and CLKFX or CLKFX180 outputs of this DCM. Data paths between these clock domains must be constrained using
   FROM/TO constraints.
INFO:Map:215 - The Interim Design Summary has been generated in the MAP Report
   (.mrp).
Running timing-driven placement...
Total REAL time at the beginning of Placer: 1 mins 59 secs 
Total CPU  time at the beginning of Placer: 1 mins 56 secs 

Phase 1.1  Initial Placement Analysis
Phase 1.1  Initial Placement Analysis (Checksum:2547d81e) REAL time: 2 mins 9 secs 

Phase 2.7  Design Feasibility Check
ERROR:Place:836 - Not enough free sites available for the components of the
   following type(s).
      LUTM      Number of Components 17430      Number of Sites 12816

ERROR:Place:375 - The design does not fit in device.
    Total LUT Utilization      : 42868 out of 54576
    LUTs used as Logic         : 25438
    LUTs used as Memory        : 17430
    FF Utilization             : 12857 out of 54576


Phase 2.7  Design Feasibility Check (Checksum:2547d81e) REAL time: 2 mins 13 secs 

Total REAL time to Placer completion: 2 mins 13 secs 
Total CPU  time to Placer completion: 2 mins 10 secs 
ERROR:Pack:1654 - The timing-driven placement phase encountered an error.

Mapping completed.
See MAP report file "opsis_hdmi2usb-hdmi2usbsoc-opsis_map.mrp" for details.
Problem encountered during the packing phase.

Design Summary
--------------
Number of errors   :   3
Number of warnings :   2
Traceback (most recent call last):
  File "make.py", line 200, in <module>
    vns = platform.build(soc, build_name=build_name, **build_kwargs)
  File "/home/travis/build/timvideos/HDMI2USB-misoc-firmware/build/migen/mibuild/xilinx/platform.py", line 28, in build
    return self.toolchain.build(self, *args, **kwargs)
  File "/home/travis/build/timvideos/HDMI2USB-misoc-firmware/build/migen/mibuild/xilinx/ise.py", line 197, in build
    self.map_opt, self.par_opt)
  File "/home/travis/build/timvideos/HDMI2USB-misoc-firmware/build/migen/mibuild/xilinx/ise.py", line 124, in _run_ise
    raise OSError("Subprocess failed")
OSError: Subprocess failed
make: *** [gateware] Error 1
travis_time:end:0dd82a26:start=1442227993825402124,finish=1442228663016460292,duration=669191058168
�[0K
�[31;1mThe command "/trusty/run.py $PWD/.travis/run.sh" exited with 2.�[0m

Done. Your build exited with 1.
@mithro
Copy link
Member Author

mithro commented Sep 14, 2015

Opsis

Selected Device : 6slx45tfgg484-3 


Slice Logic Utilization: 
 Number of Slice Registers:           12865  out of  54576    23%  
 Number of Slice LUTs:                24868  out of  27288    91%  
    Number used as Logic:             14991  out of  27288    54%  
    Number used as Memory:             9877  out of   6408   154% (*) 
       Number used as RAM:             9680
       Number used as SRL:              197

Slice Logic Distribution: 
 Number of LUT Flip Flop pairs used:  29331
   Number with an unused Flip Flop:   16466  out of  29331    56%  
   Number with an unused LUT:          4463  out of  29331    15%  
   Number of fully used LUT-FF pairs:  8402  out of  29331    28%  
   Number of unique control sets:       481

IO Utilization: 
 Number of IOs:                         125
 Number of bonded IOBs:                 109  out of    296    36%  

Specific Feature Utilization:
 Number of Block RAM/FIFO:              114  out of    116    98%  
    Number using Block RAM only:        114
 Number of BUFG/BUFGCTRLs:               13  out of     16    81%  
 Number of DSP48A1s:                     22  out of     58    37%  
 Number of PLL_ADVs:                      4  out of      4   100%  

WARNING:Xst:1336 -  (*) More than 100% of Device resources are used

Atlys

Device utilization summary:
---------------------------

Selected Device : 6slx45csg324-3 


Slice Logic Utilization: 
 Number of Slice Registers:           12504  out of  54576    22%  
 Number of Slice LUTs:                20768  out of  27288    76%  
    Number used as Logic:             14855  out of  27288    54%  
    Number used as Memory:             5913  out of   6408    92%  
       Number used as RAM:             5638
       Number used as SRL:              275

Slice Logic Distribution: 
 Number of LUT Flip Flop pairs used:  25181
   Number with an unused Flip Flop:   12677  out of  25181    50%  
   Number with an unused LUT:          4413  out of  25181    17%  
   Number of fully used LUT-FF pairs:  8091  out of  25181    32%  
   Number of unique control sets:       490

IO Utilization: 
 Number of IOs:                         137
 Number of bonded IOBs:                 122  out of    218    55%  

Specific Feature Utilization:
 Number of Block RAM/FIFO:              116  out of    116   100%  
    Number using Block RAM only:        116
 Number of BUFG/BUFGCTRLs:               12  out of     16    75%  
 Number of DSP48A1s:                     22  out of     58    37%  
 Number of PLL_ADVs:                      4  out of      4   100%  

@enjoy-digital
Copy link
Member

related to #53, buf_fifo is taking too much ressources.
I'm trying to reduce ram usage of others peripherals to allow building opsis target.

The reason it broke it that I increased a little bit firmware_ram.

@enjoy-digital
Copy link
Member

70d371c should fix it.

@mithro
Copy link
Member Author

mithro commented Sep 18, 2015

Fixed!

@mithro mithro closed this as completed Sep 18, 2015
mithro added a commit that referenced this issue Sep 19, 2018
targets: Updating for liteDRAM changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants