Re: [gentoo-user] crossdev arm-unknown-linux-gnu failed

[Jeremi Piotrowski]

On Sun, May 27, 2018 at 05:06:43AM +0200, tu...@posteo.de wrote:
> Hi,
> 
> too feed a STM32F103C8T6 MCU (Core-M3) with some code to execute,
> I want a compiler. For that I did a 
> 
> crossdev arm-unknown-linux-gnu
> 
> . That one failed to build (gcc, binytils seem to be ok).
> 
That triplet is not going to work for that hardware for two reasons:

 - bare-metal implies no kernel so 'linux' is wrong
 - gnu (== glibc) is not going to work on bare-metal

What you're looking for is 'arm-none-eabi', that's what all the vendor
supplied prebuilt toolchains use. That triplet will use 'newlib' as the
libc, which is the correct choice for bare-metal.

I wouldv'e said 'arm-unknown-linux-eabi' or the gentoo specific
'armv7m-softfloat-none-eabi' but for some reasons the binutils
build chokes on that. However compared to arm-none-eabi the only thing
these triplets do is change some of the configured defaults (arch/fpu/...,
see /usr/portage/eclass/toolchain.eclass), so you should be fine with
'arm-none-eabi'.

Re: [gentoo-user] AMD microcode problem - Fam15h ( FYI )

[Adam Carter]

>
> I should have clarified ... the '-mno-lwp' was added as a result of the
> comparison of the two /proc/cpuinfo files. I was very curious about WHAT
> exactly the microcode update did.
>
> The CPU I am using is a FX-9590.
>
> Question : Is there a PSP in your CPU?
>

According to libreboot, only fam16 onwards have PSP, so if that's true, no.
AFAIK the 9590 is identical to the 8350 other than being clocked higher, so
i'm expecting our experience to be the same.

Also, are you saying that the sequence of events for you was;
- booted with new microcode, and lwp was missing from /proc/cpuinfo
- you had instability
- you rebuilt with -mno-lwp
- stability returned

Re: [gentoo-user] Vcore unstable?

[mad.scientist.at.large]

Thank you, I assumed that was what was going on but wanted to be sure before i 
did an install on it lest it die half way through.
mad.scientist.at.large (a good madscientist)
--



26. May 2018 22:00 by r03...@gmail.com :


> On Sat, May 26, 2018 at 6:50 PM,  <> mad.scientist.at.la...@tutanota.com 
> > > wrote:
>>
>> i have a machine i just put lm sensors etc. on.  xsensors shows "Vcore"
>> fluctuating between 1.12 and 1.3v.  stays at 1.12V when idling but increases
>> with load.  Is this remotely normal behavior for an athlon chip in a desk
>> top?  It's either some sort of throttling or the Vcore power supply is
>> failing, obviously i'd like to know which.  If it's the power supply i can
>> likely fix it if it needs to be fixed.  Also occurs to me that xsensors
>> could be usefull tracking down intermittent issues.  I used it to monitor a
>> power supply i wasn't sure about for about a week and it stayed nice.
>>
>> mad.scientist.at.large (a good madscientist)
>> --
>>
>
> If it increases with load the regulator is working properly. The
> higher voltage is needed to induce a higher current slew rate, i.e.
> how fast the electrons accelerate, i.e. chip frequency.
>
> Cheers,
>  R0b0t1

Re: [gentoo-user] crossdev arm-unknown-linux-gnu failed

[tuxic]

On 05/26 11:00, R0b0t1 wrote:
> On Sat, May 26, 2018 at 10:35 PM, Andrew Udvare  wrote:
> >
> >
> >> On 2018-05-26, at 23:32, Andrew Udvare  wrote:
> >>
> >> You probably mean to use another triple name. The last part is the C 
> >> library, so you probably mean:
> >>
> >> arm-unknown-Linux-glibc
> >
> > That is:
> >
> > arm-unknown-linux-glic
> >
> > It is case-sensitive.
> >
> 
> You may need to fix the profile yourself, but the typical triplet is
> now "arm-linux-gnueabihf." There is a tracker issue on this. Most
> things compile for me, some breakage in @system.
> 
> Cheers,
>  R0b0t1
> 

Hi,

the target is a STM32F03C8T6 (the typical "Blue Pill" dev board), this
MCU has no FPU so "hf" (hardfloat) seems to be wrong to me...

And maybe a noob-question:
What profile do you mean?

Cheers
Meino