This removes TRACE_DEV(), turning it into pll_verbose() and wrc_verbose().

The functions are enabled and disabled by kconfig, with defaults matching
the previous behaviour.

So nothing changes, but the binary is smaller because the previous
wrc_debug_printf() was silent because of a run-time conditional
(though hardwired false at build time). The condional is now at build
time.  We save around 2k, between strings and calling code, in
all wrc builds (nothing is saved in wrs, which is verbose by default,
nor in devel_build_test_defconfig where all verbose options are on)).

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

devel_build_test_defconfig: enable all verbose options

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Actually, Etherbone is in gateware, and this option only enables Internet
Protocol in the software.  This fixes a long-standing misunderstanding.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

If the Kconfig option is not set, there's no effect on code size.
If set, .bss increases by 256 bytes (the buffer) and .text by
another 200 bytes.

This adds timestamping support, so we know the duration of the
interrupt (because we found it's an important thing when problems
occur).

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

CONFIG_WRNIC was not used, so it is now removed.
CONFIG_NIC_PFILTER does it all

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

E.g. Kintex-7

This adds two commands: devemem (to read and write registers/RAM)
and delays (to read and change the constant delays.  The commands are
only available for CONFIG_DEVELOPER builds.

The default delays were just wrong, they are valid of an older
gateware version.  Using 0, it is clearer to the user that the right
value is missing (if the SFP database is populated, the right value
applies anyways).

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Adam Wujek authored 9 years ago and Grzegorz Daniluk committed 9 years ago

Add checking stack overflow and detecting reset to wrs. Code common for wrpc
and wrs is placed in system_checks.c and .h. Work is based on following
commits in wrc_main.c:
1704a668 main: check for stack overflow
7836c39e

 Optionally detect reset and print a stack trace

Additionally:
--update Kconfig to have a possibility to select CHECK_RESET also for switch,
  not only for node as before
--and _endram to ram-wrs.ld

When "stack overflow" occurs then message is printed once every second.
When reset occours then LM32 will print stack trace and reset once more.
NOTE: I couldn't get spll to work after reset, for sure problem is in
      ad9516 init function, but not only there.

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

We agreed, long ago, to have 128k on the spec, like GSI is
already doing. This changes the default in Kconfig and removes
specific settings in configs/*

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Alessandro Rubini authored 10 years ago and Grzegorz Daniluk committed 10 years ago

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This has no effect on wrc.bin. The commit unifies the directory
softpll/ between wr-switch and wr-node. No differences are left.

This is an ugly ifdef, but I prefer merging the code base (removing
duplicates) before addressing the configuration problem.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Miguel Jimenez Lopez authored 11 years ago and Grzegorz Daniluk committed 11 years ago

	- Added the NIC_PFILTER configuration option in Kconfig to decide which filter rules will be used.
	- Updated the dev/ep_pfilter.c file by using the CONFIG_NIC_PFILTER macro. This is done because packet filter does
	not work correctly if we write all rules in the CONFIG_ETHERBONE section.
	- We do not use the DROP instruction because all other packets go to NIC core.

Notes:

	- The filter rules to the wr-nic do not have the DROP instruction because all traffic
	does not go to the LM32/Etherbone is re-direct to the NIC by default.

	- The NIC_PFILTER configuration option depends on ETHERBONE one.

	- Magic number of Etherbone packets is not checked due to the number of rules. (The packet filter is not able to classify correctly)

Miguel Jimenez Lopez authored 11 years ago and Grzegorz Daniluk committed 11 years ago

- Added CONFIG_WRNIC in Kconfig to decide which filter rules will be use.
- Updated ep_pfilter using CONFIG_WRNIC.
- We do not use drop because all other packet goes to NIC core.

Note: filter rules to wr-nic do not have DROP instruction because all traffic
does not go to LM32/Etherbone is re-direct to NIC by default.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This commits affect several files, to be able to support both uart and
uart_sw at the same time. My aim is sending verbose ppsi diagnostics
to the uart_sw while retaining the real uart (or vuart) for the
interactive user and wrpc status gui.

To this aim, I use weak functions to avoid hairy ifdef around the code.
Now both hw and sw uarts are initialized, and the missing init just
does nothing. Also, uart_sw_write_string is always defined, and
it is an alias of uart_write_string if no uart_sw is built.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This introduced an "advanced" menu, only for developers, and most
questions are grouped in there, because we cannot support users
playing with experimental features or work in progress (like the new
onewire code, or the new ptp daemon) until they are the officially
supported option.

The commit also removes changes in stack size, because the new
calibration code by tom is not stack-hungry like the previous one:
wrnic_defconfig is now the same as spec_defconfig and ppsi doesn't
select a bigger stack any more.

Finally, ppsi_defconfig replaces spec_ppsi_defconfig, since we only
support the "spec" hardware configuration (other implementations we know
of are still very much spec-alike).

Unfortunately, this spits two warnings:

    Kconfig:25:warning: defaults for choice values not supported
    Kconfig:29:warning: defaults for choice values not supported

even if such defaults actually works. The next commit removes them.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This adds the build choice about whether to use the older sockitowm or
the new "w1" implementation, which supports all three thermometers
but is still missing eeprom support (the API is defined, though, see
include/w1.h

This also adds a shell command, called "w1", which rescans the bus and
tries to read the temperature from all devices. In the example below
the third device is an eeprom, so it return an error for temperature
read-out.

   wrc# w1
   W1: 68000801dce56910
   W1: f70000001eda8242
   W1: 5f00000040e50143
   device 0: 68000801dce56910
   temp: 34.7500
   device 1: f70000001eda8242
   temp: 32.5000
   device 2: 5f00000040e50143
   temp: -32768.0000

The code is properly integrated in wrpc-sw, and the "first" thermometer is
used to build the MAC address of the device, like it used to be with
sockitowm.

The binary built with w1 is 3kB smaller than what is build with sockitowm.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This introduces dev/uart-sw as an alternative to dev/uart . The
software-only thing is a pair of circular buffers that can be driven
by tools/wrpc-uart-sw .

The software uart can be enabled by Kconfig (and is disabled by
default).  The code size is the same as the uart, but it "wastes" 306
bytes of data space.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This command can return the .config file to the user. It can be useful
to trace what is actually running, as addition to the "ver"
command.  It is optional because it costs .5kB of binary size.

Example:

  wrc# config
    Current WRPC-SW configuration:
  CONFIG_RAMSIZE=90112
  # CONFIG_PTP_NOPOSIX is not set
  CONFIG_PPSI=y
  # CONFIG_CHECK_RESET is not set
  CONFIG_PPSI_VERBOSITY=0
  CONFIG_PPSI_RUNTIME_VERBOSITY=y
  CONFIG_STACKSIZE=2048
  CONFIG_PP_PRINTF=y
  # CONFIG_PRINTF_FULL is not set
  CONFIG_PRINTF_XINT=y
  # CONFIG_PRINTF_MINI is not set
  # CONFIG_PRINTF_NONE is not set
  CONFIG_PRINT_BUFSIZE=128
  CONFIG_ETHERBONE=y
  # CONFIG_DETERMINISTIC_BINARY is not set
  CONFIG_CMD_CONFIG=y

(This configuration amounts to a binary size of 86252 bytes, at this
commit).

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The parameter used to be off by default in order to save space in the
generated binay.  Now ppsi is smaller and there's no reason to
prevent diagnostic code to be there.

This parameter, though, will disappear over time, as we have a new
diagnostic system, more modular (which still offers a compile-time
option to remove all diagnostic code).

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The new configuation option CONFIG_CHECK_RESET adds a function to dump
the stack (to the serial port) if a reset is detected. This happens
when a null pointer is followed or when the program is reloaded
(spec-sw/tools/spec-cl, for example).  For this reason, the feature is
disabled by default (actually, spec-cl may clear the RAM first, but it
currently doesn't do that and the check is triggered).

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Alessandro Rubini authored 12 years ago and Grzegorz Daniluk committed 12 years ago

mprintf is of uncertain copyright status, and that's why
we added pp_printf (actually, that's why I picked pp_printf
fro ptp-proposal and made it a standalone thing).

Now that everyone involved confirms pp_printf is well tested,
let's remove mprintf.  We still accept mprintf in the callers,
because the name is used by our ptp-noposix submodule, and I'm
sure people has it in their fingers and it will appear again.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Aurelio Colosimo authored 12 years ago and Alessandro Rubini committed 12 years ago

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

It also used cflags-y in the same way.

CONFIG_DETERMINISTIC_BINARY confirms this makes no difference in
the generated binary, but it opens to more configuration options.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>