Studying GPIO & The Config String ⚠ Click here to regain focus ⚠
?
?

Keyboard Navigation

Global Keys

W, A, P / S, D, N Jump to previous / next marker
t / T Toggle theatre / SUPERtheatre mode
z Toggle filter mode V Revert filter to original state

Menu toggling

q Quotes r References f Filter c Credits

Movement

a
w
s
d
h j k l


Quotes and References Menus

Enter Jump to timecode

Quotes, References and Credits Menus

o Open URL (in new tab)

Filter Menu

x, Space Toggle category and focus next
X, ShiftSpace Toggle category and focus previous
v Invert topics / media as per focus

Credits Menu

Enter Open URL (in new tab)
0:08Recap some off-stream work looking for the definition of __start()1
0:08Recap some off-stream work looking for the definition of __start()1
0:08Recap some off-stream work looking for the definition of __start()1
1:38Recap what we discovered about handle_m_time_interrupt() last time
📖
1:38Recap what we discovered about handle_m_time_interrupt() last time
📖
1:38Recap what we discovered about handle_m_time_interrupt() last time
📖
3:59TODO: Dive into __start + entry.S
🖌
3:59TODO: Dive into __start + entry.S
🖌
3:59TODO: Dive into __start + entry.S
🖌
5:05Set the stage for the day
5:05Set the stage for the day
5:05Set the stage for the day
6:13hossein1387 I had a look at link.lds (located at freedom-e-sdk/bsp/env/freedom-e300-hifive1 which provides stack size and other stuff) but it does call _start
🗪
6:13hossein1387 I had a look at link.lds (located at freedom-e-sdk/bsp/env/freedom-e300-hifive1 which provides stack size and other stuff) but it does call _start
🗪
6:13hossein1387 I had a look at link.lds (located at freedom-e-sdk/bsp/env/freedom-e300-hifive1 which provides stack size and other stuff) but it does call _start
🗪
6:54Consult link.lds
📖
6:54Consult link.lds
📖
6:54Consult link.lds
📖
8:44Come to understand handle_m_ext_interrupt()2
📖
8:44Come to understand handle_m_ext_interrupt()2
📖
8:44Come to understand handle_m_ext_interrupt()2
📖
15:59Research the GPIO3
📖
15:59Research the GPIO3
📖
15:59Research the GPIO3
📖
17:24Consult the GPIO pin layout4
📖
17:24Consult the GPIO pin layout4
📖
17:24Consult the GPIO pin layout4
📖
19:31Determine to understand the GPIO_REG macro
📖
19:31Determine to understand the GPIO_REG macro
📖
19:31Determine to understand the GPIO_REG macro
📖
21:37Point out the GPIO pins on the HiFive1
21:37Point out the GPIO pins on the HiFive1
21:37Point out the GPIO pins on the HiFive1
23:10Continue reading env/hifive1.h
📖
23:10Continue reading env/hifive1.h
📖
23:10Continue reading env/hifive1.h
📖
25:05Find the GPIO_REG() and _REG32() macros in env/freedom-e300-hifive1/platform.h
📖
25:05Find the GPIO_REG() and _REG32() macros in env/freedom-e300-hifive1/platform.h
📖
25:05Find the GPIO_REG() and _REG32() macros in env/freedom-e300-hifive1/platform.h
📖
27:09Read about the General Purpose Input/Output Controller (GPIO)5
📖
27:09Read about the General Purpose Input/Output Controller (GPIO)5
📖
27:09Read about the General Purpose Input/Output Controller (GPIO)5
📖
29:47Read the Machine Configuration Description6
📖
29:47Read the Machine Configuration Description6
📖
29:47Read the Machine Configuration Description6
📖
37:28hossein1387 From what I know, device tree is the way to tell Linux / OS what hardware we are using
🗪
37:28hossein1387 From what I know, device tree is the way to tell Linux / OS what hardware we are using
🗪
37:28hossein1387 From what I know, device tree is the way to tell Linux / OS what hardware we are using
🗪
38:12Read about Device Tree7
📖
38:12Read about Device Tree7
📖
38:12Read about Device Tree7
📖
43:41Continue reading about the Configuration String8
📖
43:41Continue reading about the Configuration String8
📖
43:41Continue reading about the Configuration String8
📖
45:18Consult the table detailing the overall memory map of the E3 Coreplex9
45:18Consult the table detailing the overall memory map of the E3 Coreplex9
45:18Consult the table detailing the overall memory map of the E3 Coreplex9
45:55Enable print_instructions() to print the information following the configuration string address
45:55Enable print_instructions() to print the information following the configuration string address
45:55Enable print_instructions() to print the information following the configuration string address
51:13Continue studying the GPIO10
📖
51:13Continue studying the GPIO10
📖
51:13Continue studying the GPIO10
📖
54:21Using XOR to invert
🖌
54:21Using XOR to invert
🖌
54:21Using XOR to invert
🖌
56:57Briefly consult the diagram detailing the structure of a single GPIO Pin with Control Registers before reading on about the GPIO11
📖
56:57Briefly consult the diagram detailing the structure of a single GPIO Pin with Control Registers before reading on about the GPIO11
📖
56:57Briefly consult the diagram detailing the structure of a single GPIO Pin with Control Registers before reading on about the GPIO11
📖
1:01:56GPIO
🖌
1:01:56GPIO
🖌
1:01:56GPIO
🖌
1:03:52We are out of time for today
1:03:52We are out of time for today
1:03:52We are out of time for today
1:05:32hossein1387 I tried to print the config
🗪
1:05:32hossein1387 I tried to print the config
🗪
1:05:32hossein1387 I tried to print the config
🗪
1:05:53hossein1387 It didn't work out
🗪
1:05:53hossein1387 It didn't work out
🗪
1:05:53hossein1387 It didn't work out
🗪
1:06:33hossein1387 It's all garbage
🗪
1:06:33hossein1387 It's all garbage
🗪
1:06:33hossein1387 It's all garbage
🗪
1:07:01hossein1387 { model = "SiFive,FE310G-0000-Z0"; compatible = "sifive,fe300"; /include/ 0x20004;};
🗪
1:07:01hossein1387 { model = "SiFive,FE310G-0000-Z0"; compatible = "sifive,fe300"; /include/ 0x20004;};
🗪
1:07:01hossein1387 { model = "SiFive,FE310G-0000-Z0"; compatible = "sifive,fe300"; /include/ 0x20004;};
🗪
1:08:42hossein1387 Can you also try? I want to know if there is a serial number or something
🗪
1:08:42hossein1387 Can you also try? I want to know if there is a serial number or something
🗪
1:08:42hossein1387 Can you also try? I want to know if there is a serial number or something
🗪
1:09:11Wind it down
1:09:11Wind it down
1:09:11Wind it down