|
2017-09-23
| ||
| 22:42 | • Closed ticket [186099eaa2]: We need to start thinking about implementing a boot loader. plus 3 other changes artifact: 0dcc5481a3 user: kc5tja | |
| 07:58 | • Verified ticket [186099eaa2]. artifact: 695b591948 user: kc5tja | |
|
2017-09-12
| ||
| 07:33 | • New ticket [186099eaa2]. artifact: 771ca7373b user: kc5tja | |
| Ticket Hash: | 186099eaa2deccd906d440c3eebc1f279c74f8d6 | ||
| Title: | We need to start thinking about implementing a boot loader. | ||
| Status: | Closed | Type: | Code_Defect |
| Severity: | Critical | Priority: | Immediate |
| Subsystem: | Resolution: | Open | |
| Last Modified: |
2017-09-23 22:42:40 7.71 years ago |
Created: |
2017-09-12 07:33:09 7.74 years ago |
| Version Found In: | |||
| User Comments: | ||||
kc5tja added on 2017-09-23 07:58:49:
Boot loader, at least initially, will come from the port of TIM. kc5tja added on 2017-09-23 22:42:40: DONE! Use the following TIM commands: .i .l addr,blk-start,blk-len .g addr blk-start can be 0 for "traditional" partitions/filesystems. blk-len implies the bootcode must exist in a single extent. addr will depend on the code being loaded. For demonstration at SVFIG, I've been using $15000, but it can be something else. E.g., if you load a 1KB boot block, it might look like this: .i .l 18000,0,400 .g 18000 | ||||