Current Server Time: 22:24 (Central Europe)

#apertus IRC Channel Logs

2020/05/07

Timezone: UTC


03:17
mumptai_
joined the channel
03:21
mumptai
left the channel
04:45
Bertl
off to bed now ... have a good one everyone!
04:45
Bertl
changed nick to: Bertl_zZ
06:17
BAndiT1983|away
changed nick to: BAndiT1983
06:30
metal_dent[m]
Morning
06:44
BAndiT1983
hi
06:44
BAndiT1983
metal_dent[m]: how is it going?
06:59
BAndiT1983
changed nick to: BAndiT1983|away
07:01
BAndiT1983|away
changed nick to: BAndiT1983
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
07:12
metal_dent[m]
and referring the articles with you sent
07:15
BAndiT1983
do you see the search bar at the top?
07:16
metal_dent[m]
yes
07:16
BAndiT1983
try to enter apertus there, you should see some interesting entries
07:17
metal_dent[m]
the logo!
07:20
BAndiT1983
are you at the position of any part?
07:20
BAndiT1983
i mean in the hexdump for example
07:21
metal_dent[m]
what do you mean?
07:21
metal_dent[m]
i'm looking at the apertus_text
07:24
BAndiT1983
open the tab hexdump
07:24
metal_dent[m]
yes, i did
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
07:25
BAndiT1983
which address do you have there?
07:28
metal_dent[m]
which slider?
07:29
BAndiT1983
when you open the file you have a dialog before entering the big UI
07:29
BAndiT1983
there are analysis settings
07:34
metal_dent[m]
"aaaa" is auto-analysis experimental
07:34
metal_dent[m]
"aaa" is auto-analysis
07:36
BAndiT1983
i use the experimental one, has a bit more info
07:37
BAndiT1983
but back to the topic, which adress have you got for the apertus text and what is the first entry
07:37
metal_dent[m]
okay, last time i selected "aaa"
07:38
metal_dent[m]
address : 0x00000000bfc0000
07:38
metal_dent[m]
entry : 03
07:38
BAndiT1983
nope
07:38
BAndiT1983
0xBFC00000 cannot be, as it's rather important address, have you looked at the PIC32 memory map yet?
07:39
BAndiT1983
e.g. http://ww1.microchip.com/downloads/en/DeviceDoc/60001214a.pdf -> page 13
07:39
BAndiT1983
but i would suggest to grab the big datasheet for pic32mz2048ecg100
07:40
metal_dent[m]
okay, will find that
07:42
metal_dent[m]
what address do you have?
07:42
BAndiT1983
but you can also see the address in the graphical representation of sections, i mean the big mulit-color bars
07:42
BAndiT1983
it's starting with 0x9D0 ;) guess why
07:43
metal_dent[m]
program flash..?
07:43
BAndiT1983
yes, very good
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
07:44
BAndiT1983
and firmware is solely in program flash
07:45
metal_dent[m]
okay
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
07:47
metal_dent[m]
it's 0x9d0 for me too, guess i was looking at some other section
07:47
BAndiT1983
and which address do you see for the logo text?
07:49
metal_dent[m]
you mean apertus_text, right? it's starting from 0x9d012b00
07:52
BAndiT1983
ok, slightly different which is expected, what is the first entry?
07:52
metal_dent[m]
d6
07:53
metal_dent[m]
what's your full address?
07:53
BAndiT1983
0x9D012F89
07:53
BAndiT1983
what does D6 tells us?
07:53
BAndiT1983
*tell
07:55
metal_dent[m]
the size which is specified in the header...? d6 is 214 so the width
07:56
BAndiT1983
great! now you should know how to search and verify that you have the right data there
07:56
BAndiT1983
another way is to inspect the .map file in the build folder of the dedicated project
07:56
metal_dent[m]
yes, it's interesting
07:56
BAndiT1983
but i like r2 more as i can see advanced infos there
07:56
metal_dent[m]
okay, i'll open that too
07:57
BAndiT1983
dashboard is also interesting, as it shows which target we have and how many things are involved
07:58
metal_dent[m]
yes, i compared the dashboards for firmware and BL yesterday
08:09
BAndiT1983
metal_dent[m]: have you looked at the procdefs.ld in common folder yet?
08:11
metal_dent[m]
no
08:13
BAndiT1983
then please do, have you seen such comment in the code somewhere? -> // Defined in procdefs.ld
08:14
metal_dent[m]
in the main file
08:14
BAndiT1983
alright, now check the position in the procdefs.ld and cross-check what cutter shows you
08:15
BAndiT1983
also the size is important!
08:31
BAndiT1983
you can also check it in .map, as infos are there mostly packed together
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
08:40
BAndiT1983
but which memory location is the comment describing?
08:42
metal_dent[m]
i meant this one -> https://github.com/MetalDent/AXIOM-Remote/blob/dev/Common/procdefs.ld#L81
08:44
BAndiT1983
no, the comment describes some other location, it's exactly above the line it comments
08:46
metal_dent[m]
you mean 0x800000..? but isn't this the length?
08:48
BAndiT1983
line 81 is not the section of the comment
08:48
metal_dent[m]
okay i got it (i think) it starts from 0x9FC00000 but 0x1000 are blank/empty...?
08:49
BAndiT1983
0x9fc.... is 0xBFC....., but it's not what i mean
08:49
BAndiT1983
what is the line below the comment saying?
08:50
metal_dent[m]
kseg0_program_mem
08:51
BAndiT1983
no, how do you conclude that?
08:52
BAndiT1983
i mean tihs comment -> // Defined in procdefs.ld
08:55
metal_dent[m]
Ohh, I was looking in the procdefs.ld
08:56
BAndiT1983
procdefs.ld has many comments, so it would be hard to pinpoint something ;)
08:56
WalterZimmermann
left the channel
08:56
pratyush[m]
left the channel
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
08:57
metal_dent[m]
that's what i was thinking, i thought you were talking about that file
08:57
metal_dent[m]
':D
09:01
WalterZimmermann
joined the channel
09:01
pratyush[m]
joined the channel
09:26
BAndiT1983
metal_dent[m]: and, have you found it?
09:37
madonius
left the channel
09:41
madonius
joined the channel
10:01
metal_dent[m]
yes, I found the line which you were saying; sorry i took a little break
10:02
BAndiT1983
no problem
10:02
BAndiT1983
have you also found the corresponding line in the procdefs.ld?
10:04
metal_dent[m]
yes, the framebuffer_mem
10:05
BAndiT1983
yes, framebuffer_mem is the origin of it
10:06
BAndiT1983
do you know why framebuffer was defined in the linker script?
10:08
metal_dent[m]
maybe because it should be placed in the core..
10:10
BAndiT1983
which core?
10:10
metal_dent[m]
memory
10:11
BAndiT1983
everything is placed in flash memory on the MCU, but why the definition of framebuffer in the script?
10:12
metal_dent[m]
i don't know
10:12
BAndiT1983
then try to guess
10:13
BAndiT1983
and compare the location of the framebuffer to the memory map of the pic32
10:13
metal_dent[m]
it's in the RAM
10:14
BAndiT1983
yes, right
10:15
BAndiT1983
and the purpose of definition? it could also be defined in code, but why is it defined in linker script instead?
10:21
metal_dent[m]
i think because the address allocated to the framebuffer should not be occupied by anything else
10:23
BAndiT1983
also almost true, just slightly different: to have a fixed layout, but it's not the only reason for this decision
10:25
metal_dent[m]
okay so what are the other reasons for this?
10:26
BAndiT1983
remember what we have discussed about the role of bootloader and it's interaction with firmware?
10:30
metal_dent[m]
yes..
10:37
metal_dent[m]
is taking a lunch break .... will be back in around 30 mins
10:39
BAndiT1983
lunch? it's almost lunch time here, but you have like dinner time in your time zone, right?
10:39
preetimenghwani[
left the channel
10:39
MarkVandenBorre[
left the channel
10:39
elkos
left the channel
10:39
pratyush[m]
left the channel
10:39
promach3
left the channel
10:39
metal_dent[m]
left the channel
10:39
shashwat1999[m]
left the channel
10:39
aleb
left the channel
10:39
sergio__[m]
left the channel
10:39
bluez_[m]
left the channel
10:39
PhilippeJadin[m]
left the channel
10:40
parasew[m]
left the channel
10:40
apurvanandan[m]
left the channel
10:40
ashok_singh[m]
left the channel
10:40
RexOrMatrix[m]
left the channel
10:40
abeljj[m]
left the channel
10:40
WalterZimmermann
left the channel
10:53
metal_dent[m]
joined the channel
10:54
apurvanandan[m]
joined the channel
10:58
metal_dent[m]
No, it was 15:00 here, little late for lunch but we had a puja today at home
10:59
BAndiT1983
ah, right, it's difference of 3:30, forgot about that 5:30 from UTC
10:59
elkos
joined the channel
10:59
aleb
joined the channel
10:59
ashok_singh[m]
joined the channel
10:59
preetimenghwani[
joined the channel
10:59
sergio__[m]
joined the channel
10:59
bluez_[m]
joined the channel
10:59
WalterZimmermann
joined the channel
10:59
PhilippeJadin[m]
joined the channel
10:59
pratyush[m]
joined the channel
11:04
metal_dent[m]
yes
11:15
promach3
joined the channel
11:15
parasew[m]
joined the channel
11:15
shashwat1999[m]
joined the channel
11:15
MarkVandenBorre[
joined the channel
11:15
abeljj[m]
joined the channel
11:15
RexOrMatrix[m]
joined the channel
11:39
BAndiT1983
metal_dent[m]: my question is still there ;)
11:39
BAndiT1983
(11:26:37) BAndiT1983: remember what we have discussed about the role of bootloader and it's interaction with firmware?
11:50
metal_dent[m]
you mean about the triggering of firmware using BL and storing of various presets in the BL and flash?
11:53
BAndiT1983
what do you want to store in BL?
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
12:10
BAndiT1983
flashing firmware is only one task of the BL, but what was discussed about the communication fo BL and firmware?
12:12
metal_dent[m]
i don't remember, i'm searching through the logs
12:13
BAndiT1983
hint: BIOS
12:13
metal_dent[m]
yes, just got it
12:14
metal_dent[m]
sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/woRfMMcbddKMRVnCPNvjqlYC >
12:16
BAndiT1983
yep, now you should know the reason for fixed location, right?
12:22
metal_dent[m]
so that both BL and firmware can access it..?
12:23
BAndiT1983
exactly
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
12:25
BAndiT1983
there are still some questions regarding the linking not solved, but i have postponed them back then
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?
12:28
BAndiT1983
sounds good! please do
13:01
Bertl_zZ
changed nick to: Bertl
13:01
Bertl
morning folks!
13:03
se6ast1an
good day
13:12
BAndiT1983
metal_dent[m]: and now Bertl will show us the quickest way to find the sections and sizes with objdump
13:14
Bertl
objdump -h ?
13:16
Bertl
(that's not -h for help, that is for displaying the section headers :)
13:31
metal_dent[m]
BAndiT1983: the progress so far -> https://github.com/MetalDent/GSoC-Progress
13:53
BAndiT1983
looks good
15:35
aombk
left the channel
15:47
aombk
joined the channel
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
16:34
se6ast1an
eg. visualizer drawing the sidebar with home icon, etc.
16:35
se6ast1an
can be all local for now just for you, you can still pick what might be interesting later on
16:37
metal_dent[m]
sure! should I write blog post every week or after every period?
16:40
BAndiT1983
i request a youtube video ;) just joking
16:41
metal_dent[m]
can do that but you'll get tired of my blabbering XD
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
16:46
metal_dent[m]
Supragya?
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
16:47
se6ast1an
yes, from the terminal title it must have been him indeed
16:47
se6ast1an
such a video really helps new contributors overcome the first steps
16:48
BAndiT1983
it was Supragya for sure
16:48
BAndiT1983
he also says it at the end ;)
16:49
metal_dent[m]
alright! I'll probably write one when the contribution periods starts and also try making a video like this
16:50
Bertl
make your own video (if you make one) i.e. do not try to copy somebody else :)
16:52
metal_dent[m]
ofc, and how can I copy a video? can refer one for the concept ;)
16:53
BAndiT1983
you can use AI to replace the terminal text with axiom remote ones :D
16:54
se6ast1an
https://www.youtube.com/watch?v=wCsO56kWwTc
16:57
sergio__[m]
left the channel
16:57
WalterZimmermann
left the channel
16:57
pratyush[m]
left the channel
17:04
metal_dent[m]
true!
17:38
se6ast1an
metal_dent[m]: if you need a small sidequest you could manually fix the home icon inperfections from the conversion process
17:40
BAndiT1983
it's very tedious and requires a lot of bit mapping
17:40
BAndiT1983
isn't it easier to fix the ocnversion?
17:40
BAndiT1983
*conversion
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
17:50
metal_dent[m]
-> https://github.com/MetalDent/AXIOM-Remote/blob/dev/Firmware/Media/Icons/convert.sh#L12
17:50
BAndiT1983
ah, interesting, do you have comparison images?
17:50
BAndiT1983
off for a walk for a moment, will be back later
17:50
BAndiT1983
changed nick to: BAndiT1983|away
17:51
metal_dent[m]
no, let me take
17:53
abeljj[m]
left the channel
17:53
RexOrMatrix[m]
left the channel
17:57
metal_dent[m]
without -> https://pasteboard.co/J7ikLTz.png
17:57
metal_dent[m]
with -> https://pasteboard.co/J7il0Fs.png
17:58
se6ast1an
indeed much better!
17:58
se6ast1an
please commit the updated scripts and icons
17:59
metal_dent[m]
okay
18:00
se6ast1an
how is your progress going with https://lab.apertus.org/T1172 ?
18:01
metal_dent[m]
no progress yet, will work on this from tomorrow ; sorry kinda forgot about that ':D
18:02
se6ast1an
the lab can help with "task management" :9
18:03
se6ast1an
also the icons still draw a random color
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
18:04
se6ast1an
but the bug is not yet listed in the task anywhere so that would also be a good idea
18:13
metal_dent[m]
yes yes, will look into that too ; created a task for now
18:21
metal_dent[m]
off to bed now... good night!
18:48
se6ast1an
good night
19:19
BAndiT1983|away
changed nick to: BAndiT1983
21:30
Bertl
off for now ... bbl
21:30
Bertl
changed nick to: Bertl_oO
21:42
BAndiT1983
changed nick to: BAndiT1983|away
22:12
se6ast1an
off to bed, good night