Current Server Time: 22:50 (Central Europe)

#apertus IRC Channel Logs

2020/05/07

Timezone: UTC

1
03:17
mumptai_
joined the channel
2
03:21
mumptai
left the channel
3
04:45
Bertl
off to bed now ... have a good one everyone!
4
04:45
Bertl
changed nick to: Bertl_zZ
5
06:17
BAndiT1983|away
changed nick to: BAndiT1983
6
06:30
metal_dent[m]
Morning
7
06:44
BAndiT1983
hi
8
06:44
BAndiT1983
metal_dent[m]: how is it going?
9
06:59
BAndiT1983
changed nick to: BAndiT1983|away
10
07:01
BAndiT1983|away
changed nick to: BAndiT1983
11
07:12
metal_dent[m]
hi, yesterday I generated both the .elf files for firmware and BL and inspected with cutter but as I'm using it for the first time so I'm playing around it
12
07:12
metal_dent[m]
and referring the articles with you sent
13
07:15
BAndiT1983
do you see the search bar at the top?
14
07:16
metal_dent[m]
yes
15
07:16
BAndiT1983
try to enter apertus there, you should see some interesting entries
16
07:17
metal_dent[m]
the logo!
17
07:20
BAndiT1983
are you at the position of any part?
18
07:20
BAndiT1983
i mean in the hexdump for example
19
07:21
metal_dent[m]
what do you mean?
20
07:21
metal_dent[m]
i'm looking at the apertus_text
21
07:24
BAndiT1983
open the tab hexdump
22
07:24
metal_dent[m]
yes, i did
23
07:25
BAndiT1983
also when starting the analysis it's always good to pull the slider 1 position to the right for "aaaa" auto-analysis, it give a bit more info
24
07:25
BAndiT1983
which address do you have there?
25
07:28
metal_dent[m]
which slider?
26
07:29
BAndiT1983
when you open the file you have a dialog before entering the big UI
27
07:29
BAndiT1983
there are analysis settings
28
07:34
metal_dent[m]
"aaaa" is auto-analysis experimental
29
07:34
metal_dent[m]
"aaa" is auto-analysis
30
07:36
BAndiT1983
i use the experimental one, has a bit more info
31
07:37
BAndiT1983
but back to the topic, which adress have you got for the apertus text and what is the first entry
32
07:37
metal_dent[m]
okay, last time i selected "aaa"
33
07:38
metal_dent[m]
address : 0x00000000bfc0000
34
07:38
metal_dent[m]
entry : 03
35
07:38
BAndiT1983
nope
36
07:38
BAndiT1983
0xBFC00000 cannot be, as it's rather important address, have you looked at the PIC32 memory map yet?
37
07:39
BAndiT1983
e.g. http://ww1.microchip.com/downloads/en/DeviceDoc/60001214a.pdf -> page 13
38
07:39
BAndiT1983
but i would suggest to grab the big datasheet for pic32mz2048ecg100
39
07:40
metal_dent[m]
okay, will find that
40
07:42
metal_dent[m]
what address do you have?
41
07:42
BAndiT1983
but you can also see the address in the graphical representation of sections, i mean the big mulit-color bars
42
07:42
BAndiT1983
it's starting with 0x9D0 ;) guess why
43
07:43
metal_dent[m]
program flash..?
44
07:43
BAndiT1983
yes, very good
45
07:44
BAndiT1983
you can see in the memory map, that PIC32 flash is split in multiple parts, won't go deeper for now, but boot flash is used for bootloader, although it's not required and you could place bootloader in the program flash also, it's only machine code
46
07:44
BAndiT1983
and firmware is solely in program flash
47
07:45
metal_dent[m]
okay
48
07:45
BAndiT1983
this also worked in previous tests when i've had merged file for flashing, the jump from bootloader to program was working
49
07:47
metal_dent[m]
it's 0x9d0 for me too, guess i was looking at some other section
50
07:47
BAndiT1983
and which address do you see for the logo text?
51
07:49
metal_dent[m]
you mean apertus_text, right? it's starting from 0x9d012b00
52
07:52
BAndiT1983
ok, slightly different which is expected, what is the first entry?
53
07:52
metal_dent[m]
d6
54
07:53
metal_dent[m]
what's your full address?
55
07:53
BAndiT1983
0x9D012F89
56
07:53
BAndiT1983
what does D6 tells us?
57
07:53
BAndiT1983
*tell
58
07:55
metal_dent[m]
the size which is specified in the header...? d6 is 214 so the width
59
07:56
BAndiT1983
great! now you should know how to search and verify that you have the right data there
60
07:56
BAndiT1983
another way is to inspect the .map file in the build folder of the dedicated project
61
07:56
metal_dent[m]
yes, it's interesting
62
07:56
BAndiT1983
but i like r2 more as i can see advanced infos there
63
07:56
metal_dent[m]
okay, i'll open that too
64
07:57
BAndiT1983
dashboard is also interesting, as it shows which target we have and how many things are involved
65
07:58
metal_dent[m]
yes, i compared the dashboards for firmware and BL yesterday
66
08:09
BAndiT1983
metal_dent[m]: have you looked at the procdefs.ld in common folder yet?
67
08:11
metal_dent[m]
no
68
08:13
BAndiT1983
then please do, have you seen such comment in the code somewhere? -> // Defined in procdefs.ld
69
08:14
metal_dent[m]
in the main file
70
08:14
BAndiT1983
alright, now check the position in the procdefs.ld and cross-check what cutter shows you
71
08:15
BAndiT1983
also the size is important!
72
08:31
BAndiT1983
you can also check it in .map, as infos are there mostly packed together
73
08:36
metal_dent[m]
for the BL the starting address in procdefs is 0x9FC01000 and the .elf file also starts from that address, before that all the entries are ff
74
08:40
BAndiT1983
but which memory location is the comment describing?
75
08:42
metal_dent[m]
i meant this one -> https://github.com/MetalDent/AXIOM-Remote/blob/dev/Common/procdefs.ld#L81
76
08:44
BAndiT1983
no, the comment describes some other location, it's exactly above the line it comments
77
08:46
metal_dent[m]
you mean 0x800000..? but isn't this the length?
78
08:48
BAndiT1983
line 81 is not the section of the comment
79
08:48
metal_dent[m]
okay i got it (i think) it starts from 0x9FC00000 but 0x1000 are blank/empty...?
80
08:49
BAndiT1983
0x9fc.... is 0xBFC....., but it's not what i mean
81
08:49
BAndiT1983
what is the line below the comment saying?
82
08:50
metal_dent[m]
kseg0_program_mem
83
08:51
BAndiT1983
no, how do you conclude that?
84
08:52
BAndiT1983
i mean tihs comment -> // Defined in procdefs.ld
85
08:55
metal_dent[m]
Ohh, I was looking in the procdefs.ld
86
08:56
BAndiT1983
procdefs.ld has many comments, so it would be hard to pinpoint something ;)
87
08:56
WalterZimmermann
left the channel
88
08:56
pratyush[m]
left the channel
89
08:56
BAndiT1983
not all are up to date there, as i've tested quite a lot back then and also bothered Bertl at the mentors summit :D
90
08:57
metal_dent[m]
that's what i was thinking, i thought you were talking about that file
91
08:57
metal_dent[m]
':D
92
09:01
WalterZimmermann
joined the channel
93
09:01
pratyush[m]
joined the channel
94
09:26
BAndiT1983
metal_dent[m]: and, have you found it?
95
09:37
madonius
left the channel
96
09:41
madonius
joined the channel
97
10:01
metal_dent[m]
yes, I found the line which you were saying; sorry i took a little break
98
10:02
BAndiT1983
no problem
99
10:02
BAndiT1983
have you also found the corresponding line in the procdefs.ld?
100
10:04
metal_dent[m]
yes, the framebuffer_mem
101
10:05
BAndiT1983
yes, framebuffer_mem is the origin of it
102
10:06
BAndiT1983
do you know why framebuffer was defined in the linker script?
103
10:08
metal_dent[m]
maybe because it should be placed in the core..
104
10:10
BAndiT1983
which core?
105
10:10
metal_dent[m]
memory
106
10:11
BAndiT1983
everything is placed in flash memory on the MCU, but why the definition of framebuffer in the script?
107
10:12
metal_dent[m]
i don't know
108
10:12
BAndiT1983
then try to guess
109
10:13
BAndiT1983
and compare the location of the framebuffer to the memory map of the pic32
110
10:13
metal_dent[m]
it's in the RAM
111
10:14
BAndiT1983
yes, right
112
10:15
BAndiT1983
and the purpose of definition? it could also be defined in code, but why is it defined in linker script instead?
113
10:21
metal_dent[m]
i think because the address allocated to the framebuffer should not be occupied by anything else
114
10:23
BAndiT1983
also almost true, just slightly different: to have a fixed layout, but it's not the only reason for this decision
115
10:25
metal_dent[m]
okay so what are the other reasons for this?
116
10:26
BAndiT1983
remember what we have discussed about the role of bootloader and it's interaction with firmware?
117
10:30
metal_dent[m]
yes..
118
10:37
metal_dent[m]
is taking a lunch break .... will be back in around 30 mins
119
10:39
BAndiT1983
lunch? it's almost lunch time here, but you have like dinner time in your time zone, right?
120
10:39
preetimenghwani[
left the channel
121
10:39
MarkVandenBorre[
left the channel
122
10:39
elkos
left the channel
123
10:39
pratyush[m]
left the channel
124
10:39
promach3
left the channel
125
10:39
metal_dent[m]
left the channel
126
10:39
shashwat1999[m]
left the channel
127
10:39
aleb
left the channel
128
10:39
sergio__[m]
left the channel
129
10:39
bluez_[m]
left the channel
130
10:39
PhilippeJadin[m]
left the channel
131
10:40
parasew[m]
left the channel
132
10:40
apurvanandan[m]
left the channel
133
10:40
ashok_singh[m]
left the channel
134
10:40
RexOrMatrix[m]
left the channel
135
10:40
abeljj[m]
left the channel
136
10:40
WalterZimmermann
left the channel
137
10:53
metal_dent[m]
joined the channel
138
10:54
apurvanandan[m]
joined the channel
139
10:58
metal_dent[m]
No, it was 15:00 here, little late for lunch but we had a puja today at home
140
10:59
BAndiT1983
ah, right, it's difference of 3:30, forgot about that 5:30 from UTC
141
10:59
elkos
joined the channel
142
10:59
aleb
joined the channel
143
10:59
ashok_singh[m]
joined the channel
144
10:59
preetimenghwani[
joined the channel
145
10:59
sergio__[m]
joined the channel
146
10:59
bluez_[m]
joined the channel
147
10:59
WalterZimmermann
joined the channel
148
10:59
PhilippeJadin[m]
joined the channel
149
10:59
pratyush[m]
joined the channel
150
11:04
metal_dent[m]
yes
151
11:15
promach3
joined the channel
152
11:15
parasew[m]
joined the channel
153
11:15
shashwat1999[m]
joined the channel
154
11:15
MarkVandenBorre[
joined the channel
155
11:15
abeljj[m]
joined the channel
156
11:15
RexOrMatrix[m]
joined the channel
157
11:39
BAndiT1983
metal_dent[m]: my question is still there ;)
158
11:39
BAndiT1983
(11:26:37) BAndiT1983: remember what we have discussed about the role of bootloader and it's interaction with firmware?
159
11:50
metal_dent[m]
you mean about the triggering of firmware using BL and storing of various presets in the BL and flash?
160
11:53
BAndiT1983
what do you want to store in BL?
161
12:07
metal_dent[m]
not store (I used the wrong term) we need a proper communication b/w BL and firmware so that we can load/update it easily using the BL
162
12:10
BAndiT1983
flashing firmware is only one task of the BL, but what was discussed about the communication fo BL and firmware?
163
12:12
metal_dent[m]
i don't remember, i'm searching through the logs
164
12:13
BAndiT1983
hint: BIOS
165
12:13
metal_dent[m]
yes, just got it
166
12:14
metal_dent[m]
sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/woRfMMcbddKMRVnCPNvjqlYC >
167
12:16
BAndiT1983
yep, now you should know the reason for fixed location, right?
168
12:22
metal_dent[m]
so that both BL and firmware can access it..?
169
12:23
BAndiT1983
exactly
170
12:24
BAndiT1983
you can define the fixed location in memory in the code, but this would be required in both projects, which is not preferable, if some memory layout changes both have to be updated
171
12:25
BAndiT1983
there are still some questions regarding the linking not solved, but i have postponed them back then
172
12:27
metal_dent[m]
okay, btw I was thinking of making a md file to track whatever I do/learn everyday, I'll share the link with you, is that okay?
173
12:28
BAndiT1983
sounds good! please do
174
13:01
Bertl_zZ
changed nick to: Bertl
175
13:01
Bertl
morning folks!
176
13:03
se6ast1an
good day
177
13:12
BAndiT1983
metal_dent[m]: and now Bertl will show us the quickest way to find the sections and sizes with objdump
178
13:14
Bertl
objdump -h ?
179
13:16
Bertl
(that's not -h for help, that is for displaying the section headers :)
180
13:31
metal_dent[m]
BAndiT1983: the progress so far -> https://github.com/MetalDent/GSoC-Progress
181
13:53
BAndiT1983
looks good
182
15:35
aombk
left the channel
183
15:47
aombk
joined the channel
184
16:34
se6ast1an
metal_dent[m]: btw. I would suggest to collect screenshots of your progress and achievements during GSoC, those might come in handy for a blog post or the final report at the end
185
16:34
se6ast1an
eg. visualizer drawing the sidebar with home icon, etc.
186
16:35
se6ast1an
can be all local for now just for you, you can still pick what might be interesting later on
187
16:37
metal_dent[m]
sure! should I write blog post every week or after every period?
188
16:40
BAndiT1983
i request a youtube video ;) just joking
189
16:41
metal_dent[m]
can do that but you'll get tired of my blabbering XD
190
16:45
se6ast1an
a video of setting up environment/git repo and compiling the source code would be a very cool thing btw, this is what a GSoC student created in 2018: https://www.youtube.com/watch?v=Rpq_ItPHFx8
191
16:46
metal_dent[m]
Supragya?
192
16:46
se6ast1an
<metal_dent[m]> sure! should I write blog post every week or after every period? <- whatever you feel comfortable with, I would like to have at least one at the end but if you are happy to write a few that would also be great
193
16:47
se6ast1an
yes, from the terminal title it must have been him indeed
194
16:47
se6ast1an
such a video really helps new contributors overcome the first steps
195
16:48
BAndiT1983
it was Supragya for sure
196
16:48
BAndiT1983
he also says it at the end ;)
197
16:49
metal_dent[m]
alright! I'll probably write one when the contribution periods starts and also try making a video like this
198
16:50
Bertl
make your own video (if you make one) i.e. do not try to copy somebody else :)
199
16:52
metal_dent[m]
ofc, and how can I copy a video? can refer one for the concept ;)
200
16:53
BAndiT1983
you can use AI to replace the terminal text with axiom remote ones :D
201
16:54
se6ast1an
https://www.youtube.com/watch?v=wCsO56kWwTc
202
16:57
sergio__[m]
left the channel
203
16:57
WalterZimmermann
left the channel
204
16:57
pratyush[m]
left the channel
205
17:04
metal_dent[m]
true!
206
17:38
se6ast1an
metal_dent[m]: if you need a small sidequest you could manually fix the home icon inperfections from the conversion process
207
17:40
BAndiT1983
it's very tedious and requires a lot of bit mapping
208
17:40
BAndiT1983
isn't it easier to fix the ocnversion?
209
17:40
BAndiT1983
*conversion
210
17:49
metal_dent[m]
yes, it's easier and last week I checked the conversion script and found that "-monochrome" is creating the problem
211
17:50
metal_dent[m]
-> https://github.com/MetalDent/AXIOM-Remote/blob/dev/Firmware/Media/Icons/convert.sh#L12
212
17:50
BAndiT1983
ah, interesting, do you have comparison images?
213
17:50
BAndiT1983
off for a walk for a moment, will be back later
214
17:50
BAndiT1983
changed nick to: BAndiT1983|away
215
17:51
metal_dent[m]
no, let me take
216
17:53
abeljj[m]
left the channel
217
17:53
RexOrMatrix[m]
left the channel
218
17:57
metal_dent[m]
without -> https://pasteboard.co/J7ikLTz.png
219
17:57
metal_dent[m]
with -> https://pasteboard.co/J7il0Fs.png
220
17:58
se6ast1an
indeed much better!
221
17:58
se6ast1an
please commit the updated scripts and icons
222
17:59
metal_dent[m]
okay
223
18:00
se6ast1an
how is your progress going with https://lab.apertus.org/T1172 ?
224
18:01
metal_dent[m]
no progress yet, will work on this from tomorrow ; sorry kinda forgot about that ':D
225
18:02
se6ast1an
the lab can help with "task management" :9
226
18:03
se6ast1an
also the icons still draw a random color
227
18:03
se6ast1an
Bertl gave you a hint for a fix already: http://irc.apertus.org/index.php?day=03&month=05&year=2020#126
228
18:04
se6ast1an
but the bug is not yet listed in the task anywhere so that would also be a good idea
229
18:13
metal_dent[m]
yes yes, will look into that too ; created a task for now
230
18:21
metal_dent[m]
off to bed now... good night!
231
18:48
se6ast1an
good night
232
19:19
BAndiT1983|away
changed nick to: BAndiT1983
233
21:30
Bertl
off for now ... bbl
234
21:30
Bertl
changed nick to: Bertl_oO
235
21:42
BAndiT1983
changed nick to: BAndiT1983|away
236
22:12
se6ast1an
off to bed, good night