uClinux can not be halted with OpenOCD
Hi all, I have a setup on ARM946E that works well for loading and booting uClinux, and during the boot phase I can stop and single-step kernel. But once booted, when it gives prompt, pressing CTRL-C in GDB can not halt the board : ^CHalt timed out, wake up GDB. Program received signal SIGINT, Interrupt. stext () at arch/arm/kernel/head-nommu.S:40 40 ldr r1, =machine_arch_type @ find the machine type (gdb) And messages from OpenOCD are these : Info : Halt timed out, wake up GDB. Warn : target not halted Warn : ThumbEE -- incomplete support Do you have any ideas what is happening ? I suspected on low-power mode, but uClinux does not enter it (I think). Best regards, Drasko -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktin_65mvjhspa8t14cd4n5_is_sblyd7kixfs...@mail.gmail.com
arm-linux-gnu-gdb target sim missing
Hi all, I cannot lounch target sim in arm-linux-gnu-gdb. Any ideas why and how to fix this? dra...@marx:~/arm$ arm-linux-gnu-gdb GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as --host=i486-linux-gnu --target=arm-linux-gnu. *(gdb) taget sim Undefined command: taget. Try help.* (gdb) help target Connect to a target machine or process. The first argument is the type or protocol of the target machine. Remaining arguments are interpreted by the target protocol. For more information on the arguments for a particular protocol, type `help target ' followed by the protocol name. List of target subcommands: target async -- Use a remote computer via a serial line target core -- Use a core file as a target target exec -- Use an executable file as a target target extended-async -- Use a remote computer via a serial line target extended-remote -- Use a remote computer via a serial line target remote -- Use a remote computer via a serial line Type help target followed by target subcommand name for full documentation. Type apropos word to search for commands related to word. Command name abbreviations are allowed if unambiguous. (gdb) Best regards, Drasko
Re: arm-linux-gnu-gdb target sim missing
On Sat, Mar 21, 2009 at 10:45 PM, Drasko DRASKOVIC drasko.drasko...@gmail.com wrote: Hi all, I cannot lounch target sim in arm-linux-gnu-gdb. Any ideas why and how to fix this? dra...@marx:~/arm$ arm-linux-gnu-gdb GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as --host=i486-linux-gnu --target=arm-linux-gnu. *(gdb) target sim Undefined target command: sim. Try help target.* (gdb) help target Connect to a target machine or process. The first argument is the type or protocol of the target machine. Remaining arguments are interpreted by the target protocol. For more information on the arguments for a particular protocol, type `help target ' followed by the protocol name. List of target subcommands: target async -- Use a remote computer via a serial line target core -- Use a core file as a target target exec -- Use an executable file as a target target extended-async -- Use a remote computer via a serial line target extended-remote -- Use a remote computer via a serial line target remote -- Use a remote computer via a serial line Type help target followed by target subcommand name for full documentation. Type apropos word to search for commands related to word. Command name abbreviations are allowed if unambiguous. (gdb) Best regards, Drasko
gdb package cannot install?
Marx:/home/drasko# apt-get install gdb-arm-linux-gnu Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: gdb-doc The following NEW packages will be installed: gdb-arm-linux-gnu 0 upgraded, 1 newly installed, 0 to remove and 189 not upgraded. Need to get 0B/2348kB of archives. After this operation, 5046kB of additional disk space will be used. (Reading database ... 107197 files and directories currently installed.) Unpacking gdb-arm-linux-gnu (from .../gdb-arm-linux-gnu_6.8-3_i386.deb) ... dpkg: error processing /var/cache/apt/archives/gdb-arm-linux-gnu_6.8-3_i386.deb (--unpack): trying to overwrite `/usr/share/man/man1/gdb.1.gz', which is also in package gdb dpkg-deb: subprocess paste killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/gdb-arm-linux-gnu_6.8-3_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Marx:/home/drasko# Any ideas?
dpkg-cross unresolved dependencies for libgcc1-arm-cross
Hi all, I have problem with dpkg-cross. I have been following the instruction on http://www.handhelds.org/~pb/deb-toolchain.html to make ARM cross toolchain for Debian, but there is a step which gives me error: Lenin:/home/drasko/arm_packages# dpkg-cross --arch arm --install libc6-dev_2.6.1-6_arm.deb libc6_2.6.1-6_arm.deb Building libc6-dev-arm-cross_2.6.1-6_all.deb Building libc6-arm-cross_2.6.1-6_all.deb Unpacking libc6-dev-arm-cross Unpacking libc6-arm-cross dpkg: dependency problems prevent configuration of libc6-dev-arm-cross: libc6-dev-arm-cross depends on linux-libc-dev-arm-cross; however: Package linux-libc-dev-arm-cross is not installed. libc6-dev-arm-cross depends on linux-libc-dev-arm-dcv1; however: Package linux-libc-dev-arm-dcv1 is not installed. dpkg: error processing libc6-dev-arm-cross (--install): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libc6-arm-cross: libc6-arm-cross depends on libgcc1-arm-cross; however: Package libgcc1-arm-cross is not installed. libc6-arm-cross depends on libgcc1-arm-dcv1; however: Package libgcc1-arm-dcv1 is not installed. dpkg: error processing libc6-arm-cross (--install): dependency problems - leaving unconfigured Errors were encountered while processing: libc6-dev-arm-cross libc6-arm-cross dpkg -i failed. Lenin:/home/drasko/arm_packages# How to resolve these dependencies? Kind regards, Drasko DRASKOVIC
Question about AMBA device registering
Hi all. can anybody explain me these lines:for (pid = 0, i = 0; i 4; i++) pid |= (readl(tmp + 0xfe0 + 4 * i) 255) (i * 8); for (cid = 0, i = 0; i 4; i++)
cid |= (readl(tmp + 0xff0 + 4 * i) 255) (i * 8); iounmap(tmp); if (cid == 0xb105f00d) dev-periphid = pid;
if (dev-periphid) ret = device_register(dev-dev); else ret = -ENODEV; in amba.c, in /arc/arm/common. I pasted the whole
amba_device_register() fnc. below. I need to register my i2c_device as an amba_device, so I have question about .periphid member od amba_device struct. What number does it represent? Is it connected to above lines found in
amba.c and how? Looks like it is, but I can decypher these... I have UARTS defined as amba_device: static struct amba_device uart0_device = { .dev = { .bus_id = dev:00,
}, .res = { .start = UART0_BASE, .end = UART0_BASE + SZ_4K - 1, .flags = IORESOURCE_MEM, }, .irq = { UARTINTR0_VECTOR, NO_IRQ },
.periphid= 0x0041010, }; Here stands .periphid = 0x0041010. Why? Is this number something specific to AMBA or to UART? I can find this nuber figure in several
more files, like arch/arm/mach-integrator/core.c, but also for uart device... Also, can anybody describe me .bus_id part of .dev structure (why is it initialized to dev:00 and what are possible initializers)? In
arch/arm/mach-integrator/core.c there stands mb:15, mb:16... for devices. In mine core.c they start from dev:00. Still I can not understand what this value means...
- /** * amba_device_register - register an AMBA device * @dev: AMBA device to register * @parent: parent memory resource * * Setup the AMBA device, reading the cell ID if present.
* Claim the resource, and register the AMBA device with * the Linux device manager. */ int amba_device_register(struct amba_device *dev, struct resource *parent) { u32 pid, cid;
void __iomem *tmp; int i, ret; dev-dev.release = amba_device_release; dev-dev.bus = amba_bustype; dev-dev.dma_mask = dev-dma_mask;
dev-res.name = dev-dev.bus_id; if (!dev-dev.coherent_dma_mask dev-dma_mask)
dev_warn(dev-dev, coherent dma mask is unset\n);
ret = request_resource(parent, dev-res); if (ret == 0) { tmp = ioremap(dev-res.start, SZ_4K); if (!tmp) { ret = -ENOMEM;
goto out; } for (pid = 0, i = 0; i 4; i++) pid |= (readl(tmp + 0xfe0 + 4 * i) 255) (i * 8);
for (cid = 0, i = 0; i 4; i++) cid |= (readl(tmp + 0xff0 + 4 * i) 255) (i * 8); iounmap(tmp); if (cid == 0xb105f00d)
dev-periphid = pid; if (dev-periphid) ret = device_register(dev-dev); else ret = -ENODEV;
if (ret == 0) { device_create_file(dev-dev, dev_attr_id); if (dev-irq[0] != NO_IRQ) device_create_file(dev-dev, dev_attr_irq0);
if (dev-irq[1] != NO_IRQ) device_create_file(dev-dev, dev_attr_irq1); device_create_file(dev-dev, dev_attr_resource);
} else { out: release_resource(dev-res); } } return ret;} -- Drasko DRASKOVIC
Software DeveloperElsys-DESIGNBelgrade, SerbiaTel. +381.11.311.5252Fax. +381.11.311.5251www.elsys-design.com
