FCSP RS485 port access Success!

[ericpullen]

Unless I can find a way into the Linux is running on this thing, I’m not sure there is much more to see. I can’t see charging rates through any of the exposed APi’s, just that status message I showed earlier.

How valuable would it be for people to have access to just that piece (along with the metadata like version, etc)?

I’ve got some ideas on how to possibly break in using the Django setup (it seems very old and possibly hackable), but so far my attempts have not worked.

Sponsored

 

[cjueden]

I made some more hardware access attempts this afternoon and was able to get output with the P8 pins and putty with a baud rate of 38400 after pressing the MCU_RST_SW button. Don't know what it means and was never able to make an input when the SFT> prompt showed.

So I thought I would try and do the same with the P3 pins and was able to get a telnet terminal using baud rate 115200. At first it shows and blank and after hitting enter a few times the login prompt and EVSE banner show. I still don't know what the creds are but probably the same as the SSH if those are ever discovered.

Not sure what to do with these access points. Anyone know where or have a suggestion on where togo from here?

 

[ericpullen]

Ooh, that EVSE prompt looks very promising. Have you tried any logins on it. Here are a few to start with:
Common Default Credentials to Try
Most Common Siemens Defaults:
• Username: admin / Password: admin
• Username: root / Password: admin
• Username: root / Password: root
• Username: admin / Password: (blank/empty)
UART/Serial Console Specific:
For the Linux-style login prompt you’re seeing, common embedded system defaults include:
• Username: root / Password: admin
• Username: root / Password: root
• Username: admin / Password: admin
• Username: root / Password: (blank/empty)
Additional Possibilities:
• Username: siemens / Password: siemens
• Username: service / Password: service
• Username: technician / Password: technician

 

[tearitupsports]

Ooh, that EVSE prompt looks very promising. Have you tried any logins on it. Here are a few to start with:
Common Default Credentials to Try
Most Common Siemens Defaults:
• Username: admin / Password: admin
• Username: root / Password: admin
• Username: root / Password: root
• Username: admin / Password: (blank/empty)
UART/Serial Console Specific:
For the Linux-style login prompt you’re seeing, common embedded system defaults include:
• Username: root / Password: admin
• Username: root / Password: root
• Username: admin / Password: admin
• Username: root / Password: (blank/empty)
Additional Possibilities:
• Username: siemens / Password: siemens
• Username: service / Password: service
• Username: technician / Password: technician

I think it may be admin and for the password the serial number of the unit.

 

[cjueden]

Ooh, that EVSE prompt looks very promising. Have you tried any logins on it. Here are a few to start with:
Common Default Credentials to Try
Most Common Siemens Defaults:
• Username: admin / Password: admin
• Username: root / Password: admin
• Username: root / Password: root
• Username: admin / Password: (blank/empty)
UART/Serial Console Specific:
For the Linux-style login prompt you’re seeing, common embedded system defaults include:
• Username: root / Password: admin
• Username: root / Password: root
• Username: admin / Password: admin
• Username: root / Password: (blank/empty)
Additional Possibilities:
• Username: siemens / Password: siemens
• Username: service / Password: service
• Username: technician / Password: technician

I think it may be admin and for the password the serial number of the unit.

No Dice :/

 

[ericpullen]

The next thing to try is hook up to that uart and power cycle the FCSP and see if it gives us any clues during boot up

I don’t have a usb serial adapter handy or I would, but I’ll see if I can get one to start playing with this.

 

[cjueden]

The next thing to try is hook up to that uart and power cycle the FCSP and see if it gives us any clues during boot up

I don’t have a usb serial adapter handy or I would, but I’ll see if I can get one to start playing with this.

I pressed both the A8 RST button and the MCU_RST_SW while connected to the telnet and it didn't change the output/terminal at all. I wonder if the A8 RST button is a reset for the A8 RS485 connection.
WOW, I completely miss read that. I will have to try to power cycle while connected tomorrow.


while at it I hooked up to the MTR_CON which I think stands for "Monitor Connector/tion" and received alot of noise I think I need to hook up the SCK pin that will solve the noise issue. Just don't have it setup with the wiring for that at the moment.

 

[ericpullen]

I was thinking a full breaker off power cycle. I just remember I do have a spare Raspberry Pi Zero W that I can turn into a wifi rs232 node. If I have some time tomorrow I may play with that and see if I can match what you are seeing.

 

