Quantcast
Channel:
Viewing all articles
Browse latest Browse all 59170

Forum Post: RE: RZA1H starter kit debugging application on linux using j link

$
0
0
Could you please send me the .config files for the kernel and the buildroot? The kernel was nothing special. If you used the standard rskrza1_defconfig for your uImage, then that's all I did. For the XIP build (rskrza1_xip_defconfig), since Qt requires socket support, and rskrza1_xip_defconfig didn't have networking, I just had to add: CONFIG_NET=y  and CONFIG_UNIX=y For the Buildroot, all I did was enable on Qt 4.8. I also enabled the examples and demos options under Qt 4.8...but that made the rootfs VERY big (bigger that he QSPI), so I basically removed almost all the example binaries from the 'target' directory, then recreated my rootfs image. Here's what it looks like inside my .config # # Other GUIs # # BR2_PACKAGE_EFL is not set BR2_PACKAGE_QT=y # BR2_PACKAGE_QT_DEBUG is not set BR2_PACKAGE_QT_DEMOS=y BR2_PACKAGE_QT_EXAMPLES=y BR2_PACKAGE_QT_SHARED=y # BR2_PACKAGE_QT_STATIC is not set # BR2_PACKAGE_QT_LICENSE_APPROVED is not set BR2_PACKAGE_QT_CONFIG_FILE="" # BR2_PACKAGE_QT_QT3SUPPORT is not set BR2_PACKAGE_QT_GUI_MODULE=y p.s. Sometimes when I start the board the screen just stays white, and I can't see anything, if I reboot the board sometimes it works again and I can see again, sometimes stays white...how can I fix this? That one I don't have an idea about. The LCD is set up in the kernel, and those pins are all output, so it doesn't need to READ anything from the LCD. The I2C lines are for the capacitive touchscreen controller are also on that connector. Do they work OK? you can use ts_print after you log into your board and see if the touchscreen is working correctly. My only suggestion is to make sure the board is plugged in good. Whenever I've had screen issues, it was because my board was not plugged in all the way

Viewing all articles
Browse latest Browse all 59170

Trending Articles