Current Server Time: 04:25 (Central Europe)

#apertus IRC Channel Logs

2020/05/07

Timezone: UTC


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