[Aminorjourney]

So I happen to have a spare FCSP.

I can confirm will boot up its LV systems if you add a 12-V supply to the Dark Start connection

I wonder if this might be a way to bench test this a little more rather than using in-situ systems.

Is there a git somewhere for what we've got so far?

 

[cjueden]

So I happen to have a spare FCSP.

I can confirm will boot up its LV systems if you add a 12-V supply to the Dark Start connection

I wonder if this might be a way to bench test this a little more rather than using in-situ systems.

That's good to know! I'd like to keep my digits away from the extra spicy wires
as much as possible.

Is there a git somewhere for what we've got so far?

Not yet. I was waiting until there was something more substantial to put out there. I can make one if anyone would like me move it to that.

 

[ericpullen]

I've got some sample code to pull what little data is available from the API directly on the FCSP, but I haven't had time to clean it up. I'll try and do that tomorrow and post it on github.

Here is where I left it off, it can detect state changes now, but I don't see any way to tell what charge rate it is at. You can see from below where I connect but not charging, then I have it do a remote start, which pulls from the FCSP, then it stops the remote start and goes back to just connected but not charging, then I unplug to leave for lunch.

⚡ FCSP Enhanced Charging Status
==================================================

🟡 CHARGING STATUS
=========================
State: CS01 - Connected (Not Charging)
Description: Vehicle connected but charging paused/stopped
Vehicle Connected: True
Actively Charging: False

🔄 INVERTER STATUS
--------------------
Inverter 1: 💤 0 - Idle

📊 DEVICE INFO
---------------
Max Capacity: 80 Amps
Station ID: SWA33ROU
IP Address: 192.168.1.197

🔄 DOCUMENTED STATE TRANSITIONS
========================================
State Flow:
CS00: 🟢 Available for any vehicle
      Action: No vehicle
  Plug in vehicle
CS02: 🔋 Vehicle charging (immediate)
      Action: Start charging
  Stop charging
CS01: 🟡 Vehicle connected but paused
      Action: Connected, not charging
  Unplug vehicle
CS00: 🟢 Back to available
      Action: No vehicle

🔄 Monitoring for State Changes (60 minutes)
==================================================
Connect a vehicle or change charging state to see status changes...

🔔 [11:34:04] STATE CHANGE DETECTED!
   Device: None → CS01
   Inverters: None → ['0']
[11:34:20] Device: CS01, Inverters: ['0']
[11:55:16] Device: CS01, Inverters: ['0']

🔔 [11:55:31] STATE CHANGE DETECTED!
   Device: CS01 → CS02
   Inverters: ['0'] → ['0']
[11:55:45] Device: CS02, Inverters: ['0']
[12:10:58] Device: CS02, Inverters: ['0']

🔔 [12:11:12] STATE CHANGE DETECTED!
   Device: CS02 → CS01
   Inverters: ['0'] → ['0']
[12:11:26] Device: CS01, Inverters: ['0']
[12:16:13] Device: CS01, Inverters: ['0']

🔔 [12:16:31] STATE CHANGE DETECTED!
   Device: CS01 → CS00
   Inverters: ['0'] → ['0']
[12:16:45] Device: CS00, Inverters: ['0']

 

[cjueden]

I've got some sample code to pull what little data is available from the API directly on the FCSP, but I haven't had time to clean it up. I'll try and do that tomorrow and post it on github.

Here is where I left it off, it can detect state changes now, but I don't see any way to tell what charge rate it is at. You can see from below where I connect but not charging, then I have it do a remote start, which pulls from the FCSP, then it stops the remote start and goes back to just connected but not charging, then I unplug to leave for lunch.

⚡ FCSP Enhanced Charging Status
==================================================

🟡 CHARGING STATUS
=========================
State: CS01 - Connected (Not Charging)
Description: Vehicle connected but charging paused/stopped
Vehicle Connected: True
Actively Charging: False

🔄 INVERTER STATUS
--------------------
Inverter 1: 💤 0 - Idle

📊 DEVICE INFO
---------------
Max Capacity: 80 Amps
Station ID: SWA33ROU
IP Address: 192.168.1.197

