| --- Log opened Sat May 07 00:00:55 2016 | ||
| shorne | wallento: If I have it break at a place after init, then it gets a bit further, but it seems libgloss never populates at trap handler. Just a _or1k_timer_interrupt_handler. | 03:59 |
|---|---|---|
| shorne | But.. I am wondering how breakpoints worked in or1ksim then..., mabye there is a sim function for it rather than simulating the hardware debug unit. | 04:00 |
| wallento | shorne: oh yeah, there are no exception handlers in baremetal | 04:22 |
| shorne | ok, I think its making more sense, actually in gdb sim you can load it up with 'target sim', you can also do some not so well documented stuff like 'target sim --trace-insn' to setup simulator debug | 04:45 |
| shorne | When I run my test then its easy to see where its getting into trouble, and its the missin exception handler setup | 04:45 |
| shorne | So... looks like I might have to get libgloss updated, double checking why its working find in or1ksim | 04:46 |
| shorne | I see, or1ksim uses the debug stop register (DST) setting TE (trap exception), meaning breakpoints trigger debug development interface | 06:13 |
| shorne | so cpu stalls and raises some flags, instead of executing the trap handler | 06:14 |
| shorne | s/DST/DSR/ | 06:24 |
| shorne | so a few options to get the sim working | 06:25 |
| shorne | 1. implement newlib trap handlers (but how would it work for non newlib builds?) | 06:25 |
| shorne | 2. implement / use the debug unit like or1ksim sim is doing | 06:26 |
| shorne | 3. get better idea from someone who knows more :) | 06:27 |
| olofk | shorne: I would have gone with option 3 :) | 10:37 |
| shorne | olofk: thats what I am thinking, I am looking at how other sims are handling breakpoints. Maybe I can get some ideas from there | 17:33 |
| --- Log closed Sun May 08 00:00:56 2016 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!