Can't disassemble my device driver
I have a adatron bdi 2000 connected to my target board and have successfully load the linux kernel and set breakpoint in schedule However when I load my device driver, it's text section is a 0xD11D6060 and the kernel is a 0xC00xxxxx. When is disassemble any routine in my driver, I get all zeros.
I have MMU xlate set in the config file and I program the mmu correctly
since I can break a schedule. Any help would be apprecciated
Tom
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Hi Tom,
Quoted 6 lines · in message <[email protected]> you wrote:
I have a adatron bdi 2000 connected to my target board and have successfully load the linux kernel and set breakpoint in schedule However when I load my device driver, it's text section is a
0xD11D6060and the kernel is a 0xC00xxxxx. When is disassemble any routine in my driver, I get all zeros.
See the hints (and utility scripts) in section "8.2.2. Dynamically
Loaded Device Drivers (Modules)" of our documentation at
http://www.denx.de/doc/TQM8xxL/debugging.html
Quoted 2 lines
I have MMU xlate set in the config file and I program the mmu correctly
since I can break a schedule. Any help would be apprecciated
You also have to use PTBASE in combination with a kernel that updates these pointers. See the BDI2000 documentation.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: [email protected] In theory, there is no difference between theory and practice. In practice, however, there is.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Quoted 6 lines · Tom Stefanski
I have a adatron bdi 2000 connected to my target board and have successfully load the linux kernel and set breakpoint in schedule However when I load my device driver, it's text section is a
0xD11D6060and the kernel is a 0xC00xxxxx. When is disassemble any routine in my driver, I get all zeros.
Quoted 8 lines
I have MMU xlate set in the config file and I program the mmu correctly
since I can break a schedule. Any help would be apprecciatedTom
Did you remember to specify the text address when you added the symbol file in gdb? If you didn't type 'help add-symbol-file' in gdb and it will explain where you can specify the starting text address of your device driver module. Neil
-- /****************************************************************** *Neil Horman
*Software Engineer
*LVL7 Systems
*13000 Weston Pkwy.
*Cary, NC 27513
*(919)-865-2915
*[email protected]
*PGP keyID 0xB5E1020A
*http://www.keyserver.net/en *******************************************************************/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/