Forum Replies Created
-
AuthorPosts
-
March 11, 2018 at 17:09 in reply to: Trouble debugging sample kernel module (RPi 1 + J-Link via JTAG) #20365maiorfiParticipant
Hi. Sadly, manual setup still shows reading zero blocks when executing “x/16xb” gdb command. I also tried some “mon mdw <address> <count>” commands, but looking at module list block I only find:
0xbf1e4940: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e4960: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e4980: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e49a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e49c0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e49e0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e4a00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e4a20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e4a40: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e4a60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e4a80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e4aa0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0xbf1e4ac0: 00000000 00000000 00000000 00000000Just to be sure JTAG is working as expected I also tried to run a mon mdw at a different address I spotted in gdb trace, and there I can find some “non-zero” content:
0xc001d4d4: e1a00000 e1a00000 e1a00000 1afffff7 e12fff1e ee070f3a e2800020 e2511020
0xc001d4f4: 8afffffb e12fff1e e3a02000 e5911158 e3800008 ee072fd5 ee072f9a ee020f10
0xc001d514: ee0d1f30 e12fff1e 00000000 00000040 00000008 0000000c 00000004 00000000
0xc001d534: 00000000 0000004c 00000000 00000040 00000000 0000000cIs there any other board I could try? I’m using a RPi 1, since it seems that RPi3 is not supported by my J-Link (V8), but I have plenty of other arm-based linux embedded devices I could try with.
Thanks!
March 5, 2018 at 13:06 in reply to: DirectSSH sample works, but target hangs after a minute or so #20320maiorfiParticipantHi. I tried same test on a VMWare virtual machine target, and it works a treat!
Thanks.
March 4, 2018 at 09:47 in reply to: Trouble debugging sample kernel module (RPi 1 + J-Link via JTAG) #20314maiorfiParticipantPutting “mon sleep 3000” only after target remote command “command not supported by this target” issue is solved, but I still get the original issue.
Please find gdb and OCD logs as attachments.
Thanks.
Attachments:
You must be logged in to view attached files.March 4, 2018 at 09:40 in reply to: Trouble debugging sample kernel module (RPi 1 + J-Link via JTAG) #20313maiorfiParticipantHi. Sorry for my delay.
Sadly “mon sleep 3000” returns on GDB session log “&”\”monitor\” command not supported by this target.\n””
February 26, 2018 at 12:01 in reply to: DirectSSH sample works, but target hangs after a minute or so #20270maiorfiParticipant…I don’t know if it is relevant, but the last line I can read on VisualKernel Program Output (just below log line printed by module_init function) is “rfkill: input handler disabled”.
February 25, 2018 at 17:57 in reply to: Trouble debugging sample kernel module (RPi 1 + J-Link via JTAG) #20257maiorfiParticipantI tried with both 500KHz and 100KHz, but with no luck.
You can find gdb and ocd session logs as attachments (for 500KHz session).
Thanks.
- This reply was modified 6 years, 9 months ago by maiorfi.
- This reply was modified 6 years, 9 months ago by maiorfi.
Attachments:
You must be logged in to view attached files.maiorfiParticipantHi. Could you share beta setup link as soon as available? Thanks 🙂
maiorfiParticipantGreat, thanks.
maiorfiParticipantHi. Any news about that?
Thanks!
-
AuthorPosts