I’m trying to bring up Beagle Board. I would like to get help on the following issues.
It cannot be accessed through CCS using XDS510 emulator. However, I could access it through Blackhawk XDS560. Is it because 1.8V power supply is routed to 14-pin JTAG connector, which actually needs 3.3V?
Currently I have flashed X-loader, UBOOT, uImage and File System to NAND. The board boots up only when MMC card is not inserted. If I try to boot from NAND with the MMC card inserted in its slot, kernel panic occurs. Please find a log of the error attached. I’m using the pre-built binaries from the following link.
I'm trying to bring up Beagle Board. I would like to get help on the
following issues.
It cannot be accessed through CCS using XDS510 emulator. However, I could
access it through Blackhawk XDS560. Is it because 1.8V power supply is
routed to 14-pin JTAG connector, which actually needs 3.3V?
I have tried only blackhawk and Lauterbach, I think 560 is also tried.
I don't know about 510, will have to check this out.
2. Currently I have flashed X-loader, UBOOT, uImage and File System to
NAND. The board boots up only when MMC card is not inserted. If I try to
boot from NAND with the MMC card inserted in its slot, kernel panic occurs.
Please find a log of the error attached. I'm using the pre-built binaries
from the following link.
> I'm trying to bring up Beagle Board. I would like to get help on the
> following issues.
> It cannot be accessed through CCS using XDS510 emulator. However, I could
> access it through Blackhawk XDS560. Is it because 1.8V power supply is
> routed to 14-pin JTAG connector, which actually needs 3.3V?
I have tried only blackhawk and Lauterbach, I think 560 is also tried.
I don't know about 510, will have to check this out.
> 2. Currently I have flashed X-loader, UBOOT, uImage and File System to
> NAND. The board boots up only when MMC card is not inserted. If I try to
> boot from NAND with the MMC card inserted in its slot, kernel panic occurs.
> Please find a log of the error attached. I'm using the pre-built binaries
> from the following link.
> Is it possible that this kernel does not have support for MMC card? Where
> can I get the kernel with MMC driver?
We haven't encountered this problem before, can you attach the log please?
Kernel does support MMC card.
Earlier, I was trying with a 8-bit MMC card. Now I tried with a 4-bit
MMC card. And it worked fine
> What should I do to bring up Ethernet over USB?
Have a USB HUB connected to USB OTG port of beagle and then connect an
ethernet dongle to the HUB. This should give you Ethernet support.
Can you please suggest one USB/Ethernet dongle which has been tested
on Beagle board?
> I also need the link for Codec Engine.
If you have an EVM 3530, same link can be used on Beagle as
well.Otherwise you can try the following linkhttps://www-a.ti.com/downloads/sds_support/targetcontent/link/index.html
Be careful with th XDS510 - the older ones (XDS510PP) support only 3V.
Here are some from my notes to boot from MMC (Based mostly on this link)
Format MMC to FAT32 (use: HP MMC/SD Disk Format Tool) SP27213.exe
Copy the following files to the MMC:
MLO
u-boot.bin
uImage
rd-ext2.bin
Connect NULL modem cable to PC, run hyperterminal: 115200,N,8,1
Turn power to the board (you might need to keep one of the PB pressed), and after it finished booting u-boot, type the following:
mmcinit
fatload mmc 0 0x80300000 uImage
setenv bootargs console=ttyS2,115200n8 ramdisk_size=8192 root=/dev/ram0 rw rootfstype=ext2 initrd=0x81600000,8M nohz=off
fatload mmc 0 0x81600000 rd-ext2.bin
bootm 0x80300000
I hope it helps… pay attention to loading of the the rd-ext2.bin
I did not try it - you MUST have SP3 installed on your PC. Then there is somekind of a template driver from TI, I modified it a little, to adjust the vid and pid to the ones in the linux kernel. This enables RNDIS (ethernet over USB) on your PC.
Next - the linux kernel should have RNDIS compiled in it, I think the one that supplied already have it - not sure.
And I suppose all you need to do is connect the USB cable to a PC and that’s it.
I might be mistaken regarding the rndis_omap3.inf which I created - I might made it for another omap3 based platform for Win-CE, and I think there is “linux.inf” configuration file somewhere that does the same job.
I made a 20-to-14 pin adapter for XDS510 and it worked fine.
MMC boot also worked. What i figured out is the 8-bit MMC card (1.8V type) is not supported. So before booting the board, MMC card should be pulled out. But if you are using a 4-bit card (3.3V only) it works without issue. I guess, after the board has been booted up, TWL4030 can be accessed to change the MMC supply to 1.8 V so that 8-bit card can also work.
Regarding RNDIS, i guess a Linux PC is needed, which i don’t have. So I purchased a USB to LAN adapter (based on Davicom’s DM9601 chip). I built the driver as .ko and did insmod. It worked but transfer rate is slow. It hangs while transferring a larger file via ftp. Any support is appreciated.
Linux PC is NOT needed, all you need is WinXP SP3 (service pack 3), and it has inside of it RNDIS support.
All is needed is to have an .inf file that would tell windows that the specific USB device, indetified by ONLY two 16 bit numbers: VID (vendor ID) and PID (product? ID) is actualy an RNDIS device, and I believe that the linux.inf (or my previous .inf file, or maybe it should be modified a little) do this on WinXP.
Nazmul Hoda said the following on 09/09/2008 08:07 PM:
Thanks Yuli,
I made a 20-to-14 pin adapter for XDS510 and it worked fine.
Curious: How did you handle this to talk with OMAP3430? Did you use some
sort of voltage translators? could you share your experience with the
gang? a photograph could help too for others to get started (If you have
schematics.. that would be awesome).. I think there are blokes with old
510s lying around..
I could modify the RNDIS driver (added the correct VID & PID). Now when i connect Beagle to PC, i see a new LAN connection on the PC named “Acme USB Remote NDIS Network Device #2”. But it says network cable unplugged.
When i did "ifconfig usb0" on Beagle i got the following.
I could modify the RNDIS driver (added the correct VID & PID). Now when i connect Beagle to PC, i see a new LAN connection on the PC named “Acme USB Remote NDIS Network Device #2”. But it says network cable unplugged.
When i did "ifconfig usb0" on Beagle i got the following.
This means IP addess is not set. Then how to get the IP address? Do i need to bridge it to another port?
You can get the IP address many different ways. It is probably easiest for you to simply manually assign an IP address. One way to do so is ‘ifconfig usb0 up 192.168.10.2’.
You should then get network connection on your PC, though also without an IP address. You can open up the TCP/IP properties on the net connection and manually assign an address, such as 192.168.10.1.
You’ll want to have a gateway setup on the device as well. I don’t believe that is covered. Can anyone recommend a good howto on setting up networking on the device to include the gateway info?
You'll want to have a gateway setup on the device as well. I don't
believe that is covered. Can anyone recommend a good howto on setting
up networking on the device to include the gateway info?
Look up the ip= kernel command line parameter. It's a set of colon-delimited
fields, one of which is the network gateway's IP.
i could make the network up this with following method.
Modified rndis_omap3.inf (avaialable in this mail chain) to include the VID and PID of the Board.
VID and PID can be found by checking the System Properties → Hardware → Device manager → Network Adapter → XXX → Details, Where XXX is the name of the network that appears when you connect Beagle to the PC.
After Beagle boots up, PC will look for RNDIS driver. Provide the path to the above file. With this you can see a new network connection in your system which will say “network cable unplugged”.
Now execute ifconfig usb0 up on Beagle. New Network will be shown as connected.
On the PC you need to bridge this network with the avialable Ethernet port.
Once the Bridge is configured and shown as connecte, Execute the following on the Beagle.
udhcpc -i usb0 (This will return an IP address)
ifconfig usb0 (Give the above IP address)
Set the voltage adapter into 'BYPASS: No adaptive clocking adapter"
And then when connecting to the omap3 chip it complains regarding the
DM64x core. Press 'ignore' few times and you have connectivity to the
Cortex core.
To run the DM64x core you need to run the GEL file to enable clocking
(from withing the debugger scope while debugging Cortex, see posting
few days ago in the same thread), and only then it is possible to
connect with another instance of the debugger to the DM64x core.
It works on only one of the USB ports