gaston1980 has quit [Quit: Konversation terminated!]
ChriChri_ has joined #linux-sunxi
tuxd3v has quit [Quit: Leaving]
Mangy_Dog has quit [Ping timeout: 240 seconds]
ChriChri has quit [Ping timeout: 268 seconds]
ldevulder__ has joined #linux-sunxi
ldevulder_ has quit [Ping timeout: 264 seconds]
NeuroScr has quit [Quit: NeuroScr]
sunshavi has quit [Remote host closed the connection]
megi has quit [Ping timeout: 268 seconds]
sunshavi has joined #linux-sunxi
netlynx has quit [Quit: Ex-Chat]
cnxsoft has joined #linux-sunxi
TheSeven has quit [Disconnected by services]
[7] has joined #linux-sunxi
TEKrantz has quit [Ping timeout: 268 seconds]
dddddd has quit [Remote host closed the connection]
pmpp_ has joined #linux-sunxi
pmpp has quit [Disconnected by services]
_whitelogger has joined #linux-sunxi
lurchi_ has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-sunxi
TEKrantz has joined #linux-sunxi
<MoeIcenowy>
ChriChri_: this is not retrievable on the device
<MoeIcenowy>
the user manual from Allwinner of this chip is needed
NeuroScr has joined #linux-sunxi
kainz has joined #linux-sunxi
NeuroScr has quit [Quit: NeuroScr]
hlauer has joined #linux-sunxi
jstein has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
jstein has quit [Quit: quit]
nashpa has quit [Quit: Going away]
nashpa has joined #linux-sunxi
tl_lim has quit [Read error: Connection reset by peer]
pmpp_ has quit [Ping timeout: 265 seconds]
florian_kc has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
pmpp has joined #linux-sunxi
florian_kc has quit [Ping timeout: 265 seconds]
Perlovka_ has joined #linux-sunxi
marble_visions has joined #linux-sunxi
slapin has joined #linux-sunxi
hlauer_ has joined #linux-sunxi
superprower has joined #linux-sunxi
Perlovka has quit [Ping timeout: 265 seconds]
marble_visions_ has quit [Ping timeout: 265 seconds]
hlauer has quit [Ping timeout: 265 seconds]
slapin_ has quit [Ping timeout: 265 seconds]
superpro1 has quit [Ping timeout: 265 seconds]
reinforce has joined #linux-sunxi
ChriChri_ has left #linux-sunxi [#linux-sunxi]
ChriChri has joined #linux-sunxi
<ChriChri>
MoeIcenowy: Does it make sense to ask them? On there site there seems not to be much information available...
jstein_ has joined #linux-sunxi
jstein_ is now known as jstein
pmpp has quit [Ping timeout: 265 seconds]
JohnDoe_71Rus has joined #linux-sunxi
<kainz>
@ChriChri odds may be slim but if you can find a way to pull boot0/the uboot out of the device theres a (slim) chance you might be bale to find something
florian_kc has joined #linux-sunxi
<kainz>
Is there documentation anywhere on what the thermal sensor calibration on H3/H5/A64 et al actually does? I'm testing sun8i_thermal.c on a nanopi-a64, and I'm either pulling wrong calibration values from the nvmem cell, or the calibration doesnt work the same way as h3. Looking through the bsp drivers and the openbsd driver, it looks like they
<kainz>
dont bother with the calibration. If that data's useful, I'd like to fix it ofc, but it looks accurate enough to handle cpufreq tripping as-is. Any recommendations, or is anyone actively working on that? Alternately, are there any other A64 boards that are known to work properly with that calibration? I have 1 or two other A64s but I havent had
<kainz>
at opportunity to boot/test them yet. I'm using sun8i-thermal.c from the megous ths-5.3 branch. I get sane-looking readings when I disable the h3 calibration on A64, and readings from the raw register values that are way off if I use the NVRAM calibration.
<kainz>
I can share my .dts changes if anyones interested.
<Ixnus>
search for B288 datasheet or user manual may get lucky
Ixnus has quit [Remote host closed the connection]
megi has joined #linux-sunxi
ChriChri has quit [Quit: bye...]
ChriChri has joined #linux-sunxi
<ChriChri>
Ixnus: I'd make a wiki page if I could get further. Up to now I do not have much information at hand.
<megi>
kainz: A64 is the only SoC I didn't debug (I don't have any device with it yet), when fixing up thermal sensor driver, so if you figure something out, let me know and I'll incorporate it
<megi>
maybe you're reading calibration data from the wrong location
<megi>
sid driver offsets addresses by 0x200 compared to what you see in BSP
<megi>
at least for some SoCs
<kainz>
The BSP i'm looking at for the nanopi a64 doesnt touch the sid for the thermal sensor at all it looks like.
<kainz>
its the one linked to from the nanopi a64 page in the linux-sunxi.org wiki.
<megi>
what version of Linux it's based on?
<kainz>
3.10.65.
<megi>
there's also newer BSP, based on 4.9
<ullbeking>
libv: 1. is the chenxi a real thing? 2. are they ALL ARM-based? are here any MIPS-based ones currently being produced?
<ChriChri>
kainz: Thanks for the suggestion! That's the direction I was hoping for... Well, I have the firmware-download unpacked and there is a file called *.uboot (size 664K) which starts with the string 'sunxi-package' and at 0x3c contains 'MIE;u-boot'. I didn't find information how to extract uboot from that file. Furthermore I can read /boot on the device, which contains the following files: REV, battery_low.bmp, default.wbf, hwconfig,
<ChriChri>
hwdevice, magic.bin, uImage, updatefs, vcom, wavefile. I probably could somehow transfer those files, if they'd be of any use.
<libv>
ullbeking: i have no idea, i just stumbled over it from a olimex wordpress comment, and then saw that statement about our wiki
<kainz>
@megi any idea where i'd find that bsp? I'm comping up short on linux-sunxi and pine64.org
<megi>
see "Dump H6 THS regs", and you can just change the base address for ths
<kainz>
i'll try that out, thanks! I'm about to go to bed for a few hours though.
<kainz>
That said, my compile>load>retry workflow is about 30 secs-1 minute per
ldevulder__ has quit [Ping timeout: 265 seconds]
<megi>
pretty good :)
<kainz>
provided I dont brick a target
<kainz>
I dont have it rigged up to netboot/hardware power cycle, but thats in the plan
<megi>
though with this tool, you can try different calibration values at runtime and see changes immediately
<kainz>
I'll definitely try that out, then.
florian has joined #linux-sunxi
AneoX has joined #linux-sunxi
<karlp>
wens: do you want me to change regulator node names? mripard says they've already accepted them, and I just copied the names from the librelec board. I cant' find any more concrete guidance on the naming
<clementp[m]>
Hi, I'm beginning with yaml schema, I am doing some test on allwinner,sun4i-a10-pwm.yaml, tweaking the example to trig an error "compatible = "allwinner,sun7i-a20-pwm" => compatible = "allwinner,sun7i-a23-pwm";
<clementp[m]>
the example is compiled but nothing is triggered
<clementp[m]>
DT_SCHEMA_FLAGS="-u" DT_SCHEMA_FILES="Documentation/devicetree/bindings/pwm/allwinner,sun4i-a10-pwm.yaml" make dt_binding_check
pmpp has quit [Remote host closed the connection]
pmpp has joined #linux-sunxi
lurchi_ is now known as lurchi__
tuxd3v has joined #linux-sunxi
pcbBob has joined #linux-sunxi
<pcbBob>
Is this channel only for questions regarding Allwinner chips?
vagrantc has joined #linux-sunxi
<KotCzarny>
that's what netiquette says
<KotCzarny>
but see topic too
<pcbBob>
Is there a similiar project for MediaTek chips then?
<KotCzarny>
i wouldnt expect much, but there is a possibility
<pcbBob>
So I have this ARM7TDMI-based chip with 170 pages of documentation and there is a small section about how to perform "Factory Programming". There is a GPIO which' state controls how the chip is booted up (either factory programming or "normal operation"). The factory programming goes like this: Data is transferred over UART1 into the internal SRAM
<pcbBob>
(32KB) - but there is no information about what baud rate and what kind of data format whatsoever
<pcbBob>
Now I found some source code from MediaTek on GitHub which pretty much says that there is some kind of header and stuff before the actual program
<pcbBob>
Now as far as I know the Allwinner chips basically work the same way for boot code - right? So I was wondering if anyone could give me some hints about what to watch out for
<pcbBob>
Is it just like this: [secret MediaTek Header][my c-file object code generated by arm-noneabi compiler][checksum] ?
<pcbBob>
And what I am also wondering is whether if this code transferred over UART1 which is then put into internal SRAM should act as a bootloader (initializing external Flash and writing new incomming data into flash which then is the program to be executed for normal operation)
<KotCzarny>
every vendor has it's own proprietary code, unfortunatelly
<KotCzarny>
as there is no standard
<pcbBob>
This chip also has JTAG - is it possible to upload a program into Flash only via JTAG?
LargePrime has quit [Quit: Leaving]
<karlp>
mediatek was around when arm7tdmi was?
<karlp>
you'll probably have better luck finding an old windows flashing binary and revenging the protocol than you will finding the jtag flash protocol, but, both are possible...
<pcbBob>
Yeah, it is probably their first mobile chip they ever did, released back in 2003
<pcbBob>
I found some slides on baidu and they seemed to even use the famous "FlashTool" back then which is also used now to flash modern MediaTek based Smartphones
<pcbBob>
I don't know much about JTAG but..do I need some kind of config file for this specific processor or is it enough if I just say to my JTAG-IDE that an ARM7TDMI is connected?
<pcbBob>
Because I doubt that there is any config file
<aalm>
i'd try googling for "mediatek mt62xx sdk" or something
pcbBob has quit [Remote host closed the connection]
hlauer_ has quit [Ping timeout: 268 seconds]
TEKrantz has quit [Ping timeout: 240 seconds]
TEKrantz has joined #linux-sunxi
popolon has quit [Quit: WeeChat 2.6]
<ullbeking>
14:16 <libv> anyway, high powered mini-itx systems not much bigger than a mini-itx board do have their uses
<ullbeking>
14:16 <libv> but perhaps gamers should not build mini-itx systems
<ullbeking>
I agree. I have seen some completely ridiculous "SFF" systems where gamers cram so much shit in to a tiny case.... and then complain that they are loud, lol