On Tue, Apr 29, 2014 at 1:31 PM, Jose Teixeira de Sousa <[email protected]> wrote: > Speaking of debug, what will be the strategy for mor1kx: >
I don't think this discussion belongs in the thread about the atomic operations, so I've changed the subject. > --debug stub or > -- adbg (this was giving problems the last time I tried, and although it > works with or1200 the adbg's RTL needs a lot of rewriting... just ask > Verilator why) > mor1kx has a debug port, it's not specifically tied to adbg, but that's likely what will be used. What problem did you experience and could you provide a testcase where it fails. What are the problems with verilator and adbg? > > We are sort of planning a Bluetooth Low energy chip using an open source > processor and LM32 appears a serious contender to mor1kx. OR1200 is out of > the question. LM32 is a nice implementation and it's smaller than mor1kx, apart from that they are pretty much comparable in the 'baremetal' niche. mor1kx has some 'cool' features (and more coming) that LM32 lacks, but you might not need or be interested in them. What speaks in OpenRISC favor is IMO a stronger eco-system around it. Stefan _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
