Tool/software: Linux
I am adding an LCD node to the DTS of my custom AM5708 board with the following message:
adam@Roark:~/ti-processor-sdk-linux-am57xx-evm-04.02.00.09/board-support/u-boot-2017.01+gitAUTOINC+340fb36f04-g340fb36f04$ make ARCH=arm
CROSS_COMPILE=arm-linux-gnueabihf- dtbs -j4
CHK include/config/uboot.release
CHK include/generated/timestamp_autogenerated.h
UPD include/generated/timestamp_autogenerated.h
CHK include/generated/version_autogenerated.h
CHK include/generated/generic-asm-offsets.h
CHK include/generated/asm-offsets.h
HOSTCC tools/mkenvimage.o
HOSTCC tools/fit_image.o
HOSTCC tools/image-host.o
HOSTCC tools/dumpimage.o
HOSTCC tools/mkimage.o
HOSTLD tools/mkenvimage
HOSTLD tools/dumpimage
HOSTLD tools/mkimage
CC cmd/version.o
CC common/main.o
LD cmd/built-in.o
CC common/board_f.o
CC drivers/usb/gadget/f_fastboot.o
LD common/built-in.o
CC lib/smbios.o
CC lib/display_options.o
CC lib/efi_loader/helloworld.o
LD drivers/usb/gadget/built-in.o
LD lib/efi_loader/helloworld.so
OBJCOPY lib/efi_loader/helloworld.efi
LD lib/built-in.o
LD u-boot
DTC arch/arm/dts/am5708-dev.dtb
Error: <stdin>:512.7-14 syntax error
FATAL ERROR: Unable to parse input tree
scripts/Makefile.lib:322: recipe for target 'arch/arm/dts/am5708-dev.dtb' failed
make[2]: *** [arch/arm/dts/am5708-dev.dtb] Error 1
dts/Makefile:36: recipe for target 'arch-dtbs' failed
make[1]: *** [arch-dtbs] Error 2
Makefile:853: recipe for target 'dts/dt.dtb' failed
make: *** [dts/dt.dtb] Error 2
Here is my addition at the top-level DTS:
lcd0: display {
compatible = "osddisplays,osd070t1718-19ts", "panel-dpi";
label = "lcd";
backlight = <&lcd_bl>;
enable-gpios = <&gpio2 5 GPIO_ACTIVE_HIGH>;
panel-timing {
clock-frequency = <33000000>;
hactive = <800>;
vactive = <480>;
hfront-porch = <210>;
hback-porch = <16>;
hsync-len = <30>;
vback-porch = <10>;
vfront-porch = <22>;
vsync-len = <13>;
hsync-active = <0>;
vsync-active = <0>;
de-active = <1>;
pixelclk-active = <1>;
};
port {
lcd_in: endpoint {
remote-endpoint = <&dpi_out0>;
};
};
};
Can someone point out a possible issue here?
