#2598 assigned defect

generic_or1k doesn't properly initalize the CPU/System

Reported by: Jakob Viketoft Owned by: Needs Funding
Priority: normal Milestone: Indefinite
Component: bsps Version: 4.11
Severity: normal Keywords:
Cc: Blocked By:
Blocking:

Description

The start.S file doesn't put the CPU/System into a known state at boot (as it should) and subsequent loads of applications require power cycling to start properly. Both the start.S file in generic_or1k and the entangled or1k-exception-handler-low.S in cpukit use hardcoded values for registers and their bits, making the assembly code unnecessarily hard to decipher.

Change History (4)

comment:1 Changed on Feb 20, 2016 at 9:40:56 PM by Jakob Viketoft

There is also no information readily available as to what exception has been hit if there's no specific handler installed for that exception. It should at least print the exception number and (when enabled) the exception stack frame.

comment:2 Changed on Feb 20, 2016 at 10:20:22 PM by Gedare Bloom

Milestone: 4.114.11.1
Version: 4.104.11

comment:3 Changed on Jan 26, 2017 at 7:16:00 AM by Sebastian Huber

Milestone: 4.11.14.11.2

comment:4 Changed on Feb 15, 2017 at 1:37:51 PM by Sebastian Huber

Milestone: 4.11.2Indefinite
Owner: set to Needs Funding
Status: newassigned
Note: See TracTickets for help on using tickets.