🔄 DOCUMENTED STATE TRANSITIONS
========================================
State Flow:
CS00: 🟢 Available for any vehicle
      Action: No vehicle
  Plug in vehicle
CS02: 🔋 Vehicle charging (immediate)
      Action: Start charging
  Stop charging
CS01: 🟡 Vehicle connected but paused
      Action: Connected, not charging
  Unplug vehicle
CS00: 🟢 Back to available
      Action: No vehicle

🔄 Monitoring for State Changes (60 minutes)
==================================================
Connect a vehicle or change charging state to see status changes...

🔔 [11:34:04] STATE CHANGE DETECTED!
   Device: None → CS01
   Inverters: None → ['0']
[11:34:20] Device: CS01, Inverters: ['0']
[11:55:16] Device: CS01, Inverters: ['0']

🔔 [11:55:31] STATE CHANGE DETECTED!
   Device: CS01 → CS02
   Inverters: ['0'] → ['0']
[11:55:45] Device: CS02, Inverters: ['0']
[12:10:58] Device: CS02, Inverters: ['0']

🔔 [12:11:12] STATE CHANGE DETECTED!
   Device: CS02 → CS01
   Inverters: ['0'] → ['0']
[12:11:26] Device: CS01, Inverters: ['0']
[12:16:13] Device: CS01, Inverters: ['0']

🔔 [12:16:31] STATE CHANGE DETECTED!
   Device: CS01 → CS00
   Inverters: ['0'] → ['0']
[12:16:45] Device: CS00, Inverters: ['0']

Did the info you pulled from the APIs show anything regarding OCPP?

 

[ericpullen]

Did the info you pulled from the APIs show anything regarding OCPP?

Nothing in the current API related to OCPP, which would have been a huge win if it existed.

I've finally got my Raspberry Pi Zero serial setup complete, so I can start probing from the comfort of my office instead of going out to the hot garage. If I can figure out how to get into the unit this way, there could be a whole bunch of opportunities open up past just seeing state changes like I showed before.

 

[cjueden]

The next thing to try is hook up to that uart and power cycle the FCSP and see if it gives us any clues during boot up

I don’t have a usb serial adapter handy or I would, but I’ll see if I can get one to start playing with this.

Ok I found some time to get the telnet output of the P3 / A8 debug uart on power cycle.

 2d       D▒*""▒   D ▒ "**  "*"""""$   "$   F" " """"22 """2022022""2"22 " """" ▒` ▒`▒"  ("" " ▒`(   DD"D1@ DD                                                                                     222"20" 22""22  22"2@01(@@1""""@""" ▒"▒@ DD@ 000 00000     000  $       " " D`
