This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: BEAGLEBK
Tool/software: Code Composer Studio
Dear TI support team,
I have set up an sd card through the create sd-card.sh script, I have copied to SD
When I boot the BBB I get:
StarterWare Boot Loader BOARDInit status [0x0] SoC : [AM335X] Core : [A8] Board Detected : [BEAGLEBONEBLACK] Base Board Revision : [UNKNOWN] Daughter Card Revision: [UNKNOWN] Copying application image from MMC/SD card to RAM Jumping to StarterWare Application...
but the led never starts to blink.
Using the same MLO, I am able to run gpio_app_led_blink_a8host_debug_ti.bin in the starterware/binary/gpio_app_led_blink/bin/am335x-evm .
I am also able to run the GPIO_LedBlink_bbbAM335x_armTestProject in CCS using the JTAG debugging.
When I run the MLO and app in processor_sdk_rtos_am335x_4_02_00_09/prebuilt-sdcards/evmAM335x , I get
StarterWare Boot Loader BOARDInit status [0x0] SoC : [AM335X] Core : [A8] Board Detected : [BEAGLEBONEBLACK] Base Board Revision : [UNKNOWN] Daughter Card Revision: [UNKNOWN] Copying application image from MMC/SD card to RAM Jumping to StarterWare Application... I2C Test: 400Kbps: Data Mismatch I2C Test: 100Kbps:Data Mismatch Some tests have failed.
I have noticed that the _c_int00 of the executable of GPIO_LedBlink_bbbAM335x_armTestProject is loaded after 0x80000000 . May this be the cause of the problem? Should I use a different bootloader?
Here more info about my configuration:
os : ubuntu 16.04
sdk: processor_sdk_rtos_am335x_4_02_00_09
ccs: 7.3.0.00019
BBB revision : C
source pdksetupenv.sh ************************************************************************** Environment Configuration: LIMIT_SOCS : am335x LIMIT_BOARDS : evmAM335x icev2AM335x iceAMIC110 bbbAM335x skAM335x PDK_INSTALL_PATH : /home/riccardo/ti/pdk_am335x_1_0_9/packages C6X_GEN_INSTALL_PATH : /home/riccardo/ti/ti-cgt-c6000_8.2.2 TOOLCHAIN_PATH_GCC : /home/riccardo/ti/gcc-arm-none-eabi-6-2017-q1-update TOOLCHAIN_PATH_A15 : /home/riccardo/ti/gcc-arm-none-eabi-6-2017-q1-update TOOLCHAIN_PATH_A8 : /home/riccardo/ti/gcc-arm-none-eabi-6-2017-q1-update TOOLCHAIN_PATH_A9 : /home/riccardo/ti/gcc-arm-none-eabi-6-2017-q1-update TOOLCHAIN_PATH_M4 : /home/riccardo/ti/ti-cgt-arm_16.9.3.LTS TOOLCHAIN_PATH_Arm9 : /home/riccardo/ti/ti-cgt-arm_16.9.3.LTS TOOLCHAIN_PATH_EVE : /home/riccardo/ti/arp32_1.0.8 CL_PRU_INSTALL_PATH : /home/riccardo/ti/ti-cgt-pru_2.1.5 HARDLIB_PATH : /home/riccardo/ti/gcc-arm-none-eabi-6-2017-q1-update/lib/gcc/arm-none-eabi/6.3.1/hard CROSS_TOOL_PRFX : arm-none-eabi- XDC_INSTALL_PATH : /home/riccardo/ti/xdctools_3_50_03_33_core BIOS_INSTALL_PATH : /home/riccardo/ti/bios_6_52_00_12 IPC_INSTALL_PATH : /home/riccardo/ti/ipc_3_47_00_00 EDMA3LLD_BIOS6_INSTALLDIR : /home/riccardo/ti/edma3_lld_2_12_05_30B NDK_INSTALL_PATH : /home/riccardo/ti/ndk_2_26_00_08 IMGLIB_INSTALL_PATH : /home/riccardo/ti/imglib_c66x_3_1_1_0 DSPLIB_INSTALL_PATH : /home/riccardo/ti/dsplib_c66x_3_4_0_0 MATHLIB_INSTALL_PATH : /home/riccardo/ti/mathlib_c66x_3_1_1_0 UIA_INSTALL_PATH : /home/riccardo/ti/uia_2_21_02_07 CG_XML_BIN_INSTALL_PATH : ~/ti/cg_xml/bin PDK BUILD ENVIRONMENT CONFIGURED *******************************************************************************
Riccardo,
Thanks for providing the information regarding the version of the SDK that you are using and providing specific information on what is working with your setup vs what is not.
I have been able to reproduce the issue that you are running into and can confirm that there is a known issue with using bootloader from this release with TI RTOS LLD examples that seems to have been introduced with the ARM GCC compiler update that came in the late for the PRSDK 4.02 version of the SDK.
It is unclear to me if the issue is caused due to ARM init code in the bootloader which causes an exception when RTOS LLD example is loaded or if there was an issue in the OSAL layer that has fixed this issue but I picked up the evaluation version of the upcoming PRSDK v4.03 release and can confirm that this issue is resolved.
I have attached the binaries from the PRSDK 4.03 release for you to confirm with your setup. The release should be available on ti.com in the next couple of days.
Regards,
Rahul
Hi Rahul,
here are the binaries. I have also tried the MLO that you have provided me, but it does not work.
/cfs-file/__key/communityserver-discussions-components-files/791/ti-forum-binaries.tar.gz
Riccardo