Bug 303 - define peripheral set for 180nm ASIC
Summary: define peripheral set for 180nm ASIC
Status: RESOLVED DUPLICATE of bug 304
Alias: None
Product: Libre-SOC's first SoC
Classification: Unclassified
Component: Source Code (show other bugs)
Version: unspecified
Hardware: PC Linux
: --- enhancement
Assignee: Luke Kenneth Casson Leighton
URL:
Depends on:
Blocks:
 
Reported: 2020-05-07 13:44 BST by Luke Kenneth Casson Leighton
Modified: 2020-09-25 12:50 BST (History)
1 user (show)

See Also:
NLnet milestone: ---
total budget (EUR) for completion of task and all subtasks: 0
budget (EUR) for this task, excluding subtasks' budget: 0
parent task for budget allocation:
child tasks for budget allocation:
The table of payments (in EUR) for this task; TOML format:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Luke Kenneth Casson Leighton 2020-05-07 13:44:14 BST 
we need to define a peripheral set for the ASIC, create a page
(and use the peripheral / pinmux generator to describe it)
Comment 1 Luke Kenneth Casson Leighton 2020-05-12 13:11:08 BST 
yehowshua i added a stub/starting-point ls180

https://git.libre-soc.org/?p=pinmux.git;a=blob;f=src/spec/ls180.py;h=77c5f1f7f7923cb8292499bac189ff1ce8f3b6ff;hb=aca6d68a6159136fe1f36c6430e2ffd07da13e8c

also added a stub / dummy LPC function:
https://git.libre-soc.org/?p=pinmux.git;a=blob;f=src/spec/pinfunctions.py;h=e46be8d114f00bbf571092c4e7a9ec5ece39d04b;hb=aca6d68a6159136fe1f36c6430e2ffd07da13e8c#l52

it will need its pin naming correcting, and also in ls180.py everything
including LPC moving to a single column.

we need to move quickly on this because Rudi is waiting for us
to communicate back to him the required peripheral set, and he
is experienced enough to know that we are well beyond the industry
standard time for making these decisions.
Comment 2 Luke Kenneth Casson Leighton 2020-05-12 13:12:39 BST 
whoops how did we end up creating 2 bugreports, #304 and #303?

*** This bug has been marked as a duplicate of bug 304 ***