1D   $"$"""@ B▒ $                   ▒"    D  @▒  d▒          @  **2  ( *D   D▒F"▒DD"""D     1    20  "2  "(`▒                                                                                     2  ▒▒D"(    ""  (1@1""2 "( (    1D▒ 22 ▒▒▒ 1d0 ▒▒  ▒dD1DD0D▒ (D `D (@D  DF  $   4 04$ 000000040!@1D`20 4▒[                                                                                         0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.126-g259f2e0422 (oe-user@oe-host) (gcc version 7.2.1 20171011 (Linaro GCC 7.                                                                                     2-2017.11) ) #1 PREEMPT Wed May 18 21:18:56 UTC 2022
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt:Machine model: TI AM335x EVM-SK
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Reserved 48 MiB at 0xbd000000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] AM335X ES2.1 (neon)
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260416
[    0.000000] Kernel command line: console=ttyO0,115200n8 root=PARTUUID=4f9cc8ba-02 rw rootfstype=ext4 rootw                                                                                     ait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 976280K/1048576K available (8192K kernel code, 325K rwdata, 2772K rodata, 1024K init,                                                                                      287K bss, 23144K reserved, 49152K cma-reserved, 212992K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0900000   (9184 kB)
[    0.000000]       .init : 0xc0c00000 - 0xc0d00000   (1024 kB)
[    0.000000]       .data : 0xc0d00000 - 0xc0d51568   ( 326 kB)
[    0.000000]        .bss : 0xc0d51568 - 0xc0d9941c   ( 288 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[    0.000000] OMAP clockevent source: timer2 at 24000000 Hz
[    0.000029] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000076] clocksource: timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000099] OMAP clocksource: timer1 at 24000000 Hz
[    0.000489] clocksource_probe: no matching clocksources found
[    0.000860] Console: colour dummy device 80x30
[    0.000923] Calibrating delay loop... 298.59 BogoMIPS (lpj=1492992)
[    0.067647] pid_max: default: 32768 minimum: 301
[    0.067913] Security Framework initialized
[    0.067997] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.068023] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.069773] CPU: Testing write buffer coherency: ok
[    0.070491] Setting up static identity map for 0x80100000 - 0x80100060
[    0.072569] EFI services will not be available.
[    0.076126] devtmpfs: initialized
[    0.107493] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    0.108394] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000                                                                                      ns
[    0.108448] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.115388] pinctrl core: initialized pinctrl subsystem
[    0.118244] NET: Registered protocol family 16
[    0.122614] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.157614] omap_hwmod: debugss: _wait_target_disable failed
[    0.227734] cpuidle: using governor ladder
[    0.257713] cpuidle: using governor menu
[    0.273341] OMAP GPIO hardware version 0.1
[    0.312483] No ATAGs?
[    0.312528] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.378830] edma 49000000.edma: TI EDMA DMA engine driver
[    0.386850] SCSI subsystem initialized
[    0.387622] usbcore: registered new interface driver usbfs
[    0.387940] usbcore: registered new interface driver hub
[    0.388195] usbcore: registered new device driver usb
[    0.389054] omap_i2c 44e0b000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux                                                                                     @800/pinmux_i2c0_pins, deferring probe
[    0.389175] omap_i2c 4802a000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux                                                                                     @800/pinmux_i2c1_pins, deferring probe
[    0.389264] omap_i2c 4819c000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux                                                                                     @800/pinmux_i2c2_pins, deferring probe
[    0.389576] pps_core: LinuxPPS API ver. 1 registered
[    0.389597] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[    0.389657] PTP clock support registered
[    0.391391] omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400
[    0.393290] Bluetooth: Core ver 2.22
[    0.393418] NET: Registered protocol family 31
[    0.393439] Bluetooth: HCI device and connection manager initialized
[    0.393473] Bluetooth: HCI socket layer initialized
[    0.393500] Bluetooth: L2CAP socket layer initialized
[    0.393570] Bluetooth: SCO socket layer initialized
[    0.394493] clocksource: Switched to clocksource timer1
[    0.420885] NET: Registered protocol family 2
[    0.422532] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.422762] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.422980] TCP: Hash tables configured (established 8192 bind 8192)
[    0.423190] UDP hash table entries: 512 (order: 1, 8192 bytes)
[    0.423259] UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
[    0.423590] NET: Registered protocol family 1
[    0.424670] RPC: Registered named UNIX socket transport module.
[    0.424702] RPC: Registered udp transport module.
[    0.424718] RPC: Registered tcp transport module.
[    0.424733] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.426690] hw perfevents: enabled with armv7_cortex_a8 PMU driver, 5 counters available
[    0.432203] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.454031] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.458828] NFS: Registering the id_resolver key type
[    0.458919] Key type id_resolver registered
[    0.458939] Key type id_legacy registered
[    0.459047] ntfs: driver 2.1.32 [Flags: R/O].
[    0.472410] bounce: pool size: 64 pages
[    0.472924] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    0.472954] io scheduler noop registered
[    0.472972] io scheduler deadline registered
[    0.473340] io scheduler cfq registered (default)
[    0.477117] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.643598] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled
[    0.652687] omap_uart 44e09000.serial: no wakeirq for uart0
[    0.653112] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 158, base_baud = 3000000) is a OMAP UART0
[    1.318147] console [ttyO0] enabled
[    1.323036] omap_uart 48024000.serial: no wakeirq for uart2
[    1.329457] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 159, base_baud = 3000000) is a OMAP UART2
[    1.340514] omap_uart 481a8000.serial: no wakeirq for uart4
[    1.346776] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 160, base_baud = 3000000) is a OMAP UART4
[    1.359155] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20
[    1.366460] [drm] Initialized
[    1.403482] brd: module loaded
[    1.422916] loop: module loaded
[    1.434959] libphy: Fixed MDIO Bus: probed
[    1.442573] QCA7000 probe start
[    1.446076] qcaspi spi1.0: ver=0.2.7-i, clkspeed=8000000, burst_len=5000, pluggable=0
[    1.454463] QCA7000 mode=3, clkspeed=8000000, irq=56, mac=00:01:87:08:21:54
[    1.461880] QCA7000 reading signature value
[    1.466528] QCA7000 reading signature Success
[    1.471145] Registering QCA7000 Device
[    1.476617] QCA7000 Registartion Success: eth0
[    1.483096] PPP generic driver version 2.4.2
[    1.488269] PPP BSD Compression module registered
[    1.493227] PPP Deflate Compression module registered
[    1.498641] PPP MPPE Compression module registered
[    1.503687] NET: Registered protocol family 24
[    1.508452] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[    1.516469] usbcore: registered new interface driver pegasus
[    1.522585] usbcore: registered new interface driver r8152
[    1.528573] usbcore: registered new interface driver asix
[    1.534393] usbcore: registered new interface driver ax88179_178a
[    1.540974] usbcore: registered new interface driver cdc_ether
[    1.547314] usbcore: registered new interface driver smsc75xx
[    1.553515] usbcore: registered new interface driver smsc95xx
[    1.559724] usbcore: registered new interface driver net1080
[    1.565838] usbcore: registered new interface driver cdc_subset
[    1.572174] usbcore: registered new interface driver zaurus
[    1.578276] usbcore: registered new interface driver cdc_ncm
[    1.586745] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.593620] ehci-pci: EHCI PCI platform driver
[    1.598523] ehci-platform: EHCI generic platform driver
[    1.604416] ehci-omap: OMAP-EHCI Host Controller driver
[    1.610209] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.616801] ohci-pci: OHCI PCI platform driver
[    1.621624] ohci-platform: OHCI generic platform driver
[    1.628561] usbcore: registered new interface driver cdc_acm
[    1.634576] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    1.643123] usbcore: registered new interface driver uas
[    1.648945] usbcore: registered new interface driver usb-storage
[    1.655582] usbcore: registered new interface driver usbserial
[    1.661817] usbcore: registered new interface driver usbserial_generic
[    1.668833] usbserial: USB Serial support registered for generic
[    1.675296] usbcore: registered new interface driver cp210x
[    1.681248] usbserial: USB Serial support registered for cp210x
[    1.687617] usbcore: registered new interface driver ftdi_sio
[    1.693756] usbserial: USB Serial support registered for FTDI USB Serial Device
[    1.701582] usbcore: registered new interface driver option
[    1.707590] usbserial: USB Serial support registered for GSM modem (1-port)
[    1.715055] usbcore: registered new interface driver pl2303
[    1.721008] usbserial: USB Serial support registered for pl2303
[    1.727379] usbcore: registered new interface driver qcserial
[    1.733518] usbserial: USB Serial support registered for Qualcomm USB modem
[    1.740980] usbcore: registered new interface driver sierra
[    1.746980] usbserial: USB Serial support registered for Sierra USB modem
[    1.754217] usbcore: registered new interface driver ti_usb_3410_5052
[    1.761130] usbserial: USB Serial support registered for TI USB 3410 1 port adapter
[    1.769319] usbserial: USB Serial support registered for TI USB 5052 2 port adapter
[    1.777593] usbcore: registered new interface driver usbtest
[    1.788151] 47401300.usb-phy supply vcc not found, using dummy regulator
[    1.817520] usbip_core: USB/IP Core v1.0.0
[    1.823641] i2c /dev entries driver
[    1.831792] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    1.840295] device-mapper: uevent: version 1.0.3
[    1.846188] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: [email protected]
[    1.855215] Bluetooth: HCI UART driver ver 2.3
[    1.859898] Bluetooth: HCI UART protocol H4 registered
[    1.865393] Bluetooth: HCI UART protocol LL registered
[    1.871651] cpu cpu0: OPP-v2 not supported, cpufreq-dt will attempt to use legacy tables.
[    1.880875] cpuidle: enable-method property 'ti,am3352' found operations
[    1.889002] sdhci: Secure Digital Host Controller Interface driver
[    1.895573] sdhci: Copyright(c) Pierre Ossman
[    2.055177] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.066323] usbcore: registered new interface driver usbhid
[    2.072197] usbhid: USB HID core driver
[    2.076719] omap_hsmmc 47810000.mmc: card claims to support voltages below defined range
[    2.086745] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[    2.088531] ip_tables: (C) 2000-2006 Netfilter Core Team
[    2.089722] NET: Registered protocol family 10
[    2.099065] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    2.100833] NET: Registered protocol family 17
[    2.100942] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts                                                                                      to load br_netfilter if you need this.
[    2.101285] Bluetooth: RFCOMM TTY layer initialized
[    2.101317] Bluetooth: RFCOMM socket layer initialized
[    2.101379] Bluetooth: RFCOMM ver 1.11
[    2.101534] 8021q: 802.1Q VLAN Support v1.8
[    2.101641] Key type dns_resolver registered
[    2.102068] omap_voltage_late_init: Voltage driver support not added
[    2.125804] Key type encrypted registered
[    2.200417] random: fast init done
[    2.207007] mmc0: new high speed SDIO card at address 0001
[    2.214892] tps65910 0-002d: No interrupt support, no core IRQ
[    2.225360] vrtc: supplied by vbat
[    2.233532] vio: supplied by vbat
[    2.239370] vdd1: supplied by vbat
[    2.245702] vdd2: supplied by vbat
[    2.253565] vdig1: supplied by vbat
[    2.259478] vdig2: supplied by vbat
[    2.265281] vpll: supplied by vbat
[    2.271016] vdac: supplied by vbat
[    2.276816] vaux1: supplied by vbat
[    2.282646] vaux2: supplied by vbat
[    2.288495] vaux33: supplied by vbat
[    2.294386] vmmc: supplied by vbat
[    2.300186] vbb: supplied by vbat
[    2.305937] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
[    2.314103] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 100 kHz
[    2.346321] bq32k 2-0068: Enabled trickle RTC battery charge.
[    2.354081] bq32k 2-0068: rtc core: registered bq32k as rtc0
[    2.360192] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 100 kHz
[    2.384038] musb-hdrc musb-hdrc.0: MUSB HDRC host driver
[    2.389770] musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
[    2.398056] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.405311] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.412959] usb usb1: Product: MUSB HDRC host driver
[    2.418256] usb usb1: Manufacturer: Linux 4.9.126-g259f2e0422 musb-hcd
[    2.425204] usb usb1: SerialNumber: musb-hdrc.0
[    2.431797] hub 1-0:1.0: USB hub found
[    2.436013] hub 1-0:1.0: 1 port detected
[    2.558046] bq32k 2-0068: setting system clock to 2025-06-27 20:33:30 UTC (1751056410)
[    2.569223] vwl1837: disabling
[    2.572554] vdd2: disabling
[    2.580968] Waiting for root device PARTUUID=4f9cc8ba-02...
[    2.632491] mmc2: new high speed MMC card at address 0001
[    2.639814] mmcblk2: mmc2:0001 W62704 3.53 GiB
[    2.645340] mmcblk2boot0: mmc2:0001 W62704 partition 1 2.00 MiB
[    2.652162] mmcblk2boot1: mmc2:0001 W62704 partition 2 2.00 MiB
[    2.660753]  mmcblk2: p1 p2 p3
[    2.837793] EXT4-fs (mmcblk2p2): recovery complete
[    2.844016] EXT4-fs (mmcblk2p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.852748] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    2.864289] devtmpfs: mounted
[    2.871525] Freeing unused kernel memory: 1024K
[    2.994661] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[    3.166025] usb 1-1: New USB device found, idVendor=0bda, idProduct=8153
[    3.173108] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[    3.194721] usb 1-1: Product: USB 10/100/1000 LAN
[    3.199694] usb 1-1: Manufacturer: Realtek
[    3.204010] usb 1-1: SerialNumber: 000001
[    3.224451] systemd[1]: systemd 234 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +S                                                                                     YSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN default                                                                                     -hierarchy=hybrid)
[    3.247872] systemd[1]: Detected architecture arm.

Welcome to Arago 2018.10!

[    3.286309] systemd[1]: Set hostname to <SWA44VFY>.
[    3.404902] usb 1-1: reset high-speed USB device number 2 using musb-hdrc
[    3.603493] systemd-fstab-generator[106]: Checking was requested for "i/dev/root", but it is not a device.
[    3.635067] r8152 1-1:1.0 eth1: v1.08.9
[    4.328188] random: systemd: uninitialized urandom read (16 bytes read)
[    4.342002] systemd[1]: Created slice User and Session Slice.
[  OK  ] Created slice User and Session Slice.
[    4.375171] random: systemd: uninitialized urandom read (16 bytes read)
[    4.383025] systemd[1]: Listening on Journal Socket.
[  OK  ] Listening on Journal Socket.
[    4.415212] random: systemd: uninitialized urandom read (16 bytes read)
[    4.422789] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    4.487559] systemd[1]: Reached target Swap.
[  OK  ] Reached target Swap.
[    4.516003] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[    4.580969] systemd[1]: Listening on Process Core Dump Socket.
[  OK  ] Listening on Process Core Dump Socket.
[    4.618350] systemd[1]: Created slice System Slice.
[  OK  ] Created slice System Slice.
         Mounting Temporary Directory (/tmp)...
[  OK  ] Reached target Slices.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-getty.slice.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Listening on udev Control Socket.
[    4.959097] EXT4-fs (mmcblk2p2): re-mounted. Opts: (null)
         Mounting POSIX Message Queue File System...
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Reached target Paths.
         Starting Load Kernel Modules...
[  OK  ] Reached target Remote File Systems.
[    5.153695] cryptodev: loading out-of-tree module taints kernel.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[    5.167550] cryptodev: driver 1.9 loaded.
         Starting Journal Service...
         Mounting Kernel Debug File System...
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on Network Service Netlink Socket.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Temporary Directory (/tmp).
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Load Kernel Modules.
         Starting Apply Kernel Variables...
         Mounting Kernel Configuration File System...
         Starting udev Coldplug all Devices...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Journal Service.
[  OK  ] Started Apply Kernel Variables.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /media/ram...
         Mounting /var/volatile...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted /var/volatile.
[  OK  ] Mounted /media/ram.
[    6.852126] systemd-journald[123]: Received request to flush runtime journal from PID 1
         Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Load/Save Random Seed.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Create Volatile Files and Directories.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[   11.180906] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc1
[  OK  ] Found device /dev/ttyO0.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
         Starting Network Service...
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
         Starting sshd.socket.
[  OK  ] Listening on sshd.socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Network Time Service (one-shot ntpdate mode)...
[  OK  ] Reached target Containers.
[  OK  ] Started A userspace daemon that run…ns under the eCryptfs mount point.
         Starting LSB: System logger...
         Starting Login Service...
[  OK  ] Started Periodic Command Scheduler.
[  OK  ] Started D-Bus System Message Bus.
[   15.808672] remoteproc remoteproc0: wkup_m3 is available
[   16.194979] remoteproc remoteproc0: powering up wkup_m3
[   16.303081] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 224708
[   16.407416] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x192
[   16.494928] remoteproc remoteproc0: remote processor wkup_m3 is now up
         Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Started Network Time Service (one-shot ntpdate mode).
[  OK  ] Started Network Service.
[   17.305576] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   17.965416] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   17.976134] eth0: SPI thread created
[   19.044811] QCA7000 Reading signature
[   19.048768] QCA7000 read signature Pass
[   19.052832] QCA7000 sync Success
[   19.117633] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   19.646026] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[   19.739939] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[   19.780548] omap-aes 53500000.aes: will run requests pump with realtime priority
[  OK  ] Started LSB: System logger.
[   24.865454] wl18xx_driver wl18xx.0.auto: Direct firmware load for ti-connectivity/wl1271-nvs.bin failed wi                                                                                     th error -2
[*     ] (1 of 2) A start job is running for Login Servic[   25.336763] wlcore: wl18xx HW: 183x or 180x, PG 2                                                                                     .2 (ROM 0x11)
e (21s / 1min 39s)[   25.400175] wlcore: loaded
[***   ] (1 of 2) A start job is running for Login Service (21s / 1min 39s)[   26.162661] wlcore: PHY firmwar                                                                                     e version: Rev 8.2.0.0.245
[   26.286317] wlcore: firmware booted (Rev 8.9.0.0.88)
[   26.345698] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Login Service.
         Starting drivers.service...
         Starting evse-startup.service...
[  OK  ] Reached target Network.
         Starting DNS forwarder and DHCP server...
         Starting Permit User Sessions...
         Starting Network Name Resolution...
         Starting Network Time Service...
[  OK  ] Started Permit User Sessions.
[   29.175406] reset_miscdev.minor=55
[   29.215512] reset driver prm[2]: 0x00000001
[   29.219943] reset driver scratch: 0x00000000
[   29.224434] reset driver scratch verify: 0xAAAA5555
[   29.325127] reset driver prm[2]: 0x00000000
[   29.329554] reset driver ret=0
[  OK  ] Started Serial Getty on ttyO0.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
         Starting Synchronize System and HW clocks...
[   29.661728] random: crng init done
[   29.665354] random: 7 urandom warning(s) missed due to ratelimiting
[FAILED] Failed to start DNS forwarder and DHCP server.
See 'systemctl status dnsmasq.service' for details.
[  OK  ] Started Synchronize System and HW clocks.
[  OK  ] Started Network Time Service.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
[   30.214832] gpio_miscdev.minor=54
[   30.218436] FactoryReset state is currently: 1
[   30.223115] Button: The button is mapped to IRQ: 97
         Starting The NGINX HTTP and reverse proxy server...
[   30.308448] ret=0
[   30.315399] Flash Thread has started running
[  OK  ] Started drivers.service.
[   30.988790] open from factory_reset.s
[   30.992979] Request from user: reset
[   31.053099] release from factory_reset.s
[  OK  ] Started The NGINX HTTP and reverse proxy server.
[   32.742290] EXT4-fs (mmcblk2p3): recovery complete
[   32.748396] EXT4-fs (mmcblk2p3): mounted filesystem with ordered data mode. Opts: (null)
         Starting helios_service.service...
[  OK  ] Started helios_service.service.
         Starting Time & Date Service...


 ####### #     #  #####  #######
 #       #     # #     # #
 #       #     # #       #
 #####   #     #  #####  #####
 #        #   #        # #
 #         # #   #     # #
 #######    #     #####  #######


FIRMWARE_VERSION: 4.1.0.AB
SWA44VFY login: [   56.821483] open from python
[   56.838695] Request from user: blue off
[   56.842792] Red set to OFF
[   56.864994] Request from user: green slow flash
[   56.869808] Green set to FLASH
[   56.873069] Request from user: red slow flash
[   56.904931] Red set to FLASH
[   56.908604] open from python
[   56.911810] read from python
[   56.955042] release from python
[  100.214937] NET: Registered protocol family 38
[  130.755020] Request from user: blue off
[  130.759125] Red set to OFF
[  130.762035] Request from user: green fast flash
[  130.775546] Green set to FLASH
[  130.779160] Request from user: red off
[  130.783131] Red set to OFF
[  132.237419] wlcore: down
[  136.400359] wlcore: PHY firmware version: Rev 8.2.0.0.245
[  136.502511] wlcore: firmware booted (Rev 8.9.0.0.88)
[  141.023318] wlan0: authenticate with 6c:5a:b0:88:4e:9a
[  141.033763] wlan0: send auth to 6c:5a:b0:88:4e:9a (try 1/3)
[  141.064254] wlan0: authenticated
[  141.079554] wlan0: associate with 6c:5a:b0:88:4e:9a (try 1/3)
[  141.105044] wlan0: RX AssocResp from 6c:5a:b0:88:4e:9a (capab=0x1011 status=0 aid=11)
[  141.157301] wlan0: associated
[  144.221273] wlcore: Association completed.
[  167.048935] Request from user: blue off
[  167.053071] Red set to OFF
[  167.074933] Request from user: green on
[  167.079020] Green set to ON
[  167.082010] Request from user: red off
[  167.094878] Red set to OFF

it will do the red set green set sequence forever until you hit enter then the EVSE login prompt shows.

So I happen to have a spare FCSP.

I can confirm will boot up its LV systems if you add a 12-V supply to the Dark Start connection

I wonder if this might be a way to bench test this a little more rather than using in-situ systems.

Is there a git somewhere for what we've got so far?

I wonder if the two "IR SEL" pins could be traced back to see where they go on the FCSP on the bench?

 

[ericpullen]

I got busy with work and haven’t had a chance to hook up my serial terminal server, but this is great intel, let me do some research on this Linux distribution. Looks like it is from Texas Instruments, so maybe they have some default passwords we can try.

Sponsored