[PATCH v1 0/9] Enable SMP for pc386 based bsps

[Chris Johns]

On 16/6/20 10:55 pm, Joel Sherrill wrote:
> On Tue, Jun 16, 2020 at 7:08 AM <Jan.Sommer at dlr.de <mailto:Jan.Sommer at dlr.de>>
> wrote:
>     > -----Original Message-----
>     > From: Chris Johns [mailto:chrisj at rtems.org <mailto:chrisj at rtems.org>]
>     > Sent: Tuesday, June 16, 2020 10:18 AM
>     > To: Sommer, Jan; devel at rtems.org <mailto:devel at rtems.org>
>     > Subject: Re: [PATCH v1 0/9] Enable SMP for pc386 based bsps
>     >
>     > On 11/6/20 12:21 pm, Chris Johns wrote:
>     > > On 1/6/20 12:22 am, Jan Sommer wrote:
>     > >> Hello,
>     > >>
>     > >> Here is a patch set which should enable SMP again for the pc386-based
>     > BSPs (mainly tested with pc686).
>     > >
>     > > Many thanks for these patches and your efforts.
>     > >
>     > >> So far I only tested it with qemu. Tests on real hardware are pending.
>     > >
>     > > It would be good to test results for hardware with SMP disabled. If the test
>     > > results do not show any regressions then I am fine with these patches for
>     > RTEMS
>     > > 5.2 with SMP documented as experimental. I will take a look at doing this.
>     >
>     > I have finally managed to get my test PC to load a iPXE loader and with that I
>     > can boot RTEMS. Without the changes I can run hello.exe and it prints the
>     > right
>     > stuff on the monitor however the iPXE boot command line that use to work
>     > ...
>     >
>     > chain tftp://10.10.5.2/rtems.exe <http://10.10.5.2/rtems.exe>
>     --console=/dev/com1,115200
>     > --printk=/dev/com1,115200
>     >
>     > ... does not generate any serial output. The output is being redirected and
>     > the
>     > serial port because nothing appears on the monitor and I tested the cable is
>     > working with a loop-back jumper.
>     >
> 
>     Sorry for the delay, we had some problems in our lab setup as well.
>     It is working now again and I could receive the output of ticker via the
>     serial line.
>     I hope I can run the testsuites in the coming nights. Then I can respond to
>     your other comments.
> 
>     Do you have a chance to check the pins of you serial port with an Oscilloscope?
>     Our board allows in the BIOS to configure the serial port for different
>     protocols (RS232 and RS422) maybe some pin mappings are not correct?
> 
>     Maybe it is of any help to you. Our ipxe script looks like this:
> 
>     echo Trying to receive IP-address...
>     dhcp || goto dhcp_failed
>     echo Received the following IP settings:
>     route
>     chain tftp://${net0/next-server}/ticker.exe --console=/dev/com1,115200

Mine is close to this. As posted above I have --printk=/dev/com1,115200.

Note, the tester has a bug where it does not correctly handle TFTP exe file
names when there is no filter configured. I will raise a ticket and push the fix
for this soon.

> 
>     :dhcp_failed
>     echo Failed to acquire configuration via dhcp.
>     echo Opening shell...
>     shell
> 
> 
> We had this problem trying to set up the embedded PC we use for testing in the
> new lab. 
> When we tried the same hardware with FreeDOS, it worked. When we tried an old Dell
> desktop as the RTEMS PC, the serial port didn't work.

I have a legacy small form factor ITX computer with a standard COM1 RS232 only port.

> We tried various combinations of computers running RTEMS and the comms program. 
> The only common denominator was the one running RTEMS wouldn't give serial output.
> 
> I have these patches ready to push. Chris.. should I push them?

Yes I think they are OK to push. I was hoping to have run all the tests by now.

Chris