Hi,
Board: Beagle board xM rev C. OS: Android 2.3 BSP: TI ginger bread.I am using the above configuration and if I connect any USB device to USB ports those are not getting recognized and not getting power also (confirmed by seeing LED on USB device).
Can anyone please tell me how to enable USB host hub to work in BSP.Thanks in advance.Regards, Bharathi
Beagleboard XM rev C is supported from TI Android GingerBread 2.3.4 DevKit 2.1 release onwards. http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_ReleaseNotes
Please ensure that you are using this release or the latest sources from rowboat.
--------------------------------------------------------------------------------------------------------- Please click the Verify Answer button on this post if it answers your question.---------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------
Please click the Verify Answer button on this post if it answers your question.---------------------------------------------------------------------------------------------------------
Thanks for reply.
We are using latest sources from rowboat.
Do you get any errors/logs on the serial port when you connect the usb hub?
If yes, please post here.
Regards,
Arun
If this post answers your query, consider clicking the Verify Answer button.
Hi Arun,
My problem got solved by using new Android version i.e., 2.3.4.
I written a usb kernel device driver. while inserting this module I am getting the following errors.
bt_kdrv_linux: disagrees about version of symbol usb_interrupt_msgbt_kdrv_linux: Unknown symbol usb_interrupt_msg (err -22)bt_kdrv_linux: disagrees about version of symbol usb_bulk_msgbt_kdrv_linux: Unknown symbol usb_bulk_msg (err -22)bt_kdrv_linux: disagrees about version of symbol usb_control_msgbt_kdrv_linux: Unknown symbol usb_control_msg (err -22)insmod: init_module 'bt_kdrv_linux.ko' failed (Invalid argument)
FYI, I built this module with the kernel version 2.6.37.
Bharathi.
Hi Bharathi,
These errors are due to the mismatch between the kernel sources and the module. Try to use the same uImage of the kernel sources which was used for building the module.
Thanks for the reply.
I will try and let you know.
I was using Android-2.3.4 pre-built images provided by TI for beagle board xM.
I downloaded Android sources and built kernel as described in "TI-Android-GingerBread-2.3.4-DevKit-2.1DeveloperGuide" by using the specified tool chain.
I copied the generated uImage which is of 3.1MB to Boot_Images folder and loaded to sd card.
Hanging at boot time,
Running bootscript from mmc ...## Executing script at 82000000reading uImage3299316 bytes read***** Kernel: /dev/mmcblk0p1/uImage ********** RootFS: /dev/mmcblk0p2 *****## Booting kernel from Legacy Image at 82000000 ... Image Name: Linux-2.6.37-g06ebbba Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3299252 Bytes = 3.1 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OKOKStarting kernel ...
Am I missing anything to change while loading a new kernel image?
I tried your suggestion but still I am getting the same error.
Can you please help me out how to solve this issue.
I believe you are still referring to the module mismatch error.
When building module, you need to point to the kernel tree inside the 2.3.4 android sources and while loading, use the same uImage built from these sources.
Also can you try build this specific driver inside the kernel?
Hi arun.
This solved my issue.
Now my usb kernel driver working as expected.
Thank you so much.